Everyone is a bot when posting? (even me)

Hi,
Sorry to hear about this glitch (and thanks for including the site that’s being affected). Two things come to mind immediately that would be appropriate to check: First, do you have any other similar plugin installed (Akismet, Recaptcha, etc)? If so, that would cause a conflict (imagine two traffic lights at one intersection – things go nuts). Second, is your site being cached (using CloudFlare or something similar)?
Please let me know – our dev team is ready to figure this out for you.
Also, feel free to contact me directly at [email protected]
Thanks,
William

Hi William,

Thank you for your reply.

I do have the ‘Akismet Anti-Spam’ plugin active.
matter-of-fact, I have used both simultaneously without any problem until now.
I got friends reporting they are bot now, this last couple of days..

No, I’m not using a caching service.

One thing that comes to mind my hosting provider has recently updated PHP 5.6 to
PHP version: 7.1.x, might that be a smoking gun to you?
After asking they told me there is a PHP 7.2.x available to go live.

If you like me to test anything, please do ask..
next week I’m able together with my tech guy to try out several scenario’s if you like.

My tech guy has a development server where we can test: https://wp.safeunderdark.com
without have to worry to cripple the live site.

Mind you, this is a different server than the ‘live site’

Thanks for you help ??

• This reply was modified 6 years, 8 months ago by Safeunderdark.
• This reply was modified 6 years, 8 months ago by Safeunderdark.

We found the problem: The plugin is not compatible with the new Jetpack comments. Because of the way Jetpack comments are handled, they circumvent our detection script. Usually, the only thing that tries to sneak past our script when posting is a bot, so it’s considering all Jetpack comments bots. Regretfully, there is no way to make a Jetpack comment compatible with NoMoreCaptchas.
Sorry I don’t have better news. We will update the compatibility list to reflect this.

Oh wow, that’s sad.. ??

just testing Version 3.0.3at my test site and it works perfectly there..
yea, jetpack not enabled there..
It can work with Akismet Version 4.0.8
and also with Jetpack Version 6.3.2
I updated Jetpack to Version 6.3.3 and it still works??

now updating NoMoreCaptchas to Version 3.0.4..

it still works?

wait I have WordPress 4.9.7 running Arcade Basic Child theme.
Running PHP version: 7.0.27 (SAPI: CGI-FCGI)

I have a wordpress update to 4.9.8 lingering in the background..

Right.. error 500… Hmm.. I might need to get back on you because of that..

Oh, boy..

okay I think I’ve stumbled on a major error here..

When ativated NoMoreCaptchas generates a error 500!!

if I rename the plugin folder everything is fine..

Renaming it back, plugin is deactivated..
upon reactivating the NoMoreCaptchas plugin.. got another error 500..

It also crippled my live site.. so you should have a look at it..
this could be a potential problem..

okay did some testing without Akismet and Jetpack..
Again error 500

not sure what’s the cause is but it
is somewhere in the NoMoreCaptchas Version 3.0.4 code. for some reason..

sorry to be the messenger of bad news.. :'(

And for information to others..

if you encounter this problem, to shutdown the plugin
go to your FTP and browse to
<your website>/wp-content/plugins and just rename
‘NoMoreCaptchas’ to ‘NoMoreCaptchas–‘ to disable it
no need to delete the plugin.

FYI:
I’ve just seen the other topic about this..
I know I have the last update.. since there are no more.. but it still crippless wordpress
the site including the back end (wordpress panel)..

even my Tech guy says.. there is no more update..

Got another note from my tech guy:

in the readme.txt is says:

Requires at least: 3.0
Tested up to: 4.9.8
Requires PHP: 5.6 or later
Stable tag: 3.0.5
License: GPLv2 or later

so this should indicate it being the latest version..

The 500 error was related to WP 4.9.8 and, as far as we can tell, there was a secondary issue arising from WP Bakery. The version uploaded today (3.0.6) should correct both of these.