Meta

A Quick Review

I’ve only had the new version of WordPress up and running for about 24 hours, but I really like it. The dashboard is nice and clean. It runs faster. Things like the category checklist are much handier than in the last version I had installed. Before, the it was toward the bottom of the page, which meant I’d forget to add categories, so I’d frequently have to go back and edit posts after publishing.

This is my first experience with using widgets in WordPress, since they weren’t supported in my previous version. Being able to drag and drop modules into the sidebar, instead of having to copy and paste and tweak code, is pretty awesome.

Another thing included in this version was built-in gravitars. I have unleashed the cute monsters (!), so if you comment and don’t have your own gravitar, you’ll be assigned a little monster.

Assuming things stay nice and stable, the improvements were well worth the pain in my ass of upgrading.

Meta

Wheee!

I got up this morning, checked my email, and there sat a spam message for an old post. (You have to turn off all your plug-ins before upgrading WordPress, including your spam-catchers.) Surely this meant that the blog was back up and running?! Yes, indeed! My web host’s little elves seem to have fixerated everything overnight.

Praise be!

And now, I’m off to look for a new template. I’m tired of the old one, especially the lack of white space, but I haven’t been motivated to change it, since I knew I needed to upgrade WordPress. I didn’t see any sense in doing cosmetic surgery when there were some serious underlying health issues.

So, now I’m off to do the fun stuff! This means that things might temporarily look funny or there might be short periods of inaccessibility.

(Yes, I was happy to get blogspam!)

Crankypantsing, Music

While Waiting in Limbo

I think my web host may help with upgrading, but I don\’t have time to mess with it right this minute. But if things go wacky, that’s probably why.

In the meantime, my teeth have finally (mostly) stopped hurting. I had a filling replaced (minor) and a broken molar repaired (major) on Friday, both on the same side. They didn’t hurt too badly after the Novocain wore off, but on Saturday they hurt like hell. Even on Tuesday morning, as I was trying to eat room temperature oatmeal, they hurt. Hrmf. Then, at some point Tuesday afternoon, I realized they weren’t hurting. Huzzah! I guess it just took a few days for the nerves to calm down.

I’m still getting occasional twinges and brief moments of throbbing, but nothing like it was. Both teeth are still really sensitive to cold, which is a bummer, but definitely an improvement. Hopefully that’ll go away, too, and preferably before Popsicle season is over!

Crankypantsing, Meta

It Just Keeps Getting Better

And by better, I of course mean worse. Much, much worse.

The Esther blog, which I upgraded successfully last weekend, is now broken. It’s apparently something to do with the database, which totally does not surprise me, but if that’s what it is I don’t understand why it worked for a couple of days. Very weird!

Looking at the database, and assuming I’m interpreting it correctly, there seems to be the same problem with the comments table that I had when trying to upgrade the main blog. And, of course, I can’t restore from a backup on the server, because the oldest available backup is Monday’s, and that was already corrupted. WTF?! Whatever happened happened between Saturday and Monday.

That isn’t a huge deal, I guess, since that blog just functions to let interested people know when there are new letters. I figured folks could subscribe to the RSS feed and it would make it easy for anyone interested in following along to know when there was new content. Which is a long way of saying, I can start over from scratch there without any problem. Assuming I can get WordPress to work out of the box. I didn’t have much luck with that the last time I tried it.

The crap with the main blog is even more annoying. I’m back where I started from, with what seems to be a more or less functional install of WPv2.6. I need to upgrade to WPv2.8.1. If I try to do it all over again, I’ll just recreate the mess I made on Monday morning. I have no idea how to proceed. I asked tech support if I could just upload the v2.8.1 files to my directory, then have them do the database upgrade. I’m betting they tell me “Hell, no!” Really, though, it would save them (and me, obviously) a bunch of time, trouble, and confusion.

All that said, since the upgrade of the Esther blog has now gone kerplooie, I’m at a total loss as to what to do. Even if we get the new version of WordPress up and running, will the database become corrupted after the fact?

Crankypantsing, Meta

Okaythen

We’re back where we started from, which is way better than losing the whole shebang, but kind of annoying nonetheless.

I’m not sure what I’m going to do, because WordPress really does need to be upgraded. This version is horribly insecure. But if I try to upgrade again, I’ll be back in the same mess I was in yesterday. Grrrr. At this point, if tech support can’t help me figure it out, I’m half tempted to install a fresh copy of WordPress on another subdomain, import everything into it, then wipe this one out completely and start over from scratch. Then, import everything back into this installation. What a pain in the ass! There has to be a better way to do this, but I’ll be damned if I can figure it out.