Note to self: don’t update the blog after 11PM
Tue 5 Feb 2008, 12:19 am
After I finished that last post, I saw that WordPress has an urgent security release, version 2.3.3. So I deactivated all the plugins and went to work the old svn update magic.
Except that this time the magic was disappearing ink. After the update, the whole blog was nowhere to be seen from the browser, though I could see the files just fine on the server.
At another time, in another mood, I would have taken that as a perfect opportunity to end the blog. But right now, I have notes for a few more posts, so you’ll be stuck with me for a while longer.
So instead, I renamed the blog directory fubarseealso, downloaded a fresh install of WordPress with svn, and copied files from fubar until things looked OK. But if you find anything weird (by which I mean weirder than usual), please do let me know.
- License:
- File under: Blogs and blogging,Navel gazing
- Comments? 2
This is why I am chary of leaping into WordPress emergency updates. A perfect example of “the second mouse takes the cheese.” I’m still suffering from how they goofed up the visual editor a couple of updates ago so that long posts get all furry with their line breaks. I know they’re saying we gotta update NOW but this being the second update in a month or so, I’ll wait for “no really, we mean 2.3.2.1b…”
Comment by K.G. Schneider — February 5, 2008 @ 6:45 am
Surely your plan is wiser, Karen. I can’t say that I love it when things break, but it does always make me feel good to be able to fix stuff when it does break. So it’s almost worth it.
FWIW, the new install for 2.3.3 seems to be working fine, so it was probably bleary me that was the problem, not the upgrade itself. I’m even getting email notifications of comments again. I’m not sure if that is because of this bugfix, or because of my fresh install, but if it took a little nuking to make that happen, I don’t mind.
Comment by Steve Lawson — February 5, 2008 @ 9:41 am