latest update (to 2.3.3) fixes an exploit that may have been used at my own site.
For me, the update process looked like this:
1. ssh to my blog's directory.
2. svn sw http://svn.automattic.com/wordpress/tags/2.3.3
Yea!
How did I miss this? The
For me, the update process looked like this:
1. ssh to my blog's directory.
2. svn sw http://svn.automattic.com/wordpress/tags/2.3.3
Yea!
Comments
but one of my instances isn't, so I had to do it by hand - i essentially downloaded and unzipped the entire 2.3.3 install package, copies up everything but wp-content (to preserve my themes and custom css) and that was enough. I was going to copy around the files I specifically customized, but it worked before then. ;)
If only I'd known being the world authority on Hitler's Favorite Beer would entail such ongoing responsibility.
Edited at 2008-02-11 02:48 am (UTC)
Yeah, what can I say? There's a vulnerability. I'm proud that I made the process of updating trivial. It sucks otherwise.
Oh, to have such mad programming skillz! Then, in addition to painless updates, I could've had a cool job, made lotsa money... and maybe even attracted a hot nurse.
(comment subject to editing to remove "hot nurse" remark)