WordPress developers has just released the long-awaited fourteenth release of WordPress, WordPress 3.1. Code named “Reinhardt” in honor of the jazz guitarist Django Reinhardt. “With the 3.1 release, WordPress is more of a CMS than ever before,” claimed project lead Matt Mullenweg in a release statement.
WordPress 3.1 has mostly bug fixes with many new features. There were over two thousand commits to the codebase in the 3.1 cycle and more than 820 closed issues in Trac. Interested users can visit the WordPress Codec for an in-depth overview of all the features that are added, improved or changed in the recent release.
WordPress 3.0, codenamed Thelonious, has just been released by WordPress and is the thirteenth major release of WordPress. WordPress 3.0 Beta releases have been available for the last few months, but now the final version is released officially.
Among the features listed in the official blog post: a new default theme called Twenty Ten, new lighter interface, and 1,217 bug fixes. Theming has gotten a bit of attention, with APIs that make it easier for theme designers to allow for customized menus, post types, headings, backgrounds, and more.
WordPress 2.9 has now been updated to 2.9.1. This upgrade will take care of many bugs that were found in the earlier version. Some of the bugs that were found in 2.9 and which are taken care of in the latest version 2.9.1 are as follows:
- could not be converted to UTF-8 / WordPress should cache failed feed fetches so as to avoid overloading feed sources
- cron stopped working with standard configuration
'$wpdb' typo in
wp-admin/maint/repair.php causing table prefix not to appear
- Upload Handling. Use
is_numeric instead of
- Need confirmation/undo/something for media delete
I took a small break of half an hour from my studies to quick post this big news! :)
The WordPress development team have released WordPress version 2.9 “Carmen”named in honor of magical jazz vocalist Carmen McRae which can be downloaded from the official WordPress website. WordPress users who have configured automatic updates can also upgrade to WordPress 2.9 from within their blogs. As always, it is recommended to backup the files and database before initiating the update.
The new version comes with over 500 bug fixes, changes and enhancements which makes it a recommended download and install.
The WordPress developers have released a security update for their blogging platform WordPress, now raised to version 2.8.6. This security release version fixes two vulnerabilities relevant to multi-author blogs. These exploits can only be exploited by registered, logged in users with posting rights. If you have untrusted authors on your blog, upgrading to 2.8.6 is recommended. It is always recommended to update to the latest version of WordPress as soon as possible.
The first problem is an XSS vulnerability in Press This discovered by Benjamin Flesch. The second problem, discovered by Dawid Golunski, is an issue with sanitizing uploaded file names that can be exploited in certain Apache configurations. Thanks to Benjamin and Dawid for finding and reporting these.
WordPress 2.8.5 “Hardening Release” is released now. WordPress recommends every site to upgrade to the latest version. According to the WordPress Blog,
We have also been working on trying to make WordPress as secure as possible and during this process we have identified a number of security hardening changes that we thought were worth back-porting to the 2.8 branch so as to get these improvements out there and make all your sites as secure as possible.
A new version of the popular blogging platform WordPress was released just a few minutes ago. It is an unexpected upgrade considering that the last WordPress update was less than two weeks ago. The new update fixes a security vulnerability that affects all but the latest version of WordPress.
This update fixes an XSS vulnerability which could be used to create comment author URLs that would redirect the system administrator away from the blog’s website to another website for security exploit. All WordPress webmasters are encouraged to update their blogs as soon as possible to patch the security vulnerability and should not ignore this update.