Plugin Author
Arnan
(@adegans)
Does it work if you enable the WooCommerce protection?
Plugin Author
Arnan
(@adegans)
Hmm 🤔
Which version of WordPress/ClassicPress and WooCommerce do you have?
WP 6.7.1 and Woocommerce 9.5.1.
I also have Payment Plugins for PayPal WooCommerce 1.0.54
-
This reply was modified 1 year, 4 months ago by
Envox d.o.o..
Plugin Author
Arnan
(@adegans)
I just did some tests and it seems to work fine for me on WP 6.7.1 and WC 9.5.1.
Make sure you’re not allowing the username to be an email address as that defeats the ‘disallow email as username’ setting in my plugin.
The email for username setting is warned about in the No-Bot settings.
You’ll find this in WC > Settings > Accounts & Privacy, under the ‘account creation options’.
I made the requested changes: now Woocommerce asks me to enter a username during checkout, but the No-bot plugin returns “Error: Bots are not welcome!”
Plugin Author
Arnan
(@adegans)
Then the plugin thinks you’re a bot.
This can happen if you enter something in a hidden login field, this field should stay empty. Bots don’t know that, so they auto-fill every field they find and thus fail the checks.
Or if the security questions you set up do not match the possible answers, another thing bots often screw up and thus fail another check.
My guess would be that something is wrong with the security question you set up.
Hm, the thing is, it’s been working as expected for many months now and it seems that in some of the recent updates to one or more plugins I started having this problem. This would be easier for me if the plugin never worked properly 😉
The security question has been the same from the very beginning.
Plugin Author
Arnan
(@adegans)
Yes that for sure would be easier from a troubleshooting pov 🙂
Let’s rule out a few things.
– It used to work.
– Issues likely started after doing updates.
– Yesterday on my plain WooCommerce setup It worked fine for 4 tests all created a new account without issue, while blocking the account until I met all requirements.
– You’ve changed one setting for usernames in WooCommerce which changed the login behavior.
– The current error is related to a background check for bots.
To me this means that WooCommerce has changed something without you knowing.
It also means that your settings in No-Bot are probably fine, assuming you didn’t change anything.
Since No-Bot does not talk to other plugins other than WooCommerce it seems unlikely to me that there is some kind of conflict (with other security plugins for example).
Since you’re now stuck on a bot protection feature related to the form fields it might be an autofill issue (From another plugin or your browser. Though either sounds unlikely) or something is wrong with the security questions you set up (More common if things go wrong).
Maybe simply re-saving the security questions helps. If the plugin gets stuck on that, mismatching the answers, resaving it with the correct data should fix that.
Of-course make sure the questions have the answers you want.
