Problem/Motivation
We are having some anonymous users getting blocked with the message:
You have reached this page because you submitted a form that required JavaScript to be enabled on your browser.
But are finding they have JavaScript already enabled in their browser.
I then looked through the entire Antibot issue queue, and found this one that was marked Closed (Fixed) about 10 months ago, buried in the queue:
https://www.drupal.org/project/antibot/issues/3455727
I did begin to wonder if that message was a general Antibot blocking message... and it appears it is!
This commit is very helpful, so we don't go down the Javascript troubleshooting rabbit-hole with the user... they are getting blocked for some other reason.
Can we please get a release soon? There are 19 commits out on dev past the current release of 2.0.4, including the helpful one above......
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | antibot-new-message-3601070-4.patch | 1.14 KB | fizcs3 |
Issue fork antibot-3601070
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
danrodComment #3
danrodThanks for creating this issue, I'll fix some extra issues before creating a tagged release.
Comment #4
fizcs3 commentedYou're welcome @danrod, and thank you.
In the meantime:
I tried to apply a patch to 2.0.4 of the MR from related Issue #3455727 which has the revised message, but it would not apply...
So, I created a new patch that does apply to 2.0.4, copying that revised wording in, and have attached it for us to use.
Comment #5
danrodHi @fizcs3 , I created a new release with the latest bugfixes and new features: https://www.drupal.org/project/antibot/releases/2.0.5
Please test and let me know how it goes, I'll mark it as "Fixed", but please let me know if you have issues with this new release.
Thanks !
Comment #6
danrodComment #7
danrodI tested the new release and works as expected, no issues found and the forms I tested work fine.
Comment #8
danrodComment #9
danrodComment #11
danrodComment #12
fizcs3 commentedThank you @danrod!
Our issues with "antibot false positives" we've since found stemmed from Cloud Flare Rocket Loader being enabled on the domain. We didn't really need that and disabled it.