Please Upgrade To WordPress 2.6

WordPress 2.6 was released today and features lots of great new features (see following video). Unlike WordPress 2.0.x (2.0.11 currently) but like the 2.1.x, 2.2.x, and 2.3.x branches, the 2.5.x branch is now unsupported and will not be updated with new security patches. You should not put off updating. There is nothing to be scared of and it is unlikely any of your plugins or your theme will break. So do yourself a favor and upgrade!

One of those features is the default Gravatar picker I helped write. If you are a theme developer and wish to add your own default Gravatar to the list, check out my previous post.

11 thoughts on “Please Upgrade To WordPress 2.6

  1. “2.6 is pretty much identical to 2.5 from a plugin and theme compatibility point of view” – actually WP 2.6 is NOT compatible with the K2 theme, the sidebar manager is not working. Consider it before upgrading.

  2. Just upgraded to 2.6 and all the posts give 404 errors. Even if I click View Post in the admin interface, still returns a 404. I disabled the collapsing archives and the other plugins, still nothing happens….

  3. Please, Do Not Update… not yet tho.

    WordPress 2.6 has a problem with permalinks not working.
    Just checked over a local wordpress install, so i’m sure it isn’t just me.

    WP Fast paced releases are making it look like Microsoft patchy Service Packs.

    Have to wait to 2.6.1 to fix this.. I’m keeping my 2.5.1 release till then.

    Silla!

  4. There is also a major issue with users not being able to log into their blogs once the upgrade is done – and there is no fix for that available yet.

    I suggest NOT upgrading at this time.

  5. Snoskred on July 18th, 2008 at 8:38 PM wrote:

    There is also a major issue with users not being able to log into their blogs once the upgrade is done – and there is no fix for that available yet.

    That only occurs in a very small number of users (I upgraded about a dozen client blogs and all worked fine). Even then, clearing your cookies I hear fixes the problem (although I could be wrong).

    EDIT: Yep, deleting your cookies will solve the problem (assuming it’s not plugin related). This is due to a change in how the WP cookies are set and old cookies colliding with new cookies.

  6. Actually no – if you read the comments on my blog post on the topic, you will see that for some the cookie clearing solves the problem, but not always.

    There is also a long thread on the subject in the wordpress support forums.

    The bottom line is, why put your blog at risk by upgrading when there is no great need to do so? Stick with 2.5 or lower until they sort out these bugs (and there are others including a major permalink problem) and upgrade when they have a fix for things.

Leave a Reply to Viper007Bond Cancel reply