Things not to do when updating wordpress…

Sorry, couldn’t think of a better title for this one. Usually I can, but in this case it was the most bizarre thing that has happened. One of my client had an old WordPress site. I tried several times to update it (it was pre-2.5, so I had to do it manually), but finally learned from the hosting company that they didn’t want people updating WordPress. They said they weren’t sure it was stable, and that is why they kept it below 2.5. So, I informed the client, and thought no more of it.

Then, out of the blue, the hosting company suggested that perhaps it would be a good idea to upgrade after all, but the only way they would let me do was so was to remove it and reinstall it. No, problem I thought, I’ll just export the wordpress content and then upload it again when 2.9.2 was installed.

But, and here is the but, the older wordpress exports in xml. The new WordPress doesn’t recognize that. And of course it was 11pm at night, on a weekend, so there was no one to call or contact, and the blog had no content. Sigh. The only good thing was that the XML code was easy to figure out, and I was able to extract all the content, and repost the site, so no one was quite the wiser (although it didn’t save some photos, which I had to request, saying they had been lost in the upgrade.

So, what is my advice? Oh, besides always having backup, as I thought I did? Always have the old WordPress blog site up when you update, so if you can’t retrieve things any other way, you can always see how it was supposed to be.

Actually, the best thing to do, if you can, is make all your updates on your computer, keep a copy there, so that if anything is lost, you can get it all back.


Leave a Reply