Vortex Radar

Great thanks JNashHawkins, you’re right. It does look like a plugin issue. I’ll reach out to them. ??

Looks like I spoke too soon. Even after restoring from a backup, it’s still being problematic with the same issue…

So I just did a restore using JetPack’s Vaultpress feature and it did the trick. Thank goodness for automated daily backups!

I’m really hesitant to update my plugins again now…

Thanks for the suggestion. I’ve taken a look at that one too and it has the same suggestions as the tutorial I linked to in the OP.

Looks like WPBrusier was the culprit. With that plugin disabled, I can now log in normally again and the comments now work on my site too.

Thanks so much for your help Lisa! You are a lifesaver. ??

Looks like it’s a plugin issue! Thank you!

I tried renaming the plugins folder and got a different error on login, so I tried resetting my password again and I’m in!

Now I gotta figure out which plugin caused the issue with a little trial and error. Thank you! ??

The username, email, and user role all look correct. Is user_status = 0 correct for an admin?

I tried resetting the password in phpMyAdmin with an md5 hash, but that didn’t work.

I just created a new user in phpMyAdmin using these directions. No luck logging in as the new user though.

There’s no unexpected users.

As far as security plugins, I am using Wordfence, Really Simple SSL, and Vaultpress.

• This reply was modified 5 years, 10 months ago by Vortex Radar.

I’m just gonna leave it with the feature disabled. It may be some other plugin conflicting, but I’ll mess with it later I suppose if I really need that feature activated. Commenting is working again and that’s the main priority. Thanks! ??

Testing some more, it’s a result of enabling “Let readers use WordPress.com, Twitter, Facebook, or Google+ accounts to comment.” If I disable that option, the problem is resolved.

Testing now, I notice that when I disable the Jetpack plugin, it starts working again.

I upgraded from Jetpack Free to the paid Jetpack Personal plan on 12/13 and my last comments are on 12/15 so I’m guessing it may have something to do with my new plan being activated.

I didn’t. Nothing in the spam queue either. On my end it looks like you never left a comment.

Fix: Disable logging in Bad Behavior and it should then function normally without errors.

https://www.ads-software.com/support/topic/135564?replies=101

Looks like it’s an issue with some plugins using a call to wp_post2cat which no longer exists as of WordPress 2.3.

I’m having this issue running WordPress 2.6.3 and Bad Behavior 2.0.24.

Just chiming in to say that I have the same problem as well and am hoping to find a fix. Spam has gone up since removing Bad Behavior from the server due to this problem.

bump