The folks on the WordPress team have released version 2.0.5 of the WordPress Blogging Application. This release includes around 50 bug fixes one of which was a missing index on the posts table. I just upgraded and the site performs much better now. I had always thought that the site ran a tad bit slower after the 2.0 upgrade, but for some reason I just figured 2.0 was doing so much more than the 1.x versions. Didn’t even think of looking at table indexes.
Mark Jaquith has also put together his list of change files and corresponding archives containing only the changes from 2.0.4 to 2.0.5, along with a patch file to upgrade your stuff directly. I opted to download from the WordPress site.
In any event, according to the release announcement, there are some security fixes in this release as well. As I do with every release of WordPress that contains security release, I am reminding you not to be lazy and get your site upgraded as soon as you can. The performance improvements alone are worth it.
Now … off to see if they fixed that “posting from Flickr mangling CSS thing” …
The WordPress team has released version 2.0.4 of the WordPress blogging software. From the release notes:
This release contains several important security fixes, so it’s highly recommended for all users. We’ve also rolled in a number of bug fixes (over 50!), so it’s a pretty solid release across the board.
This release contains security fixes. As I continuously remind everyone since being hacked, don’t be lazy on these upgrades!
Needless to say, I’m done.
The WordPress team has released version 2.0.2 to address some security issues with 2.0.1. You can get the full story over at the WordPress blog, or go directly to the download area and grab it. Remember, don’t be lazy.
I am continuing to work on the site and its migration to WordPress 2.0. Along with the upgrade of the main site, I’ve had to upgrade the following items:
- Ultimate Tag Warrior – I have upgraded this to version 2.8.9 to remove an error in the admin screens
- FAlbum (Integrated WordPress / Flickr Photo Album) – I have upgraded this to version 0.5.6. Along with getting everything to work properly, this version also gets rid of those missing images you saw in the photo album due to Flickr changing its URL scheme. With this work completed, the integrated photo album is now back up and running.
Right now, I think everything is working properly except for the comment issue when “wordpress” is in the permalink. If you find anything else broken, please let me know. I will continue to test over the next week or so.
Incidentally, the WordPress team is planning to release the official 2.0 release on December 26. Once that happens, I’ll go through the excercise again to ensure that I am on the most current version.
Overall, I think the WordPress team did a great job with this version of the software. For some additional information on WordPress 2.0, you might want to hit the following articles written by Owen Winkler:
I found that if permalinks are on and the post-slug contains the word ‘WordPress’, the comments section would not appear on the post. I have submitted an issue to the WordPress team.
If you notice, I have changed the word ‘WordPress’ in each of the slugs to ‘wp’ and they work fine. An old post with WordPress in the slug can be found here. Notice – no comments section.
Obscure issues like this is why I don’t mind installing beta software in my production environment. Chances are, if you don’t run it for real, you won’t find this stuff.
It looks like Apple has released a podcast server solution for its OSX Server product.
I decided to upgrade the site to WordPress 2.0 to see what the new version looks like. Currently, I’m having some problems with permalinks and some plugins may not work. I will continue debugging later on in the next two weeks. One thing I will say is the new version looks great.
The main problem (that I know about right now) is that it seems as if the comments do not work on posts since the upgrade. For some reason, on newer posts you just cannot get to the comment template. I’m currently tracing through that to figure out what the deal is.
As I get the bugs worked out, I’ll post up the details of what I’ve found.