WordPress 3.3.1 is now available. This maintenance release fixes 15 issues with WordPress 3.3, as well as a fix for a cross-site scripting vulnerability that affected version 3.3. Thanks to Joshua H., Hoang T., Stefan Zimmerman, Chris K. and the Go Daddy security team for responsibly disclosing the bug to our security team.
Why don't all wordpress installs auto-update again..?
Forgotten wordpress blogs are becoming the new scourge of the web.
It's a shame to see so much old/good content magically turn into viagra adverts.
indybail
1:20 pm on Jan 5, 2012 (gmt 0)
I want to manual install WordPress updates so I can maintain plugin compatibility. I accept things like the lack of auto updates as the price of having rich plugin capabilities.
rogerd
11:27 pm on Jan 9, 2012 (gmt 0)
At least with the way WP is currently designed, a forced update might break many sites who are using plugins and theme frameworks that will also need updates. In addition, it's not uncommon to find major updates that are incompatible with hosting limitations, e.g., a PHP or MySQL version. In theory, though, that would be a great benefit.
lorax
11:43 pm on Jan 9, 2012 (gmt 0)
I haven't run into any issues with updates but I have chosen matured plugins and themes/theme frameworks.
martinibuster
7:51 am on Jan 10, 2012 (gmt 0)
Does this break Thesis installations?
lorax
12:11 pm on Jan 10, 2012 (gmt 0)
Not that I've seen. I have about 20 of them in place and the upgrades went fine.
WordPress 3.3.1 Security and Maintenance Release
