WordPress development team has decided to skip the scheduled 2.4 release that was due on January 24 and move straight to 2.5 release. I guess after releasing 2.3.2 we can’t blame them and I’m quite greatful for this break. It gives us, bloggers using this superb platform a window of time we can use to have a harder look at our blogs…

So what exactly should you do right now? A hundred bucks question and perhaps this post will serve as an answer…

WordPress 2.3.2 released and this time around it addresses several security issues as well as bug fixes. You can read more complete details on what has changed with this release here but this is not what this post is about…

Once again I want to provide a complete set of changed files and detailed info on proper upgrade…

Almost a month since initial release we have finally received a long expected bug fix update. But looks like WordPress 2.3.1 addressing more then just a few bugs but also a security issue. While that security problem only impacts people whose host still have register_globals enabled (shouldn’t be too many) it is still worth updating.

There is much already written on the topic and but one of the best ways to learn is to hit one of the sources. Peter provides all the details on what is been addressed in this release and reading through his blog it appears that at least some of the enhancements slated for 2.4 release made it in here as well.

I have taken a leap and performed an upgrade of my blog to WordPress 2.3. I wish I could say everything was rosy but unfortunately it wasn’t so. Even with proper preparation and investigation and research there were several things worth noting.

This post is to provide my personal account and perhaps help other people overcome lost functionality due to UTW being discontinued as well as few other things.

As I’m getting ready to release my Web 2.0 Wealth product, [tag-tec]WordPress[/tag-tec] team sprang on me a new upgrade to the blog system. While I have already updated final package with new version – there is no need to replace everything you your blog.

This is a minor release and can be done on live blog incrementally! Make sure you backup your files and database first from your cPanel and then proceed with upgrade of WordPress to 2.2.2 version using [tag-tec]video tutorial[/tag-tec] presented in this post.

I have received several emails as result of my post on upgrading WordPress to latest version 2.2.1. As I have mentioned in my previous post – in my experience of upgrading live blog from version 2.2 to the latest I didn’t have to update database and all changes appears to be related directly to code within files.

Obviously it raises simple question – if no database upgrade required – would it be possible to simply upload modified files to address issues and implement the fixes? I don’t know for 100% but as a technical person I simply had to investigate. What you see here is a list of files that I have found to be modified and different between 2 releases: wordpress-2.2.zip and wordpress-2.2.1.zip. I have verified that files actually have changes within code and while in some cases it is simple fixes, in some it looks like actual code modifications.