WordPress 2.0.4 Update
It has been a few days now, but I noticed that WordPress 2.0.4 has now been released and is highly recommended due to the fixing of a few security issues. They also list a number of bugfixes as well. So, if you’re running a site based on wordpress it’s time to update. It’s really a fairly painless process. I do recall upgrading ONE site to 2.0.3 and it was quite painFUL…. things went quite wrong and I had to restore the database from a backup. BUT… I’ve now upgraded 5 or so installs to 2.0.4 without a hitch. (One was a 2.0.3 install and the others were (I believe) 2.0.2).
I haven’t yet seen specifics on the security issues, but I did see a mention at SecurityFocus and you can be bet that there will be some people looking for details to see what they can exploit.
For your info (and my future reference)…. here’s the way I tend to do these upgrades. Open up a tab with the main site page (domain.com) and a tab with the admin page…. open a ssh session to the ssh console of the site.
Next…. my host has a tendency to force most commands to be interactive which drives me nuts. alias cp=’cp’ is the first thing I do…
then …
wget http://wordpress.org/latest.zip
unzip latest.zip
mkdir backup
cp wp-config.php ./backup
cp wp-content ./backup -r
Now…. we’ve got everything unzipped to a directory called wordpress (it just defaults to that) and I’ve got everything backed up that I really need. (Database backups are handled by a cron job…)
OK – in the admin page go to the plugins and disable everything.
NOW back to ssh
cd wordpress
ls (just to see what’s there….)
cp * ../ -r
Now go back and re-activate plugins. In the case of a database upgrade it will say you’re database needs upgrading click here…. next page gives a link to click and that’s all. Then it asks if you really want to activate plugin “” (it forgot what we were trying to do in the midst of the database upgrade.)
It takes you back to the plugin page – nothing has been enabled yet – you can go through and activate what you had previously. Refresh the main site page (to make sure all looks good.)
Then you can cd .. in the ssh session and rm latest.zip and the temporary wordpress directory.
It really makes for a relatively quick process. (5-10 minutes/site?)