Upgrading WordPress to 2.9.1

If this blog goes dark, you’ll know why. This always scares me. I wish WordPress had reliable XML export and import, not SQL.

I upgraded The Cafes yesterday. The automatic upgrade failed, but manual upgrade seems to have succeeded.

OK. Seems like the upgrade completed successfully. Holler if you notice any problems. I think I’ll spend the rest of the morning straightening out the old computer mess as part of my general effort to simplify, clean up, and declutter my apartment.

Oops. Forgot to reenable the plugins including Akismet so there’s already a lot of spam. Bleach. Fixed.

3 Responses to “Upgrading WordPress to 2.9.1”

  1. Digitivity Says:

    Why be afraid of a WordPress upgrade? A backup is just a couple of command lines away:

    Here’s what a variation of what I use:

    nice mysqldump –user=username –password=password \
    –host=databasehost databasename | bzip2 > wp_database`date +%Y%m%d`.bz2

    nice tar cfz blog_backup`date +%Y%m%d`.tgz public_html

    The first dumps the database into a bzipped SQL file. The second gzips your files.

  2. Romain Guy Says:

    And if you don’t like the command line (or don’t have access to it), you can generate database backups from the admin interface.

  3. Elliotte Rusty Harold Says:

    I can backup easily enough. However I’ve never been able to successfully restore. The SQL dumps usually require a lot of fixing before they’re loadable. :-( Fortunately I’ve never had a complete failure on the upgrade. I did once lose all my categories though, and it was simply easier to reenter them manually than to restore.

    I much prefer the way eXist does this. each document is backed up into a separate XML document sop that one corrupt file doesn’t bork the whole process.

Leave a Reply