Lessons in Upgrading a WordPress blog

In the last 3 days, I’ve been trying to fix a blog that got screwed with a buggy upgrade from WordPress 2.0.3 to version 2.1.2. I have been upgrading dozens and dozens of blogs on an almost regular basis for years now but this has got to be the toughest one yet. A fracked up upgrade means that either some files are old and some are new or that some database tables did not convert completely or got corrupted in the process.

And yes, we’re not running out of lessons yet:

• If it ain’t broke, don’t fix it. That goes to say that if the upgrade is not a necessary one, i.e., the existing version is not vulnerable or open to exploits, skip the upgrade for later (or when you have time for the unexpected).
• Don’t assume that you’ve seen them all. With all the blogs and WP versions that you’ve gone thru, you’d think you’re an expert already. Well, it only takes one really screwed up update to get your humility to sink back into its proper place.
• Backup, backup, backup. Again, backup – backup – backup. Have to drill that deep into the skull.
• Read the manual (or documentation or update notes). Is anybody actually reading them?
• Time your upgrades. Don’t do them just before you go to sleep. So many things could happen is you’re close to dozing off. If something screwy happens, you’ll still have some energy to stay at it. Tech Support guys call it the “resolution time“.
• If it’s not your own blog, get a waiver or disclaimer. Ok, that’s way too much. I mean, you’ll need to make the owner of the blog understand that though it’s an easy task, things could go wrong. A lot of patients die from a simple appendectomy because of circumstantial infections or the doctor just forgot to fish out the scalpel before stitching their belly back.
• Save copies of the old app version. In case you’ll need to revert back, you still have copies of the old version to re-install.

The usual upload time of the new WordPress seems to be much longer compared the old versions. I believe there are more files now than the pre-2.0 version.

Anyway, hope this helps. ;)