WordPress 2.8 upgrade problem, downgrade possible?
June 16, 2009
Just like thousands of WordPress (WP) users who saw on June 11 that a new version — WordPress 2.8 — is already available, I clicked on the auto-upgrade link as soon as I saw it inside my blog’s Admin panel.
Wrong move! It crashed this blog and the site won’t load anymore!
For almost an hour yesterday, this blog was inaccessible. I tried logging in to the Admin Panel but I just got redirected again and again to the Admin login page.
How to downgrade a WordPress version?
I thought the only solution left was to downgrade the WordPress version. After searching online, I wasn’t able to find some easy way to do it. The ones I saw involve restoring the database backup but I did not bother with it because I know it would take hours since our WP blog database is huge.
Any other easy ways to downgrade a WordPress blog? Please post below.
Fortunately after further searching online, I read that the common cause of WordPress crashes after a version upgrade is incompatibility with the installed plugins. Usually, the solution is to uninstall all plugins then re-install them one by one to see which ones are causing the error. But then again, I can’t simply uninstall the plugins because I cannot login to the Admin Panel.
That’s when I stumbled upon a quick and easy but effective solution. Using my FTP software, I accessed my blog’s WordPress files.
Solution to WP 2.8 upgrade problem
Under the wp-content folder is the plugins folder which I renamed (to any name!). After doing so, all plugins became deactivated.
I then changed the folder name back to plugins and, fortunately, I did not encounter any problems anymore logging in to the Admin Panel. One by one, I activated the plugins but decided not to activate the following for the meantime because I read that they might be incompatible with the recent WordPress version.
- All-in-One SEO Pack
- Google XML Sitemaps
- WordPress Mobile Edition
This blog is now running version 2.8 and, fortunately, is currently problem-free.
Hope the above post will help those searching for a solution to the same WP 2.8 upgrade problem we had.