post-page

WordPress 3.1.1 Released

4
responses
by
 
on
April 6th, 2011
in
WordPress, WordPress News

WordPress 3.1.1 has been released. This maintenance and security release fixes 26 issues with the following highlights:

  • Performance improvements
  • Fixes for IIS6 support
  • Fixes for taxonomy and PATHINFO (/index.php/) permalinks
  • Fixes for various query and taxonomy edge cases that caused some plugin compatibility issues

Regarding this release’s security fixes, “the first hardens CSRF prevention in the media uploader, the second avoids a PHP crash in certain environments when handling devilishly devised links in comments, and the third addresses an XSS flaw.”

For most of you, 3.1.1 should be available as an automatic update via your Dashboard. If that isn’t working for you, you can download WordPress and perform a manual update.

heading
heading
4
Responses

 

Comments

  1. Charleston (1 comments.) says:

    WordPress update is getting more often lately. Hesitate to do now as last time some of my plugin was not working after the upgrading. Anyone who’s owns wp should do a backup b4 doing any changes and that’s valuable.

  2. Byron (11 comments.) says:

    If anyone gets a fatal memory error while trying to update, you might try deactivating some of your larger plugins and see if you get your memory usage low enough that it will go through. I was getting the memory error at around 30MB even though my host has allocated me 250MB. Happened on several sites on the same host, could be the host, but maybe not.

    Here’s a thread where a couple of others had this issue: http://wordpress.org/support/t.....?replies=5

    Cheers,
    Byron

    • gestroud says:

      I keep getting a 30MB warning whenever I try to upgrade/update plugins on my sites. Keep having to de-activate the other plugins to upgrade the ones in need of an update. Very strange.

      • Byron (11 comments.) says:

        I did a quick search of the files and found this line in the default-constants.php file:

        define(‘WP_MEMORY_LIMIT’, ’32M’)

        I’ll put in a Trac ticket and see if they think that might have something to do with the memory errors.

        Cheers,
        Byron



Obviously Powered by WordPress. © 2003-2013

page counter
css.php