Released June 21, fixes 12 bugs. Security release.
From the release post: "This is a security release for all previous versions and we strongly encourage you to update your sites immediately."
8:33 pm on Jul 5, 2013 (gmt 0)
I knew it was a bad idea to modify all my wordpress files.
2:22 am on Jul 7, 2013 (gmt 0)
And this is why I'm phasing out the one WP install I have. Gimme static HTML, cached :-)
3:33 pm on Jul 9, 2013 (gmt 0)
If you are going to update...
Remember to update your themes as well.
In fact, if you are using a little known theme, or the theme has a lot of modifications to it, it might be a good idea to remove the theme from the wp-content folder altogether.
I did the upgrade and I couldn't get back into the wp admin, nor would by blog load for visitors.
After much trial and error, it turns out my somewhat obscure, modified theme was preventing ANYTHING from loading correctly; neither the front end nor the backend.
Just thought you might want to know.
3:39 am on Jul 10, 2013 (gmt 0)
@Planet13 How old was that theme? For the past few years I've never had an issue with WP upgrades - even with themes that were heavily modified (Thesis, CoWorker, and Genesis). The basic rule of thumb for upgrades is still and should always be: a) make a backup copy of your database and b) all of your files as they are at the moment just before backup. Always.
3:06 pm on Jul 10, 2013 (gmt 0)
It was an old theme 9magasin uno reloaded ver. 1.1). There was already an update out for the theme, but I DIDN'T update because I didn't know how to make child themes, and I didn't want to lose my hand-made modifications to the theme.
Yes, backups are a many splendid thing. I am glad I made mine, even though things worked out.