reybeez

Okay an update. Nothing worked and I didn’t want to do a clean install because I felt I would be doubling down on a problem without fixing it. Thankfully, I keep yearly full database backups. So I rolled the entire site back to something like 4.8 with the full database from then. This would mean I would lose a few comments but, at the very least, the articles was in the same state as today when I was trying to re-use the blog. Everything worked in that version. From there, I did a full update to 5.2.2 and everything works again, including Yoast with the new posts.

Next step is to see if I can reduce the weight of the database a bit by dropping tables that my install doesn’t use. I’ll mark this topic as resolved but not on account of discovering what was wrong but rather that I’m operational again based on the rollback. The steps above might help other people but do note that messing with the db comes with risks.

I haven’t tried reinstalling wordpress. That seems like the nuclear bomb option. I’ll do it, but as my last step since I’ll have to export everything (etc.) I reached out to my hosting company and am waiting to hear back.

I just started getting this after my upgrade to 2.8. M.Hasaan’s answer works though.

I just started getting this after my upgrade to 2.8. Gregclow’s answer works though.

I’m on inmotion hosting too and I have the same problem. So far, I’m thinking it’s the company so I’m planning a move.

Tracked it down. Apparently a plugin by the name of Subscribe to Comments isn’t compatible with 2.5 but it doesn’t let you know. What the plugin does is add a row to the $_comments table in the mysql which isn’t interpreted by the edit_comments.php. What I did to fix it was create a new $_comments table and imported the data from the table with the extra row into it (this means you’ll have to duplicate that table, and delete a row to match the row count to allow the data transfer). After the data is transfered the comments show up just fine when edit-comments.php loads in the backend.

For future reference, don’t copy paste from Word. It uses smart quotes, elipses, em-dashes…all things that wind up doing some pretty wacky junk when you move databases.

duplicate your db.
download wp 2.5 fresh install
install in a new folder and use the wp-config.php file linking to the duplicate db.
see if you have the same problem.
if you don’t check to see if your original folder is using any .htaccess files. Disable them and see if you have the problem.
If it doesn’t have the problem after the htaccess files are disabled, you may want to edit the file to have not as tight settings.

I found out that the error occurred when I had the WPIDS wordpress plugin enabled. Once I disabled that I was able to connect with LiveWriter.

I’d suggest first disabling your plugins and re-enabling them one by one.

Good luck.

interesting: recent comments show up on admin front page but not on edit-comments.php

Further notes: problem continues even with all plugins disabled. Continues when pulling data in from an older version of my database too. Also continues when I disabled the htaccess files. Next: disable the php.ini files.