WordPress 2.1.1 and 2.0.9 are out with bug fixes and security patches. Download the full version of 2.1.1 or choose 2.0.9, which includes a security patch only and not the WordPress 2.1 major updates and changes.
A list of file changes are on the announcement, and Techtites offers two file sets of only the changed files for the two different versions for those who just want to “patch” not redo.
For more on all kinds of WordPress news, including updates and fixes on popular WordPress Plugins and Themes, WordPress.com blog news, and news from around the WordPress community:
- WordPress Wednesday: Hot 2.1 Plugins and Themes, Contests, Challenges, and NoFollow
- WordPress Wednesday: Easter Eggs, Editor Extras, WordPress Plugins, and more WordPress 2.1
- WordPress Wednesday: Custom Fields Contest and Lots of WordPress.com News
- WordPress Wednesday: Happy Birthday and More WordPress 2.1
- WordPress Wednesday: WordPress 2.1 and More
For more on what I’m doing on the Blog Herald, see Lorelle Joins The Blog Herald.
Site Search Tags: wordpress news, wordpress release, wordpress version, wordpress 2.1, wordpress 2.1.1, wordpress update, security update, wordpress tips, blog herald, lorelle, lorelle on blog herald
Copyright Lorelle VanFossen, member of the 9Rules Network Subscribe
6 Comments
I’m all 2.1.1’d up. Seems fine but of course I can’t see any changes at the user end anyway – it’s not about that.
Hi Lorelle,
Thanks for the link.
BTW, I didn’t receive a Pingback from this post. I’m not sure if I am right about this, but I think WP sends the pingback only to the first url in the post that hasn’t yet been pinged.
For the second, you need to edit and save, and so on.
Why doesn’t WP put up a “changed files only” version? Honestly, there is a vast number of people who have hacked the code, and so we want to screw up as few files as possible with an upgrade.
And it figures, I upgraded to 2.1 yesterday. Sigh.
Always backup, always upgrade 🙂
awesome. I should go upgrade right now. Or maybe I’ll wait till my Fantastico tells me to. 😀
Excellent. I’m really looking forward to some of the fixes that are part of this update.
Of course this means I’ll need to create another Development environment for testing … 😛