WordPress 2.6.2
WordPress 2.6.2 is a security release which tackles problems with SQL Column Truncation and mt_rand().
Since WordPress 2.6.1 was an optional update—first time in the history of WordPress—is WP 2.6.2 the same way? Here’s the answer:
If you allow open registration on your blog, you should definitely upgrade. With open registration enabled, it is possible in WordPress versions 2.6.1 and earlier to craft a username such that it will allow resetting another user’s password to a randomly generated password.
The dev blog also notes that this vulnerability is also applicable to other PHP-based applications.
Aside from security fixes, WP 2.6.2 contains a number of bug fixes as well.
WordPress MU 2.6.1
In coordination with the last official release of WordPress, WordPress MU 2.6.1 is out. Unlike WP 2.6.1, though, which is a maintenance release, WP MU 2.6.1 is required.
Download the latest version of WordPress MU here.
WordPress 2.6.1
WordPress 2.6.1 is finally out. Here’s a nice tip if you’ve been wondering about when you should upgrade:
With 2.6.1, we’re continuing our trend of releasing a maintenance release shortly after a major release in order to get fixes for the inevitable “dot zero” bugs into your hands without a long wait. If you’re happy with 2.6, however, keep on using it. You need not upgrade to 2.6.1 if 2.6 is getting the job done.
If you’re an early adopter, you probably made the move to WP 2.6 already, and you may not have to upgrade immediately since this is not an urgent security release. If you haven’t, waiting for the “dot one” release ensures a lot more bug fixes than the “dot zero” release. Check out the the list of 60 bug fixes here.
Download WordPress 2.6.1 here.
WordPress 2.6.1 Beta 2
Beta 2 of WordPress 2.6.1 is out. The team is approaching 60 bugs fixed for the official 2.6.1 release. You can the new fixes since beta 1 here.
WordPress 2.6.1 Beta 1
WordPress 2.6.1 Beta 1 is out. You might want to grab it now, or wait until an official release arrives, which Ryan Boren says will arrive around the time of this year’s WordCamp San Francisco.
Here’s another tip from him:
With 2.6.1, we’re continuing our trend of releasing a dot one release about a month after dot zero. We want to get fixes for the inevitable dot zero bugs into your hands without a long wait. If you’re happy with 2.6, you can ignore 2.6.1.
There are over 50 fixes, a lot of which address the typos in code and major bugs—like the 404 error that turns up when your permalink structure is /index.php/%postname%/.
