WordPress 2.2 Adds Tags

The NeoSmart Files noticed the addition of native tagging support to WordPress 2.2 in the SVN repository. What’s this mean for WordPress bloggers? Not much really, other than the fact you’ll no longer have to use a third-party plugin for tagging your posts or pages.

This is great for WordPress, tagging is something I expected to see with the release of 2.0, but that didn’t happen. Tags are something bloggers really want, native tags will just make WordPress an even more attractive blogging platform.

I’m going to have trouble leaving the Ultimate Tag Warrior plugin behind in favor of the new tagging system in WordPress 2.2. Ultimate Tag Warrior has been so nice to work with and is pretty much the de facto WordPress plugin for tags. Ultimate Tag Warrior has some features not found in the tag system native to WordPress 2.2, such as tag suggestions. Also, Ultimate Tag Warrior allows you to apply tags you’ve used previously to a post via a select form, something not found in WordPress 2.2 tags. Hopefully the WordPress team has those features planned for inclusion at some point.

Anyway, head over to The NeoSmart Files for more, they have a screenshot comparing Ultimate Tag Warrior to native tags in WordPress 2.2.


WordPress 2.1 Release Candidate 2

WordPress 2.1 Release Candidate 2 is out, roughly two days after RC1 was released. I’ve been keeping up to date with 2.1 releases since beta 2. You can download 2.1 RC2 here.

The only plugin I’m having trouble with in WordPress 2.1 is the FlickrRSS plugin. Ultimate Tag Warrior also had problems with WordPress 2.1, although I didn’t experience any of them. Ultimate Tag Warrior wasn’t slightly broken, it was trashed, and would delete tags for posts. Here’s what the guys at NeoSmart had to say:

Ultimate Tag Warrior is completely broken with WordPress 2.1 and you can lose all your tags by upgrading to WordPress 2.1. In the more recent SVN revisions of WordPress 2.1, any time a comment is added, deleted, or unapproved, you lose all the tags for that particular post.

Thankfully, Christine, the Ultimate Tag Warrior author, has released a new version of UTW that’s compatible with WordPress 2.1 (I think). I believe the new release implements a fix that was published for the UTW/WP2.1 issue back in December. There still seems to be some speculation over weather or not version 3.1415926 of UTW fixes all the problems with WordPress 2.1. I never had any problems with UTW and WordPress 2.1, even with versions prior to 3.1415926. Sounds like the problem may be somehow related to Akismet from the discussion going on at the UTW forum.


Jerome’s Keywords and WordPress 2.0

I was having some problems with my keywords getting deleted when updating a post (using Jerome’s Keywords 1.8). The problem was a result of a blank textarea on the page to edit a post. Wasn’t hard to fix at all.

The textarea, with a header of “Keywords”, shows up blank when editing a post. The initial post is good because that text area is filled out manually. jeromes-keywords.php was using “$postdata->ID” as a reference in the get_post_meta() function. $postdata->ID didn’t contain any value at all.

After doing a little digging, I found I could get a posts ID using $post->ID, notice the missing “data”. It only takes a few steps to get Jerome’s Keywords working 100% in WordPress 2.0.
1. Open wp-content/plugins/jeromes-keywords.php in a text editor.
2. On line 553, change the line that says “global $postdata, $content” to read “global $post, $content”.
3. On line 555, change “get_post_meta($postdata->ID, KEYWORDS_META, true)” to “get_post_meta($post->ID, KEYWORDS_META, true)”.
4. Save jeromes-keywords.php, you’re done.

After doing that, the keywords textarea created by the plugin will be populated with your original keywords. I guess that textarea must have the keywords there all the time, even when editing. Before, my keywords weren’t in the “keywords” textarea, they were only in a custom field.

It appears that Jerome’s Keywords deletes post meta every time that post is edited. And I think that’s the desired functionality for some reason. I only say that after looking at the code for a half hour or so. I think the post would end up with one custom field named “keywords” for every time the post is edited or updated. So, update a post 4 times and you’ll have 4 identical custom fields named “keywords”.

All of my favorite plugins are now working very well for me with WordPress 2.0-RC1.