Closed (fixed)
Project:
Antibot
Version:
8.x-1.4
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
1 Jul 2021 at 14:20 UTC
Updated:
7 Dec 2021 at 12:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
gawade.nagesh commentedComment #5
gawade.nagesh commentedHere is the patch.
Comment #6
gaurav.kapoor commented#5 works for me.
I was able to reproduce this issue and see that as of now if we add form id of a view exposed form (Eg: 'views-exposed-form-content-page-1') in the antibot settings, then antibot doesn't work.
After, applying the patch, the antibot starts working for specific exposed views exposed form as well.
I Will keep this issue open for now to get more feedback regarding the patch and we should also add a test specific to views exposed form as well.
Thanks for working on this @gawade.nagesh.
Comment #7
gaurav.kapoor commentedComment #8
paulocs@gaurav.kapoor how did you test it?
It looks like the form wasn't submitted before the patch as well but the form is not redirected to
/antibot...Comment #9
gaurav.kapoor commented@paulocs, here is how I tested it:
1. Add form ID of a view exposed form (Eg: 'views-exposed-form-content-page-1') to antibot settings.
2. The antibot module starts working for specific exposed views forms now, rather than all of them.
So with this users don't have to enable antibot for all the exposed view forms. With a slight tweak in deciding which forms to alter, we are able to have this feature.
Let me know if I am missing anything.
Comment #11
gaurav.kapoor commented