The WordPress team has released a maintenance update to the WordPress 2.6 branch. This release includes several improvements for international users, it also fixes permalink problems faced by blogs hosted on IIS servers.
This release does not require a mandatory update, so you can continue using WordPress 2.6 if you are happy with it, although you may want to upgrade to this release if you have been facing any of the bugs that were fixed in this version.
[…] nello sviluppo del loro ottimo prodotto e in questa giornata di festa fanno uscire una nuova minor release 2.6.1 che […]
[…] on: Aug/15/08 and its been viewed 1 times WordPress version 2.6.1 was released yesterday – this blog has upgraded. This is not a mandatory or security upgrade at all – you’re safe not to do the upgrade, if you don’t want to (doesn’t it feel like we JUST upgraded to 2.5 …then 2.6..now…? haha). It’s more of a maintenance update, as reported by Keith @ WTC. […]
[…] is now up to version 2.6.1 therefore, I shall update! Expect downtime, errors, spoke, fire, swearing, destruction, […]
[…] minor maintenance update has been released for WordPress. The non-essential update addresses a number of things for […]
Obviously Powered by WordPress. © 2003-2013
that’s great,thanks~~~
Oddly, the notice that an upgrade is available only appeared at the top of one of my blogs that I run with WordPress. The other two don’t show anything, and that means that the plugin I have to upgrade it for me doesn’t recognize that there’s a new version out there. It’s very strange.
Wow that was fast. It feels like I just installed 2.5, and then shortly after 2.6 and now 2.6.1 already. While it’s not a major release, I did find one compelling reason that people may want to upgrade:
“Links not reassigned to default category after category deletion” <– this bug was just fixed in 2.6.1
Ten minutes ago I just setup my new blog with WP 2.6, now I’d like to upgrade it to 2.6.1.
Maybe I am going to upgrade all of my blogs, Thanks to WP team.
Seems that I still happy with my WP2.6.
The release of WP this time was so fast isn’t?
Slowly moving along towards 2.7. I can’t wait.
Would anyone know how to fix this problem?
When I upgraded to 2.6 and i go to one of my tag pages, and if you click on it, i get a “sorry, nothing here blank page.” any suggestions? i put in a sample link below… its driving me crazy…
http://laberintosocial.com/tag/free-search-code/
I’ve done updating my blog into WP 2.6.1
Seems likes no different (although the official founder says there was sixty minor bug-fixes)
I’ve just migrated my other blog to wordpress and installed wordpress 2.6. Now, I’ve upgraded that blog wordpress version to 2.6. Keep it up. 😀
How I wished I didnt upgraded to 2.6, or even 2.5. Now I can’t use EmbedIt. 🙁 Any other alternatives to embed javascript codes on WP?
I wish WordPress had the ability to know whether or not the update is mandatory. I don’t plan on upgrading to 2.6.1 but I really would like to get rid of the banner at the top telling me I’m not using the latest version. If WordPress was able to understand that somehow then it wouldn’t be telling me to update my WordPress install when the update doesn’t include any security fixes.
Poop. I hate having to upgrade WordPress so darn often. But I guess it’s good that they’re actively developing it.
Wow,
I just upgraded my 2.5 to 2.6 the other day and when I logged in to my panel it says there’s a new 2.6.1 upgrade!
Definitely upgrading for sure! At least, I know i’m getting the latest release and bugs are fixed.
Keep it up wordpress!
I just upgraded from 2.51 to 2.61, and when I log in all my content is gone and I’m seeing a brand new blog. I did a database backup, so it’s not really gone … but 2.61 thinks it is. (I did every upgrade from 2.1 to 2.51 … but may not have been ‘merging’ wp-config … which I did this time.)
I tried to merge my old wp-config with the config-sample, per instructions … this is the only area to get hand-editing. I’ve repeated several times now.
Anything known to cause this symptom? Thanks!
I’ve restored my blog-content. I had changed $table-prefix in wp-config.php to an incorrect value. Works much better with the right prefix! 😉
I am finding it impossible to upgrade from 2.5 to 2.6. My hosting is on Go Daddy – all the sites on Network Solutions upgraded without a problem. But when I upgrade to 2.6 on the Go Daddy hosting account everything seems to go well until I have to log back in after the installation. The old password does not work and I request a new password. That doesn’t work either – so I have had to go back to 2.5 just to get the site to display. Any ideas? Thanks, Chief
Chief – Are you seeing the error msg: “”Sorry, that key does not appear to be valid.”?
If so, that is due to a know bug (search with that string for more info on the bug), and there are several work-arounds. The following solution by “Otto42” is posted on the WordPress forum, and it worked for me.
****
Easiest way to reset your password:
If you can’t login, but you can access your site via FTP, then edit the theme’s functions.php file and add this code to it, right at the top after the first <?php bit:
wp_set_password(‘password’,1);
Put in your own new password for the main admin user. The “1” is the user ID number in the wp_users table.
After you then login, make sure to go back and remove that code. Don’t leave it there by any means.
****
Hope that helps.
Ted
We just installed wordpress a few months ago on our site and already have done two updates, not counting plugin updates. I’m glad WordPress is trying to stay ahead of the hackers. That is why we chose them for our CMS.