WordPress 2.0 Final is Here

I just did an update on my local WordPress subversion trunk and noticed the version had been updated to 2.0. No more release candidate, this is the final 2.0 WordPress release. Not many changes between 2.0-Final and RC3. I think there were maybe a total of 15 files that had any changes to them, if that many.

The WordPress.org site is down for the time being, displaying a message:

Switching servers, please check back in about a half hour. Thanks! – Matt

Probably getting ready to announce WordPress 2.0 on the site. Congratulations to the WordPress team on another fine release.

WordPress 2.0-RC3

So, I didn’t post for WordPress 2.0-RC2, although there was a far greater number of changes in RC2 than there is in RC3. But, RC2 is history now, so screw it. Sounds like this could be the final release candidate before WordPress 2.0 is officially out of beta and ready for “production” use.

The next release of WordPress is drawing near. Please help us shake out any last remaining bugs by downloading and testing the 2.0 Release Candidate. If all goes well, the Release Candidate will become 2.0 final. We’re almost there. Download, test, and head over to the Beta Forum to let us know if the Release Candidate is ready for prime time.


I’ve got release candidate 3 running here right now, no problems at all. On a related note, Spam Karma 2.0 informed me of 2.1 being in beta. Can’t seem to find a link to it now though.

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.

More WordPress and some FireFox

UPDATE: Get SK2-WP2Compatibility, a plugin for Spam Karma 2. It fixes the comment count problem mentioned below when using Spam Karma 2 with WordPress 2.0. OK, just wanted to get that out in the open. Please continue.

Now that I’ve spent a little more time with WordPress 2.0 RC1, I’ve discovered a plugin compatibility problem that’s probably going to destroy me. Spam Karma 2 causes some problems when updating the “comment_count” value in the “wp_posts” table. It doesn’t just cause problems displaying comment numbers, I had to manually updated that field for some posts. But, it’s not like this type of thing wasn’t expected. I’m not brave enough to run slackware-current on my main workstation anymore, this works for me though.

So, I can either use Spam Karma and not have any comment counts for new or updated posts, or I can just stop using Spam Karma. I really don’t want to let Spam Karma go. I’ve already seen about 200 trackback/comment spams since disabling Spam Karma earlier today. I really hope to see a new release of Spam Karma that works with WordPress 2.0. I guess this problem was known about a few weeks ago. I somehow didn’t notice it when I upgraded to 2.0 beta 1 and then to 2.0 beta 2.

Anybody know of a comment/trackback spam WordPress plugin that’s known to work with 2.0? There’s the list in the support forums, which also happens to discuss the Spam Karma problems. I may see if the latest WordPress Hashcash will work at all.

There is good news though, not really relating to WordPress though. FireFox 1.5 stable is out! You can get FireFox 1.5 at the new official home of FireFox and Thunderbird, Mozilla.com.

Also, my favorite Mint Pepper has been updated to work with Mint 1.23. I was thinking of downgrading to Mint 1.14 just so I could have the Outclicks Pepper. Andrew Sutherland couldn’t have picked a better time to release his updated pepper.

CONTINUED UPDATE: Too bad I didn’t see this about an hour ago. Looks like I’ll get to keep my Spam Karma thanks to SK2-WP2Compatibility, a plugin for Spam Karma 2.

SK2-WP2Compatibility is a plugin for Spam Karma 2. It has no effect without Spam Karma 2.0 or higher being already installed on your WordPress system.
This plugin has no spam fighting or spam killing abilities. Instead, it is intended to provide a way by which all users moving to WordPress 2.0 can enjoy the benefits of Spam Karma – without having to worry about WordPress 2.0 specific changes.

Might not need that SK2 plugin for too long, there’s word of a Spam Karma 2.1 soon.

WordPress 2.0-RC1

WordPress 2.0 Release Candidate 1 is here. I don’t have any official links or anything, I haven’t even seen a mention of it on the mailing list. We’ve had one WordPress 2.0 test release each week for the last three weeks now. I like it. Only way I know of to grab it is via subversion.

I’ve noticed something weird in 2.0 Beta 2 though. It may have been there in Beta 1 also, may still be in RC1, who knows. None of my tags show up on Technorati or anywhere. And I also noticed there’s no data in the “wp_postmeta” table relating to the freshly published post, like there should be. So, after publishing the post, I’m taken back to the “write post” page. Only, the “write post” page doesn’t finish loading for a couple minutes sometimes. Previously, I had just navigated away from the loading page without giving it a second thought. I decided to wait for it to finish tonight. After loading, all the tags I had set for that post were in their proper places in the “wp_postmeta” table.

There were some pretty odd circumstances with that post though. For one, I set the posts date/time to about 3 minutes out from where I currently was. After I published the article, it took about 3 minutes to show up here. That behavior is totally expected though. WordPress is good like that.

Also, there were some values in “wp_postmeta” I had never seen before. I didn’t write em down, if I seem it again soon I’ll make a note. All I know is the “meta_key” value was set to something like “_ping_me” or something similar to that. After the post had published, the unknown “meta_key” value had been deleted and my tags were in their proper place in that table.

Now, I don’t know if this behavior is always there when post-dating a post, but it seemed like the ping services (in “wp_options” table) were actually being pinged while the “write post” page was loading right after I had published.

Who knows, maybe it’s all coincidence. Time will tell. Oh, and before I forget, PHP 5.1.0 broke WordPress and lots of stuff for me, and lots of others as well. Tried upgrading to PHP 5.1.1 today, same broken shit. Pages load blank the first time around, second time they load perfectly. I’m sticking with 5.0.x for a while. Soon to be moving to MySQL 5. I’m pretty sure I don’t have to pay for MySQL 5, I gotta research that a little first. I assume I can because the .tar.bz2 source is where it should be on dev.mysql.com.

OK, time to upgrade to WordPress 2.0 Release Candidate 1 before bed. I gotta say though, I love the new dashboard. It’s got a Web 2.0 feel to it, but nobody knows what Web 2.0 is. So, I’m gonna take a chance and say “I really dig the new half Web 2.0 WordPress.”

UPDATE: OK, all updated to 2.0-RC1 now. You should ignore everything above this update pretty much. The problem I spoke about earlier isn’t related to WordPress, don’t hold me to that though. I did some more testing before upgrading to 2.0-RC1. I think it’s some odd plugin functionality. I’ve been using Jerome’s Keywords for tagging. Every time I edit a post the tags get wiped. I know that’s the general problem. I don’t know if it’s caused by the plugin or if it’s WordPress wiping out all the “custom fields”. Jerome’s Keywords stores its tag data in those “custom fields”, inside the “wp_postmeta” table.

You can get WordPress 2.0-RC1 in the nightly builds directory on the wordpress.org server.