2.6.2 is FINE. Seriously.
Posted Monday, September 15th, 2008 7:08 pm by Dave Moyer
I'm currently running WordPress 2.6.2 on my blog, and... GASP! I'm fine. I was recently pointed to this story.WordPress 2.6 Warning - DO NOT Upgrade on snoskred.comAs for right now, it appears that this is by no means a serious issue. In essence, it's a bunch of people whining about something that's mostly irrelevant and unimportant, and does not pose a significant problem. This is an issue that has been happening for people who have been updating from an age-old version to the new one, causing issues with missing files that were added in between, etc.If you experience any problems from 2.6.1 to 2.6.2, let me know in the comments below.Comment from Sephryoth:The issue described in the post is one where, on some sites, when you upgrade, you cannot access your blog’s admin panel. I know that because it happened to me, and the suggested fix (clearing cookies) did not work, since I tried it in three separate browsers, with the same result.The issue described in the post is one where, on some sites, when you upgrade, you cannot access your blog's admin panel. I know that because it happened to me, and the suggested fix (clearing cookies) did not work, since I tried it in three separate browsers, with the same result.Yes, that's exactly the problem going on for some users. But again, the support ticket for this problem is not new, in fact it's been around for a long time, and the users that seem to be having the problem are skipping versions of WordPress, causing issues with missing files that were added in between, etc. Thanks for the comment though, and my request for cpmments still stands if this problem affects you upgrading FROM 2.6.1 to 2.6.2!photo credit: adria.richards
The issue described in the post is one where, on some sites, when you upgrade, you cannot access your blog’s admin panel. I know that because it happened to me, and the suggested fix (clearing cookies) did not work, since I tried it in three separate browsers, with the same result.
It is not something that I would call “irrelevant and unimportant.” That is, unless you don’t consider being able to post to your site important.
It might be fine for you, but it isn’t fine for an awful lot of people. So let me sound the note of caution that telling people to upgrade because it was fine for you is potentially a dangerous piece of advice to be giving out to fellow bloggers who might be relying on your advice – if it turns out not be fine for them they won’t be exactly thrilled.
I’m not saying it based purely on my own experience, I based it on the experience other people had as well, and also after reading the support forums long enough to get a king size migraine. Because that place is not somewhere fun to hang out, unfortunately.
People are still having issues with the problems I mentioned right now today. And logging in to your blog is quite a vital function – if you can’t do that, you can’t write a post or moderate comments or do anything!
I believe better advice to give to people reading your blog is to be cautious, check things out before you upgrade, read the support forums to see what problems they are having and perhaps wait for a later, less buggy version.
And the most vital piece of advice you as a blogger should give to fellow bloggers is – if people do want to upgrade, backup and be prepared to use the backup if you need to. Because if things happen to go wrong and you were the reason they upgraded because it was fine for you, and you didn’t suggest they should back up? Disaster for the blogger.. :(
And in my case, I gave the advice I did because I feel very strongly about it. I still stand by it. 2.3.3 is perfectly safe as long as you disallow user registration. It doesn’t have a lot of the issues that happened with later versions. Bloggers want to be able to blog, not to have to deal with bugs. I don’t know why WordPress is choosing to go down the path they are, but it is upsetting plenty of people.