WordPress 2.7.1 was released yesterday. This is a maintenance release that fixes some 68 minor bugs and provides some preventive security measures. Lorelle lists the changes in this release in her post on the WordPress 2.7.1 release.
This has been the first large scale test of the new WordPress automatic upgrade and it has hit some rough spots. If you are having difficulties with your automatic upgrade:
- Check the web host core update compatibilty grid. Your web host may prohibit this feature.
- If you have been using the WordPress Automatic Upgrade plugin, deactivate it. It is not compatible with the built in upgrade feature.
- Try deactivating all of your plugins and retry upgrade. Other plugins or combination of plugins may be preventing the upgrade.
- Change the permission on the wp-contents folder to 777. Change back to 755 when the upgrade is complete.
- Clear the cache on your browser and retry upgrade
- Try a different browser, some people are reporting problems with the upgrade on Firefox and then upgrade easily on Internet Explorer!
- Be patient
- Not all blogs are recognizing the update yet, and displaying the upgrade message. People are reporting that the message is showing up on more and more blogs over the last 24 hours.
- The actual upgrade process can take 20 minutes depending on your set up and web host. There are not a lot of status messages during the process and you might only see a blank panel during the upgrade.
Some people are seeing a failure to connect to their database error immediately after the upgrade. Simply close the browser window and visit your blog in another browser window to clear the error.
In summary, for the vast majority of WordPress users are finding the new automatic feature of WordPress 2.7 to be really easy to use and loving it. As it evolves and continues to improve, expect it become seamless and easy for more and more of us.
Pingback: WordPress Woes: 2.7.1 upgrade glitches | The Wonderful Web
Pingback: What’s Buzzing? » Blog Archive » Kotoko » Wordpress 2.7.1
I was lucky. I couldn’t wait, had to leave the house. So I closed the browser and other programs, but left the machine on. It completed itself without me watching the blank screen.
Carol
The upgrade places a file in the root of the site, called .maintenance. It is supposed to delete this file after the upgrade has completed.
If your blog has the “…unavailable for scheduled maintenance…” message for a long time and you have received the message that the upgrade is complete, go into your site and delete the .maintenance file. Its not needed once the upgrade has been done so deleting it is fine.
I’ve posted more about this bug on my blog here: http://lynnepope.net/what-to-do-when-wordpress-auto-upgrade-hangs
Hope this helps some of you.
Pingback: (Anti) Social-Lists 2/15/09 | (Anti) Social Development
Pingback: WordPress 2.7.1 Released, Automatic Upgrade Works! - Web Development Blog
you are a lifesaver – thankyou! been going around in circles for an hour or so but now i can breathe easy!
Great, glad to hear that you found the troubleshooting guide to be helpful!
Thank you very much for pointing me in the right direction after pulling my hair out. Appreciate it.
Er, and you didn’t pull my hair out. That was me.
ROFL, i am glad that I was the helpful one and not the one standing around with fistfuls of hair! All kidding aside, glad to be of assistance.
I had a big trouble with wp 2.7.1. my manage plugin page did not load properly. I can’t activate or deactivate my plugins. It’s killing me. can anyone tell me what’s the problem.
Catherine’s last blog post..My Secret Way of Keyword Analysis
Catherine,
I need a little more information. What do you mean that it doesn’t load properly? Do you mean it appears corrupted or do you mean that it loads but says you have insufficient permissions, even when logged in as admin?
If it is the latter, it means you have a database problem. You will need to use PHP MyAdmin or something like it to edit the wp_options table in your database.
Hi,
Hopefully someone here can help me. After upgrading to 2.7.1 I had multiple problems. The first was members couldn’t sign in. well it seems in the config file the define Cookies lines were missing. I replaced those and that seems fine now.
My other problem I haven’t had any luck figuring out. While signed in as Admin I click on Blogs, and then choose the Backend link on a blog. It loads the profile page for some reason. Once there in the new blog’s admin area many of the links when clicked will also load the profile page. It only happens on about 5 out of my 20 blogs. Does anyone know what might be causing this / how to fix it?
Thanks for any help,
Gene
I’m having trouble publishing or saving posts, pages, and drafts. WordPress barfs all over me when I try; I have a few different sites that all run it, and one simply brings me to the main domain when I try to publish–or it says “Code corrupt. Insert fresh copy”. All my other sites give me that line too, or it will load part of the main domain page in weird places on the post-new.php page (changes the styles to the blog’s style and loads some of the images in the background, or loads some text from the splash page into the box that says word count or the box that allows you to choose tags).
I have no clue how to get anything of them working properly again.