Hi @alastairmcl, thanks for getting in touch.
The login button being unresponsive does sound strange, even for a Wordfence block as I’d not expect any action to be taken by the firewall before the form is submitted. It sounds like another plugin might be conflicting with Wordfence on the front-end, which is why the problem seems to be solved when it’s disabled.
I would firstly recommend enabling Learning Mode or allowlisting directly from any blocks you see on the Live Traffic page. Both methods are explained here: https://www.wordfence.com/help/firewall/learning-mode/
If that doesn’t solve it, Wordfence’s Login Security (2FA/reCAPTCHA) are only compatible with the default WordPress and WooCommerce login/registration forms. If this plugin creates a custom popup or form that has a different login flow to what we’re expecting, that may be another reason for the issue if you have those features enabled. You may need to disable one or both of those to see if the problem subsides during that time.
Thanks,
Peter.
Hi Peter,
I have already enabled learning mode and we are not using any Wordfence login systems aside from blocking invalid usernames etc. I need some practical advice on what we can do to actually troubleshoot this properly as there are no console errors or any other obvious way to debug.
Hi @alastairmcl,
Recommending Learning Mode or a manual allowlist from Live Traffic might have helped immediately fix a false-positive that was blocking another plugin’s actions, in turn breaking your login form. Thanks for trying that out.
When disabling Wordfence seems to fix an issue not being reported by other customers, it is often a plugin/theme conflict. The best way to test this is to begin with Wordfence as your only enabled plugin (other than Formidable Forms in this case) and switching to a default theme such as Twenty Twenty-Five. If the login form works as expected, reenable your plugins and theme one-by-one, testing the page in between until you find out what causes the issue to return.
We do adhere to documented WordPress development standards, so often another plugin/theme’s styles or JavaScript will be conflicting with Wordfence when this kind of problem occurs.
Many thanks,
Peter.
