Badly manipulated by WordPress 2.5

Everything was fine originally. I wrote my blog about entrepreneurship and making money, while WordPress 2.5 was busy fixing bugs of various sizes. Seeing other friends either delaying the upgrade with warnings or announcing their joy in upgrading to WordPress 2.5, the Jishui Chengyuan Blog wanted to observe more and secretly paid tribute to these pioneers in my heart.

By chance, last night during the site backup process, I saw a few more friends who had upgraded to WordPress 2.5. On impulse, I downloaded this version from the official website and tested it locally first. I found that the backend was simpler, the colors were livelier, but it didn't have the professional and rigorous overall coordination of version 2.3.

It was said that the execution efficiency of WordPress 2.5 was higher. Tempted by this irresistible and seemingly beautiful allure, we began our journey of upgrading from WordPress 2.3 to WordPress 2.5: First, we FTP'd all the files to the server and overwrote the old files, then logged into the backend normally. At this point, it would prompt you to click on the upgrade, a left click, and very quickly, the upgrade was completed.

Everything looked normal, so I felt a little excited. It was 3 AM when I washed my face and went to bed.

With the sunlight, the hour hand pointed to 11 in the morning. After getting up, we logged into the new WordPress 2.5 backend. As soon as we entered, it very obediently used a prominent red color to alert me that there were spam comments again. They definitely had to be deleted without hesitation. So, without delay, I left-clicked, selected all, deleted, selected all again, deleted, deleted again! Hmm, how come 80 spam comments weren't finished after deleting several times? Shockingly, we realized that under the prominent red guidance, WordPress actually placed spam comments and normal comments on the same page!!

The worst thing in the world is this - with the cooperation of the mastermind and accomplice, poor comments, carrying the hard work of friends who wrote them, passed away. Wait, we did back up the database before the upgrade and exported the xml file for insurance. Lucky us.

Next came the recovery journey: We rushed over, quickly went to the godaddy account, opened the mysql database, and directly uploaded the database backed up last night. Immediately, it prompted that the relevant tables already existed, and the upload was unsuccessful! Could I delete the previous tables or even drop the database and re-import it? Lifting the axe, I ultimately dared not bring the knife down on the small hand of the database, seeing the innocent eyes of the Jishui Chengyuan Blog and thinking of the potential catastrophic consequences.

Unintentionally, the writing got longer and longer. With feelings of shock, disappointment, anger, and excitement, we will see how things get resolved. Want to know how your comments can be recovered? Stay tuned for the next episode.

Jishui Chengyuan Blog original writing

Reprints must indicate - Reprinted from: Jishui Chengyuan Blog - Internet Entrepreneurship and Making Money SHOW! [http://jscyshow.com]

This article link: http://jscyshow.com/upgrade-to-wordpress-25-problem-lose-comment-414.html