How to manually restore a corrupt table in PHPAdminPosted on 10
Last week I logged into my WordPress Admin and to my surprise, found that all of my site’s comments (12,000+) were missing. After some searching around, I narrowed down the problem to a corrupt wp-comments file. How the file became corrupt I do not know, but thankfully the comments are restored now.
I thought it would be worth sharing how I went about fixing it, just in case it happens to some one else. The solution not only works for the wp-comments file, but all WordPress / PHPAdmin SQL files so basically this is a tutorial on how to manually restore a corrupt table / file in PHPAdmin, rather than just the specific comments file used in the example below.
After I noticed my comments were gone I sent out a tweet to figure out how to fix a corrupt comments file. I got a few suggestions (thanks!) such as turning off all plug-ins and repairing the database table, but none of these solutions worked. Another suggestion was to upload my full sql backup to restore the comments. I tried this but PHPAdmin blocked the import due to duplicate database entries. I was then pointed to this article, which I later found, was the right solution.
Although the article had the solution, I didn’t really have the database skills to do what was needed, however, thankfully Josh Betz kindly sent me an email & video explaining how to do it. I also had help from another friend who tested the files on a local DB first.
Here are Josh’s accompanying instructions for the video. Take note that this tutorial is for the comments & commentsmeta tables but you can use this method for any table in PHPAdmin.
To restore all your comments, you probably want to replace the `wp_comments` and `wp_commentsmeta` tables. I’ve got two screen shots here of both of those sections. In the video I explain that there is code to create each of the tables and then there is code to populate the tables. The creation of the tables is obviously where it says CREATE TABLE `table_name`. They are then populated with the sections of INSERT INTO `table_name`.
Now, the plugin that I use adds a part that will drop the table that it’s trying to restore before it creates the table because SQL isn’t going to let you create a table that already exists, which is why you were getting that error.
What I would do if I were you would be to copy the CREATE TABLE `wp_comments` and all the INSERT INTO `wp_comments` lines after that along with the CREATE TABLE `wp_commentsmeta` and all the INSERT INTO `wp_commentsmeta` after that. I would put those two sections into a new file called restore.sql and add DROP TABLE IF EXISTS `wp_commentsmeta` before the creation of that table and DROP TABLE IF EXISTS `wp_commentsmeta` before the creation of that table.
Then you can go into phpMyAdmin and click on the database you want, then import your sql file.
Another learning experience & just another reason to back up often!
- Taking UX to the Next Level in 2014: How to Exceed Customer Expectations (4)
- 4 Successful Marketing Campaigns that Rocked the World! (7)
- The Current State of Illustration and How to Succeed in 2014 (7)
- My Logo for Jerry Seinfeld shown at Superbowl Half Time (8)
- The 2013 Logo of The Year + Runner Ups (9)