WP 2.0.2 and semi-SVN

BOK • 11th Mar 2006 • Blogging, Technical, Blogging, WordPress

Because of yet unannounced XSS issues (XSS: cross site scripting), a security release of WordPress was released yesterday, so I upgraded to version 2.0.2. Because an automated upgrade-script is (still) unavailable I hereby reveal the basic way of how I do this myself.

First I create a backup of both my weblog-database (through the database backup plugin) and directory-tree, followed by the deletion of the “old stuff”:

cd $HOME/WordPress/
tar zcf BACKUP-20060311.tgz /path/to/your/weblog/

cd /path/to/your/weblog/

cp wp-config.php /tmp/
rm wp-*.* readme.html wp.php xmlrpc.php license.txt
rm -rf wp-admin/ wp-includes/ wp-content/cache/

In the meantime I had the new WP-tarball (or ZIP-file if you download that one) downloaded and extracted in my $HOME/WordPress/-directory, so I could easily copy all the new stuff over and change the rights to the web-owner:

cp -p -r $HOME/WordPress/wordpress/* .
mv /tmp/wp-config.php .
chown -R www:www *

Easy peasy Japanesy!
But oops… I deleted some PHP-scripts needed for plugins in /wp-admin; thank God for that backup-file I made!

I also tried to get to the latest version of the K2-theme from SVN (“subversion”, a sort of developers repository), but just for one special theme only I don’t feel like installing a whole bloat of software on my box, so instead I pulled the latest tree from the SVN-repository and installed it in the themes-directory:

cd $HOME/WordPress/themes/
mkdir SVN ; cd SVN
wget -r -np http://getk2.com/svn/        // "-r" = recursive, "-np" = no parent
cd getk2.com/
mv svn k2betatwor217
mv k2betatwor217 /path/to/your/weblog/wp-content/themes/
chown -R www:www /path/to/your/weblog/wp-content/themes/k2betar217

Afterwards in the file “functions.php” I changed the $current-entry that shows the revision-number into the one I leeched (see the footer of this page).
Maybe not the way it is meant to be, but for the moment I don’t really care…