Wordpress 2.1.3 is Out
Posted by Stephen on
April 3, 2007
Just a note to all those Wordpress Bloggers out there that Wordpress 2.1.3 is out. Fixed stuff includes…
These releases include fixes for several publicly known minor XSS issues, one major XML-RPC issue, and a proactive full sweep of the WordPress codebase to protect against future problems. Many thanks to Sumit Siddharth and Alex Concha for their help with reporting issues in this release.
As an update to the systems issue we had last month, we have taken dozens of additional precautions with the servers and systems that run WordPress.org and they appear to be working well, despite hundreds of hack attempts after we publicly disclosed there had been a problem. We are also now aggressively monitoring all downloads for any changes or modifications, and we are confident the same type of problem won’t happen again.
It’s always a good idea to upgrade, unless of course the upgrade has been hacked. Hopefully, they won’t have that problem this time.
Aww man . . i hate upgrading . . i JUST upgraded to 2.1.2 2 weeks ago . . i guess now i know what i’m doing this weekend!
Upgrade again? Awww…..No, I’ll wait a bit longer to see if no one hacks into it this time.
I only upgraded to 2.1.2 yesterday
I took the plunge today to 2.1.3 and even changed the quick 5 step guide to just throw all the files in the folder and click upgrade 
No problems noticed yet although I do not recommend this method. Just have a good backup.
I guess I’ll rely on you again for this Stephen
Can I do that too?
Guess I should have done my rounds of reading before posting as I just posted about this update now.
The worst part about upgrading is deactivating all the plugins!!!
They need a “deactivate all” button.
I’ve actually heard that this is something under consideration for a future release. I know that I’m pushing my luck but I usually leave all the plugins activated and review the site afterwards. I ran into a problem once doing this but with these minor updates it has been okay.
I’m not daring enough to keep my plugins on while upgrading – although if I’m just replacing a few files I don’t see what the harm is…. have you upgraded to 2.1.3 without disabling plugins? Let me know how it goes
Yeah, I did both of my sites without disabling plugins and haven’t experienced any problems thus far. Before doing the upgrade, I always make sure to get a good backup of my database and all my content files just in case.
On these minor updates, I also have a tendency to not completely blow away all of the files but delete the files that have been changed and then deploy only those updates.
I leave the plugins active and figure I can just deactivate after if there is a problem.
seriously… gary and i were trying to think of a way to make a plugin that would deactivate plugins upon upgrade. LOL let me know if you make it.
That plugin wouldn’t come from me but it was being discussed from the peeps at WP. It was a comment from Matt Mullenweg left in a thread on Matt Cutts’ site, he said there will be a link in v2.2 to deactivate all plugins.
Here is the reference
Good good – I’ll upgrade my wp installation when it includes a link to deactivate all plugins!
oh GAWD! not again… i upgrade ONE DAY before they announced 2.1.2. and that .htaccess file can kiss my ass… obviously, i’m not a tech person…
My .htaccess file reverts to default A LOT.
I keep a backup handy to copy over through command line every week or so
Thanks…I think I’m going to wait a couple weeks to upgrade.
too many upgrades for me ..
i’m sticking with 2.0.7 … before the 2.1 big upgrade & after the big safety scare patch