Or, README twice, click ‘upgrade automatically?’ once.
I knew — somewhere, just not front and center — that the auto-upgrade feature of WordPress would overwrite any code you may have inserted into the ‘classic’ or ‘default’ themes.
I knew that.
I think I have backups around here, somewhere
I upgraded the site to WordPress 2.3.1 and seem to have walked upon my previous tags scheme. Hmm I followed (I think) Andrew’s directions, but the old tags do not appear. Sluthing is required
Under WordPress 2.1, Ultimate Tag Warrior (for now) is misbehaving, eating tags and such, but Donncha has the centralized info on how to fix things. You should upgrade WP-Cache to version 2.0.22 as well.
Weblog Tools Collection points to Circle Six’s DiggProof your WordPress which is really about optimizing and tweaking your mySql database for WordPress.
Via WordPress’ dashboard I see that WordPress 2.1 is out.
WordPress 2.1 “Ella”
On behalf of the WordPress.org community of commiters, contributers, and volunteers, I’m very proud to announce the immediate availability of WordPress 2.1 “Ella”, named for jazz vocalist Ella Fitzgerald. [more including listing 19 big new features and over 550 bug fixes]
I only have one question, what’s a “commiter?” Are am you me us one?
[Later:] Yeah, that’s immature and snarky. Unless commiter is someone who commits changes to the the code? I dunno
[Immature and snarky stuff deleted because it was, well, immature and snarky.]
[Later later later:] OK, that makes sense. Thanks, Scott.
Anyway, one blog updated without (apparent) breakage. Thus far.
OK, I did hose my Ultimate Tag Warrior tags, but that wasn’t Christine’s fault. I did that meself, to meself. Oops. And they aren’t important enough (IMO) to me to resurrect them from the backup.
Whoops! Wrong plugin. It seems I was using Andrew Grant’s Keyword Tags so the keywords automagically reappeared.
[Later later:] The various admin pages, most especially the ‘Dashboard’, seem much, much faster to load.