I have a request for the initial configuration of the Antibot module.
After installing the module, the following forms, among others, are automatically protected by the module:
- user_login_form
- user_pass
If there is a problem with the Antibot module, for whatever reason, and the module locks these forms, it is no longer possible for the Drupal admin (and of course all other users) to log in to the website.
Again, if the Drupal admin does not have the drush tool (e.g. because his web host does not support it) with which he could uninstall Antibot, or at least delete the corresponding form IDs from the configuration, he is practically faced with a major problem.
My suggestion is:
Do not protect any forms with Antibot by default. Instead, for example, specify a selection of which forms it makes sense to protect - together with a warning and the recommendation to test extensively beforehand whether the antibot protection really works.
Issue fork antibot-3421589
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
danrodYes, this makes sense, given that we already had a couple of cases like that: https://www.drupal.org/project/antibot/issues/3223364
I'll look into this.
Comment #4
danrodI created a MR for this: https://git.drupalcode.org/project/antibot/-/merge_requests/28
you need to uninstall and install it to see the changes. Needs a quick review, hope someone can help me testing this.
Comment #5
danrodI had to leave the
user_passform in the list because the tests we failing on me, but I think it's ok for now.Needs review.
Comment #6
danrodComment #7
danrodI'll merge this to the 2.0.x branch if you don't mind @gaurav.kapoor , if you have questions please reach me and we can discuss the change.
Comment #8
danrodComment #10
danrod