WordPress Upgrade Month
It’s starting to look that way. Since I wrote a couple of weeks ago about the WordPress 2.0.6 upgrade, WordPress 2.0.7 was released on Monday. It’s not labeled as a mandatory update, but it’s recommended (and it’s a piece of cake if you’ve already installed 2.0.6). The next major release (2.1) is supposed to be just around the corner (22nd of January).
Last time, I mentioned that 2.0.6 required a little more upgrading work than usual, but that’s only for folks who use Steve Smith’s FeedBurner Plugin and have WordPress installations on Apache servers running mod_php. Mark Jaquith described the issue and offered a fix. WordPress 2.0.7 includes the fix, so if you’re using the latest version of FeedBurner Plugin (2.2) and upgrade to WP 2.0.7, then there shouldn’t be a problem.
If you’re not using FeedBurner Plugin 2.2 but an older release, it’s a good idea to upgrade. It has a number of advantages over previous versions, and also makes it easier to burn your blog’s comments feed. Also, the new version does not create/maintain a special RSS feed, but simply uses the standard WordPress feed links. If you use “pretty” permalinks, the standard feed might be
http://yoursite.com/subdirectory/feed/, for example. Upgrading to 2.2, you’ll also have to update the .htaccess to remove the old FeedBurner redirects.
Once that’s done, log into your account at FeedBurner.com and change your feed’s source from the old, special random-number feed to the standard RSS feed of your blog. To check that everything’s working, just browse the URI of your standard feed, and it should redirect to the FeedBurner output.