Unfortunately, I can confirm this issue.
The v2.3.04 update only included a minor field-related code change in the JavaScript file, so it shouldn’t affect form submissions under normal conditions.
Could you please confirm if you’re using any caching or optimization plugin? If so, try clearing its cache and see if the issue persists, sometimes old cached JS files can trigger that “Spam or JavaScript disabled” message.
Also, please share one of the URLs where v2.3.04 is currently active so I can check it directly and investigate further.
@dcsupport I had an issue on one client site, and rolling back resolved it. But, on my test site using SureForms with the extended version, it’s not having the issue.
So let me try reproducing it using the main plugin only and Contact Form 7 or other… I will update shortly.
Ok well I’ve tried reproducing it on a dev site using Contact Form 7 and only the latest version of the main plugin activated, and it’s working fine.
On my client site, it was a long form and if required fields were missing, it was showing the WP Armour error message along with the required fields error messages per field… so maybe that was the cause? I’m not sure now.
Is this marked as resolved now? Why?
I am using the plugin on a standard wordpress contact form, no special form plugin. Only the standard fields: comment, name, email, URL. So nothing special. Yet I still had the issue? (which I would not have found out if another user hadn’t contacted me by mail)
I checked again, and found out it’s even worse than I thought: I now have the same problem using 2.3.03 too. Tested on various browsers. WP-Armour worked fine when it did but I’m afraid it’s too unreliable to use now.
How is this marked as resolved? We have the same issue; contact form 7 does not work at all anymore … 🙁
I have the same question. Disabled the plugin for quite some time now and will check again on the next update but I don’t have much hope
To clarify, we didn’t marked the ticket as resolved.
If any site where you have installed the latest version and can share url to me that will really help to find the cause. So far, in most cases it has been just old javascript cached file issue.
Thanks
OK I reactivated the plugin (deactivated for 2 weeks) to send you a link to test. But as I tested myself I see it works fine now. So it may have been a cache issue like you mentioned indeed. I will keep testing in the following days and let you know if the problem returns
