Better read this announcement immediately if you’ve updated to 2.1.1 within the last few days. It’s quite likely you need to go to 2.1.2 asap as the security on 2.1.1 was compromised.

This security hole does NOT apply to people still on 2.1 (but I imagine if you were planning to upgrade, you should go directly to 2.1.2…).

Those busy folks are at it again…just installed another update. This one apparently comes highly recommended with security fixes and the like. As usual, I used Mark on WordPress’s zipped diff file. No fuss, no muss…

They’ve been working overtime…2.1 was released a couple of days ago and as usual, its best to update as soon as possible. One of the nice things about this upgrade is that it includes the latest Akismet. Which along with Bad Behavior (verified good for 2.1) will help cut your spam right out.

This is a major upgrade, so Mark on Wordpress didn’t create convenient diff files this time. Instead, follow the instructions over at wordpress: Upgrading Wordpress which are clear and straightforward.

All my plugins were fine with the upgrade, and while that of course won’t be true for ALL plugins, chances are you probably won’t have too much issue with that.

So there is yet another update to WordPress (now at 2.0.7), which I urge you to go out and get. If you have 2.0.6, you can get just the diffs to 2.0.7. If you are not up to 2.0.7, I strongly suggest you do so, as many of the updates since the 2.0 release have consisted of security fixes, not just whizz-bang features.

In the same vein, akismet is up to 1.8.1 (although their website gives an earlier version number, I had 1.8.1 after updating). If you have already installed it and are just updating it, all you have to do is unpack the new version in the same plugin directory, you are already set up with your API key and everything (their faq doesn’t make it clear what is involved in updating versus newly-installing, probably because it’s so trivial).

Plus which I use the plugin Bad Behavior for further spam killing (now at version 2.0.9). It works a charm. It’s also been pretty recently updated, so I suggest installing it if you haven’t got it, or updating it if you’re behind.

It’s a few days later, but I’ve upgraded my wordpress installation, and y’all should too. If you’re upgrading (as opposed to installing), you might want to check out Mark at Wordpress’ zipfile of changed files that makes upgrading much easier (and safer in some ways, especially with regard to the wp-content directory) than trying to use the whole enchildada from WP’s download repository.