Yet Another WordPress Upgrade Gone Wrong

Well, the upgrade process was easy with the exceptions that I could no longer view the blog.

I can still access the admin page, but no page can be viewed.

This is not good.

For some reason, the upgrade from WordPress 2.6 to WordPress 2.6.1 went wrong.

Installing WordPress 2.6

WordPress 2.6 has just been released, and I hastily upgraded the self-hosted blog from version 2.5.1 to version 2.6 after I backed up the database first.

The upgrade process took about 10 minutes to complete, including the uploading new WordPress 2.6 files to the server. It could’ve been faster, but for some reason the web-host incoming FTP is pretty slow.

Before upgrading, I turned of any caching plugins.

Overall, the upgrade process is painless. Don’t forget to clear your browser cache after upgrading to WordPress 2.6.

WordPress 2.6 Tyner

——-

p.s. WordPress Apps for the iPhone is coming soon, but there’s no ETA given yet.

Updating to WordPress 2.5.1

WordPress 2.5.1 is released.
http://wordpress.org/development/2008/04/wordpress-251/

This release includes a number of bug fixes, performance enhancements, and one very important security fix. Some of them are:

  • Performance improvements for the Dashboard, Write Post, and Edit Comments pages.
  • Better performance for those who have many categories
  • Media Uploader fixes
  • An upgrade to TinyMCE 3.0.7
  • Widget Administration fixes
  • Various usability improvements
  • Layout fixes for IE

I am upgrading my blog to WordPress 2.5.1 as I am writing this post. The first thing I did was backing up the WordPress database before attempting the upgrade.

Resurrecting a WordPress Blog

To quote the character played by Tony Shalhoub, “Here’s what happened.”

March 4th 204, I decided to upgrade my WordPress 2.0.x blog to version 2.3.3 after creating a backup. Long story short, the Yahoo! installed WordPress blog could not be upgraded to version 2.3.3 safely, and essentially in the process, my database was corrupted.

The worse news is that the backup was not good either. After a seemingly long period of self-deprecation, I started a new WordPress 2.3.3 blog. It was almost perfect, but completely functional.

Anyway, I reinstall the blog using Yahoo! control panel, and it turned out to be version 2.3.2 sans all my postings. I had a really old back-up, and it was not compatible with WordPress at all.

March 30th, I upgraded all my WordPress blog to version 2.5 including the one with all the missing postings. Still dreading from the loss, I slowly did some manual entry on the blog. Then it hit me. I tried using the backup and restore feature. I backed-up 37prime.wordpress.com and restored it to 37prime.com/blog.

IT WORKED!

Not perfect, but I got 80% of my postings back.

Now I have no worries when it comes to moving the WordPress blog.

I’m sleepy, so I’m gonna get some sleep.