Futurelooks

OK. So thanks to @outcats85 I was able to login again thanks to a tip on the latest Jetpack Plugin (4.2?) breaking the plugin.

However, I’m still not able to log back in using my usual admin account.

Does anyone know how to clear the lock out on a user account? I’ve already cleared the DB (it_temp/it_lockout) and have turned off pretty much everything except for the hide backend feature.

Any ideas?

Wow. Thanks! That at least got me back in. But my main admin account is still triggering the brute force ban. Not sure how to get around that ??

Bumping this one up because a few hours after I updated to 5.6.1 this issue cropped up.

“This has been disabled” is now all we see. Can’t login. Can’t do anything. Renaming the plugin directory and removing .HTACCESS section has no effect.

Did anyone else get this problem going from 5.6.0 to 5.6.1. It was working so well for so long.

@outcats85

May I ask which plugin you found affecting this? Hopefully it will fix my issue as well.

Thanks js.

It looks like these changes were already integrated into the core.trac version of Option.php. I just compared your changes and they were already present.

Just got word back from a few of our readers. Problem persists even with the option.php from the core.trac.

Sounds like there are definitely some things not right with the WordPress Core. But the only thing I’ve observed is that the install that had this plugin is the one having the hissy fit.

Not blaming you as you’ve made some good points as to how your plugin cannot be a cause. However, the site is still having the issue despite the recommended fixes, which are still appreciated.

Hopefully someone will pop their head in with a “Eureka” moment.

Just installed the updated option.php from that to see if there would be any change.

Option 1 doesn’t fix it. I just got responses back from around the interwebz saying it’s still persistent. Going onto option 2.

Just tried option no 1 in your suggested PHP fixes. I’ll keep an eye on it and get some feedback from our staff and readers and report back.

I would normally think that except that both websites I run have exactly the same custom themes (with the exception of color/logo), down to the same plugins, running on the same server, with the exception that one of them, I installed this plugin, while the other one, I didn’t (tried out Yoast instead). The other site doesn’t exhibit the issue at all.

The other behaviour I noticed is that it seems to be exhibiting a “time out” period. For example, I’ll do what I did above in IE, then I hit the error. I’ll leave it alone for 10 – 20 seconds, refresh the page, and it’ll come up again. If I don’t wait long enough, it’ll attempt to load, then choke and return this error.

I just tried commenting out those two lines. Doesn’t affect Chrome because the problem wasn’t with that browser, but IE still has the issue, despite clearing out the caches, the site cache, even the CDN directly.

Does that give you any more data points?

Just curious, but has anyone had users using Internet Explorer complaining that the problem persists? I use Chrome myself normally, but when my staff and some readers mentioned that IE was giving this error all the time, even with the fix posted, I gave it a shot, and sure enough, it’s persistent. Basically, I’ll go to the site, no issue, click on some articles, no problem, then head back to the main page using the HOME tab and it’ll give me the “0 is a protected WP option and may not be modified” error.

This is with or without the plugin installed. But the issues started when I started using it. I can see that there might be a possibility that WP code might be at fault (as you noted above) but is there we can work around this for now? My staff and my readers are getting annoyed.

Thanks!

I’ve been trying to completely remove this plugin. Is there anything I’ve missed besides the usual deactivate/delete and DB scan for NGFB options? I’m still getting the “0 is a protected WP option and may not be modified” error.

Just wanted to cover my bases before looking elsewhere. But the only search for this error only comes up with threads/posts related to this plugin (which I have used and had issues with on my install).

Thanks!

-Stephen