WordPress 2.5 Upgrade

By | 2008/03/29

After some testing on some of my less-popular blogs I’ve upgraded this one to WordPress 2.5.  The whole ordeal seemed fairly painless (although with the number of blogs I host I really should consider WPMU).

I use svn to manage my installations which makes it really simple.  If you’re considering an upgrade, these are the steps I followed:

  1. Make a backup of your current data–can’t be too safe.  Export your current database & php.
  2. De-activate current plugins
  3. change to the root directory of your blog and execute:
  4. svn sw http://svn.automattic.com/wordpress/tags/2.5/
  5. I had an issue with Akismet, so I also then did:
  6. rm -r wp-content/plugins/akismet/
  7. svn up
  8. visit http://your-site.com/wp-admin/upgrade.php
  9. re-activate plugins
  10. Done

I want to congratulate the WordPress team for a great release.  Things look really sharp this time around and there look to be a lot of UI improvements.  I’m also glad to see I didn’t have any issues upgrading like I did after the early 2.2.x series.

8 thoughts on “WordPress 2.5 Upgrade

  1. Chip Bennett

    I also upgraded to WP version 2.5 this weekend; like yours, my experience was relatively painless. Thus far, I’ve not experienced any real problems (and like the admin UI changes).

    However, I notice that you had a pretty lengthy upgrade instruction list. I would like to recommend that you look into WordPress Automatic Upgrade (most recent version available in the wordpress.org plugin repository), for guided and painless upgrades.

    The WPAU plugin will guide the upgrade automatically, from performing file/database backups, to putting the blog in maintenance mode, disabling active plugins, fetching and installing the upgrade files, upgrading the database, and re-enabling previously active plugins.

    It has been a great help for me in keeping my wordpress installation always up to date.

    Reply
  2. Maurice Walshe

    you also need to add the SECRET_KEY entry to the wp-config – whey the upgrade script doesnt do this I dont know

    Reply
  3. Mike Brennan

    I think you have one minor typo. The command:

    svn sw http://svn.automattic.com/wordpress/tags/2.5/

    should have a period at the end to tell subversion to put the files in the current directory. Otherwise, it puts them in a subdirectory called “2.5”. So the command should be:

    svn sw http://svn.automattic.com/wordpress/tags/2.5/ .

    Other than that, this went smoothly for me. Thanks for the tip! I was tired of waiting for 2.5 to show up in the Ubuntu repositories, so I uninstalled WordPress (saving my wp-config.php before doing so), and switched to using subversion. Much better.

    Reply
  4. Jamie Le Souef

    2.5.1 is quite nice and stable. I’ve had a look at 2.6 and found that there are a couple of bugs (for my anyways)

    How are you finding it over 2.3.x?

    Reply
  5. Brisbane web design

    Thanks so much for your tutorial.

    I’m really looking forward to this week’s release of Ubuntu.

    A Stumble for your efforts 🙂

    Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.