Archive for November, 2008

An update to the updater

Sunday, November 30th, 2008

Aaron gave me a great suggestion for the WordPress MU update script: pull the latest version directly from the download page. So I’ve added that as an alternative method. If no specific version is passed in, the script will pull down the latest, determine what version it is and check to see if it already exists before continuing with the installation (

I haven’t actually had the chance to fully run it through its paces yet, so we’ll see for sure when the next update is released.

I love upgrades

Wednesday, November 26th, 2008

I’m happy to report that I just had the chance to test my WordPress MU upgrade script, and everything went off without a hitch! One simple command and all of my blogs got the update to 2.6.5. Glory be!

Simplifying WordPress MU upgrades

Friday, November 14th, 2008

Okay, I’ll admit it. I’m really bad about upgrading my WordPress MU install in a timely manner. And that’s a pretty big disservice, especially for others (like my brother) hosted on the same install. So tonight, I put together a new directory structure for my WPMU installation, and with my brother’s help, wrote a wonderful little shell script to handle future upgrades for me.

Originally, I had WordPress MU file sitting in a WPMU directory. With each upgrade, I’d have to make sure I didn’t disrupt the existing important files (like those in wp-content).

My new structure involves a version-specific directory within the WPMU folder (eg wordpress-mu-2.6.3). Alongside that is a directory named const, to hold all of the files that remain constant between upgrades. Finally, there’s a symlink named current that points to the current version-specific directory. I then create additional symlinks within this directory back to files and directories in const.

I’ve attached a sanitized copy of the final script ( for your pleasure. It first checks to make that it’s running as root – my WPMU installation is outside the scope of my home directory, so that’s a necessity. There’s a few more checks to make sure the user has specified a version, and that there’s an archive of the WordPress MU files for that version. Then it goes to town, extracting the files, and symlinking the relevant items in const. I won’t go into the nitty-gritty, since it’s all pretty self-evident from the script.

If you do choose to use this yourself, just be sure to change the path on line 27 (unless that really is where you want your files).

Valid XHTML 1.0 Transitional