- π¬π§United Kingdom sabrina.liman
sabrina.liman β made their first commit to this issueβs fork.
- @sabrinaliman opened merge request.
- π¬π§United Kingdom sabrina.liman
I've added webforms to the honeypot config page as checkboxes and added a text area that allows form ids to be added.
- Status changed to Needs review
over 1 year ago 10:55pm 7 July 2023 - last update
over 1 year ago 14 pass, 4 fail - πΊπΈUnited States tr Cascadia
Setting to "Needs review" to get the testbot to test the patch.
The last submitted patch, 24: allow-more-flexible-form-config-2342473-24.patch, failed testing. View results β
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.- last update
over 1 year ago 14 pass, 4 fail - last update
over 1 year ago 14 pass, 4 fail - last update
over 1 year ago 14 pass, 4 fail - Status changed to Needs work
over 1 year ago 12:02am 8 July 2023 - πΊπΈUnited States tr Cascadia
Those are real test failures caused by the patch. There are also a lot of coding standards problems, mainly because you're using 4 spaces of indentation rather than the Drupal standard 2 spaces.
Can you take a look at the test failures and see if you can resolve them with a new patch?
- First commit to issue fork.
- π³πΏNew Zealand ericgsmith
Had a look at the patch but it might need further work that I don't think I have time for.
Patch from #24 was introducing a new config key additional_form_ids which was not being used anywhere other than the form, and it was merging these values onto the existing form settings. This confused me as adding to additional_form_ids manually had no effect.
I made a few changes to only store in form_settings - but I suspect its actually cleaner to only use additional_form_ids and then update the logic in HoneypotService to be aware of the additional source if ids. This would certainly make the form logic cleaner - but unfortunately was not the first direction I went down.
Leaving as needs work based on above.
- First commit to issue fork.
- Merge request !28Issue #2342473 by DYdave, ericgsmith: Added 'additional_form_ids'... β (Open) created by dydave
- last update
9 months ago 30 pass - Status changed to Needs review
9 months ago 1:30am 4 June 2024 - π«π·France dydave
Thanks a lot Eric (@ericgsmith) for your comment at #30!
It provided the basic guidelines for the implementation of this feature:
I've created a new merge request MR!28 with the approach suggested with a new configuration form setting
additional_form_ids
which could be used in the service.Additionally, a few tests were added to check the additional custom form ids would be properly protected by honeypot, see:
https://git.drupalcode.org/project/honeypot/-/merge_requests/28/diffs#di...- Job: https://git.drupalcode.org/issue/honeypot-2342473/-/pipelines/190336
- PHPUnit: https://git.drupalcode.org/issue/honeypot-2342473/-/jobs/1769492
The added test cases seem to pass.
The only errors currently reported are not related with this merge request, they have already been addressed in different issues, see:- π PHPUnit: Fix Functional Tests 'HoneypotFormCacheTest' Needs review
- π [10.2] PHPUnit errors: non-existent service plugin.manager.field.field_type_category Needs review
Therefore, at this point, this new feature "should" be ready to be tested, thus switching ticket back to Needs review as an attempt to get more reviews, testing and feedback on MR!28.Thanks in advance!