On the Newest Upgrade

WordPress 2.3 dropped yesterday.

I downloaded the latest version, spent half an hour uploading the new files to my server, and crossed my fingers.

WordPress upgrades have been a mixed bag in the past. The 2.1 upgrade was a miserable experience.

This upgrade wasn’t. I uploaded the files. I ran the update script. I didn’t even turn off my plugins.

Once it was up-and-running, I altered my template files to account for the new tagging functions built into WordPress — both in single-page views and for the tag cloud page. Once those were working, I deleted Ultimate Tag Warrior from the system; it wasn’t needed anymore.

For all the thud and blunder about adding tags into WordPress core, WordPress 2.3 doesn’t ship with any sort of tag management tool. None.

That is mildly annoying.

There at least needs to be a function where untagged posts can take a generic tag, for ease of locating and editing to add tags. Something.

Suffice it to say, the upgrade is done. WordPress purrs like a kitten. The bad memories of January are beginning to fade away… 😉

4 thoughts on “On the Newest Upgrade

  1. Does 2.3 still support the old categories, or is it exclusively tag-based now? (Looking at your footers, it appears so, but I figured I’d ask before biting the bullet. I could backup and restore, but that can get messy where the database is involved. ;))

  2. Andrew, WP 2.3 supports both tags and categories.

    The UTW tag importer works nicely. I don’t recommend using the category-to-tag importer. That one makes a bit of a mess.

  3. I have no interest in using tags at the nonce; categories serve my purposes far better. (Hierarchy is far more useful for sorting my video archive… :)) So, it’s good to know that they’re still supported.

    I’ve just never been much of a tag person; I never installed UTW, so I don’t have to worry about imports. 😉 Maybe if/when I ever get back to blogging, I might start using them. *shrug* I guess I’m just not a Web 2.0 person.

Leave a Reply

Your email address will not be published. Required fields are marked *