WordPress 2.8.1 Released

WordPress 2.8.1 was released yesterday and looks like the major reason for upgrading in this case is a new exploit that from my quick reading could be potentially dangerous.  You can find the exploit details here.  Other than that just a standard set of fixes:

  • Certain themes were calling get_categories() in such a way that it would fail in 2.8. 2.8.1 works around this so these themes won’t have to change.
  • Dashboard memory usage is reduced.  Some people were running out of memory when loading the dashboard, resulting in an incomplete page.
  • The automatic upgrade no longer accidentally deletes files when cleaning up from a failed upgrade.
  • A problem where the rich text editor wasn’t being loaded due to compression issues has been worked around.
  • Extra security has been put in place to better protect you from plugins that do not do explicit permission checks.
  • Translation of role names fixed.
  • wp_page_menu() defaults to sorting by the user specified menu order rather than the page title.
  • Upload error messages are now correctly reported.
  • Autosave error experienced by some IE users is fixed.
  • Styling glitch in the plugin editor fixed.
  • SSH2 filesystem requirements updated.
  • Switched back to curl as the default transport.
  • Updated the translation library to avoid a problem with mbstring.func_overload.
  • Stricter inline style sanitization.
  • Stricter menu security.
  • Disabled code highlighting due to browser incompatibilities.
  • RTL layout fixes.

Full Details at http://wordpress.org/development/2009/07/wordpress-2-8-1/

So I suggest everyone upgrade ASAP to avoid any problems.  I figured I’d make a post just so the word gets out there for anyone stumbling on our blog.

This entry was posted in General. Bookmark the permalink.

3 Responses to WordPress 2.8.1 Released

  1. Chris says:

    Cool,

    One thing you need to do is fix your layout for safari 4.0.2 as comments where people have websites as a in there name seems to over lap the number of the reply.

  2. Cody says:

    We’ll look into this, thanks for letting us know :)!

  3. Hikari says:

    Worst thing in WP is plugins upgrade. It takes a lot of time to verify if each upgrade didn’t break anything and a few days after upgrading almost all plugins there are a dozen of new versions again to upgrade.

    Because of that I end up waiting too much to upgrade WP, waiting for all plugin devs to make them compatible. I didn’t upgrade to 2.7.1 because a plugin that didn’t work and only recently I was able to find the problem… dev didn’t know how to fix the bug even with many ppl complaining about it.

    And to make things worse I have to manage 2 blogs myself, and want to create 1 more -.-

    Hopefully I will go directly to 2.8.1 in a few weeks 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *