Categories
Computers

WordPress 2.6 hits the road

Old news for some, I suppose, but the challenge for me was upgrading my WP2.5.1 to 2.6. Would I do it? Could I do it? The answer is an emphatic YES! I managed to do it last night, although I sustained some nerve-wrecking moments, especially after deleting old files, uploading new ones, then waiting to see whether it would be successful. I’m happy to say that the upgrade went without a hitch (my mentor Doris would be proud of me). I’d just like to share some personal tips if you’re new to this stuff (there’s a newbie born every minute).

  1. Read and watch the video about the new WordPress 2.6 and its features here.
  2. You can read the Three Step Upgrade here but honestly, I would advice reading the detailed upgrade instructions. I must have read through this at least 3 to 4 times, and it paid off for me because my upgrade went by without any problems at all. Follow the instructions very carefully.
  3. This is perhaps the most important, especially if this is your first time upgrading WordPress. Give yourself plenty of time. I did this after the family went to bed, and so I could focus and concentrate on the task at hand. Took me about 30-40 minutes, but it paid off!

5 replies on “WordPress 2.6 hits the road”

Oh I’m very proud of you!! I accidentally aborted an upgrade once and corrupted my SQL database. I can assure you that was no fun to get out of. I won’t bore you with the gory painful details – but lesson learned from me – take the nerve wracking minutes over clicking cancel any day of the week!

Glad to hear you did it without any issues. I backup both my entire directory files + the SQL database before I start, then I follow the detailed upgrade instructions. It does make it a lot longer backing up all the files, but of course it’s worth it if you loose anything. 🙂

So do I, Lisa. Backup, that is. But now, after having gone through one upgrade, the old grey matter is now prepared for future ones, lol.

Leave a Reply

Your email address will not be published. Required fields are marked *