A while ago, I upgraded to WordPress 2.3. I host my blog with Dreamhost, and they have easy, “one-click” installs for this sort of thing, but the one-click upgrade wouldn’t work for me. Turns out there was a problem with the path the one-click robot was using to apply the upgrade: I had entered an extra trailing slash at some point along the road, and this broke the poor little one-click robot’s brain. It just couldn’t find the code it was supposed to update.
This isn’t something I can re-configure from my end, so, rather than calling on support, I took this as an opportunity to try something new: installing/upgrading WordPress via Subversion.
I’d been using Subversion a lot lately for the projects I’d been working on, and thought this sounded like a good idea. Version control is a Good Thing. I dig it, and figured I might as well version control my blog, too, and let Subversion do all the thinking when it comes to future upgrades. If I’d fixed things to work with the Dreamhost one-click, I’d still have had to wait for them to upgrade the one-click itself every time there was a new WordPress version available. If I’d downloaded the code and installed it myself, I’d have had to do that every time a new version was available. By using Subversion, I could get all the updates as soon as they were available, and could leverage version control to avoid whole-cloth reinstalls/updates with each version of WordPress.
So, following the directions in Section 4 of a Codex article called “Installing/Updating WordPress with Subversion“, I converted my “traditional” WordPress blog to a Subversion checkout of version 2.3. This went off without a hitch, and everything seemed to be just fine.
Today, I finally got to test the ease of upgrading my recently-Subversioned WordPress install. This was accomplished with one command:
$ svn sw http://svn.automattic.com/wordpress/tags/2.3.1/
That’s it. Worked like a charm, and now I’m up to date again. I highly recommend this method of installing and updating/upgrading WordPress.
Tags: Subversion · Wordpress6 Comments
6 responses so far ↓
[...] though, we’ve moved away from using the one-click for WordPress. Instead, this blog was created by checking out a stable version of WordPress from the WordPress [...]
[...] though, we’ve moved away from using the one-click for WordPress. Instead, this blog was created by checking out a stable version of WordPress from the WordPress [...]
[...] though, we’ve moved away from using the one-click for WordPress. Instead, this blog was created by checking out a stable version of WordPress from the WordPress [...]
[...] though, we’ve moved away from using the one-click for WordPress. Instead, this blog was created by checking out a stable version of WordPress from the WordPress [...]
[...] though, we’ve moved away from using the one-click for WordPress. Instead, this blog was created by checking out a stable version of WordPress from the WordPress [...]
[...] though, we’ve moved away from using the one-click for WordPress. Instead, this blog was created by checking out a stable version of WordPress from the WordPress [...]