Lorelle on WP: WordPress 2.7 Upgrade Tips at Your vBulletin Resource The Staff Lounge

You are here: Home » Wordpress » Lorelle on WP: WordPress 2.7 Upgrade Tips

Lorelle on WP: WordPress 2.7 Upgrade Tips

440 Views Published 1 year, 7 months ago in Wordpress

WordPress 2.7 has been released, and in addition to the information I provided in “WordPress 2.7 Available Now,” here are some tips to help you make the transition to WordPress 2.7.

Reports on the WordPress Support Forum and around the web are that WordPress 2.7 is the easiest upgrade ever. There are only a few reports of problems, which deal with Plugins that have now become integrated features in WordPress 2.7 and Plugins and Themes with customized comment areas. I’ve listed the most common support questions and their answers below, along with all the help you need to make this transition to WordPress 2.7 easy and pain free.

Check Your Web Host for Compatibility

Prior to upgrading, review WordPress 2.7 Core Update Host Compatibility to ensure that your WordPress blog will upgrade in compliance with the new features and demands of WordPress 2.7. Find a Web Host is a list of web hosts WordPress recommends.

Some issues reported during testing were server issues. WordPress 2.7 now supports PHP5 and it is important that web hosts upgrade to current versions of PHP and MySQL for many reasons, including feature improvements and security vulnerabilities, to protect you as well as themselves. The WordPress development team has worked closely with web host providers around the world to ensure that WordPress will work, and we all benefit from those discussions, including non-WordPress users.

If your web host is not on the compatibility or recommendation list, contact them directly to determine if they are supporting the new version of WordPress. If not, consider moving to another web host that will continue to support your blog and WordPress development.

Upgrading from an Older Version of WordPress

To upgrade from an older version of WordPress, I recommend a step-by-step process. If you are upgrading from WordPress 2.3 to WordPress 2.7, a big transition, go through the following documents on the WordPress Codex, the online manual for WordPress Users, and upgrade your WordPress blog for the transitions from 2.3 to 2.5, 2.5 to 2.6, and 2.6 to 2.7 to ensure you have made all changes necessary to your WordPress Theme. In general, Migrating Plugins and Themes to 2.7 should cover everything, but those upgrading from very old versions will want to check everything to ensure a successful upgrade.

Or check with your WordPress Theme author for an updated version of the Theme.

NOTE: If you are using the Auto Upgrade WordPress Plugin or something similar, a sticky post WordPress Plugin, or the Admin Drop Down Menus WordPress Plugin, deactivate them now. These features are now built into WordPress and no longer require these Plugins.

How to Upgrade to WordPress 2.7

If you are using one of the beta or release candidate versions of WordPress 2.7, run the upgrade feature. If you are using an older version of WordPress:

Check the WordPress 2.7 Core Update Host Compatibility guide.
Check for updates to your WordPress Theme and Plugins.
Follow the guide for Migrating Plugins and Themes for the version you are upgrading from. Check the WordPress 2.7 Plugin Compatibility and WordPress 2.7 Theme Compatibility lists to ensure your Theme and Plugin will work with WordPress 2.7.
Download WordPress 2.7 and follow the instructions for installing WordPress (new installations) or upgrading WordPress. If you need more specific help with your upgrade, especially using the new auto-upgrade feature, see the extended upgrade instructions.

I’m Worried About Upgrading to WordPress 2.7

Many are worried about upgrading to WordPress 2.7. Here are some of the worries, and some answers.

It’s Painful to Upgrade: WordPress 2.7 now features auto-upgrade, so this could be the last “painful” upgrade you do, though upgrades are not very painful, really. Now, WordPress will alert you when there is a new version or upgrade available and walk you through the process. The same applies to WordPress Themes and Plugins, making life much less painful.
My WordPress Theme Will Break: There is very little that will impact WordPress Themes in this new version, outside of WordPress Plugins that interact with WordPress Themes, especially with comments. WordPress Themes will be even better protected in future versions with the Parent/Child Theme feature (your changes are protected during upgrades) and easy auto-updating of Themes. If your Theme features customization to the comments area, see Migrating Plugins and Themes to 2.7 and Justin Tadlock’s “Making your theme’s comments compatible with WordPress 2.7 and earlier versions”.
I’ll Only Have to Upgrade Again and Again: Trust me, future upgrades are going to be easier than ever. Don’t let this old whine of “WordPress updates too often” fool you. You are smarter than that. EVERY computer program, online and off, has regular updates. My computer nags at me daily to update something. WordPress only updates when they have to due to a security vulnerability discovered or threatened, or when they have great new features that you will benefit from. With the auto-upgrade feature, this process will be simple and painless. Upgrade now.
I Won’t Be Able to Use My Favorite WordPress Plugins: If your favorite WordPress Plugins work with the Administration Panels or blog comments, the odds are that it won’t work or will need to be upgraded in WordPress 2.7. Check for upgrades to all your favorite WordPress Plugins and the WordPress 2.7 Plugin Compatibility list. If you are upgrading from a pre-WordPress 2.7 beta release, use the Upgrading WordPress instructions and deactivate all Plugins before installing, then activate them one by one to test them. If you can’t live without a certain WordPress Plugin, consider donating to their cause or encouraging their continued support of their Plugin. Or search for a new replacement.
I Want to Wait Until All the Bugs are Fixed: WordPress 2.7 has undergone extensive development and testing. It is currently in use on almost 5 million WordPress.com blogs and has been for a couple of months, though the new interface wasn’t activated. With past versions, waiting was a good recommendation. Now, with the recent WordPress 2.6.5 security update, it is highly recommended that you take that one step further and upgrade to 2.7 now to ensure you have the latest and most secure version. Having had some of my blogs, and those of my clients and fellow bloggers, hacked because we didn’t upgrade, we know the pain. Upgrade now.
I’m Not Technically Inclined: One of the most exciting features of WordPress 2.7 is the auto-upgrade feature. Once you get past a little initial code on this upgrade, depending upon which version you are upgrading from, no technical inclination required. WordPress, WordPress Themes, and WordPress Plugins all now feature automatic upgrades, making your life easier and less technical.
I Just Don’t Want to Upgrade: Okay, so there are some people who like making their life harder and want to stay with an older version of WordPress for whatever reasons. Quick Online Tips featured WordPress Plugins for those who wish to stay with WordPress 2.6, offering much of the functionality of WordPress 2.7. Be sure and upgrade to the latest version, WordPress 2.6.5, to maintain a secure version and protect your site from hackers and vulnerabilities. You will have to upgrade soon to maintain a secure version of WordPress, but this will delay the inevitable.

How to Get Help with WordPress 2.7 Issues

Some of the most common problems reported on the WordPress Support Forums for WordPress 2.7 are related to the following:

Admin Drop Down Menu WordPress Plugin: The popular Admin Drop Down Menu WordPress Plugin is no longer required for WordPress 2.7. Deactivate the Plugin if you are having trouble seeing the Dashboard or other Panels on the WordPress Administration Panels.
Internet Explorer Makes the Interface Look Strange: WordPress developers and designers have been fighting with Internet Explorer browser design issues and they recommend that you use the most recent browsers available, specifically FireFox 3, Google Chrome, and Safari 3.
WordPress Auto Upgrade Plugin: If you are using one of the automatic upgrade WordPress Plugins, deactivate it before installing the new version of WordPress.
Sticky Posts: If you have been using a sticky post WordPress Plugin, deactivate it. Sticky posts are now integrated into WordPress 2.7 and available on the specific post’s Edit panel. Check the box next to “Stick post to the front page” option.
Inability to Access WordPress Plugins After Upgrade: WordPress Plugin access is now found on the WordPress Dashboard Panel. If you are having trouble accessing them, link to them directly with http://example.com/wp-admin/plugins.php with your domain name.
A Plugin is Not Working: The Plugins are now accessed via the Dashboard. If you are having trouble finding your WordPress Plugins in 2.7, enter the address directly:
http://example.com/wp-admin/plugins.php.
If you have installed WordPress 2.7 correctly, there is now an Uninstall Plugin API which allows useres to uninstall WordPress Plugins completely, not just deactivate them.
Also check the WordPress 2.7 Plugin Compatibility list to ensure the Plugin will work with WordPress 2.7 and contact the Plugin author directly if you are having problems.
My Theme is Borked/Broken: If you are having trouble with your WordPress Theme after following the Migrating Plugins and Themes and checking the WordPress 2.7 Theme Compatibility list, then contact the Theme designer or check out the WordPress 2.7 Theme News section in WordPress 2.7 Release News and Links.

If you are still having trouble, turn to the WordPress Codex first. It’s the online manual for WordPress users.

Second, search first, through the WordPress Support Forums and your favorite search engine to see if others are having the same problem. Try different keywords and search terms as people often use non-standard terms to describe their problem.

Turn to the WordPress Support Forums next to leave a request for help. Follow these guidelines to get the fastest and most appropriate help:

BE SPECIFIC AND CLEAR: “WordPress 2.7 is broken” is not helpful. What is broken? Is it a Plugin, Theme, login, specific panel, what is broken? If you are not giving a clear title and helpful information in your help request, you will not a helpful answer in return.
WordPress Support Volunteers and Staff are not Mind Readers: Again, be clear. Be specific. Don’t expect us to understand what you are talking about. Give us all the pertinent information you can and you may get a specific and helpful answer.
Make Your Request in the Right Place: If you put a request for help with a WordPress Theme design issue in the Installation section of the Support Forums, the odds are that those who hang out there can’t help you. Put your request for help in the right place:
- Installation
- How-To and Troubleshooting
- Themes and Templates
- Plugins and Hacks
- WP-Advanced
- Your WordPress (Brag area)
- Miscellaneous
- Requests and Feedback
- Alpha/Beta
- WordPress.com Forums for WordPress.com only issues
Direct Your Help Request to the Right People:
- If you are having a general problem with WordPress, then use the WordPress Support Forums.
- If you are having trouble or a question about a WordPress Plugin, contact the Plugin author.
- If you are having trouble with a WordPress Theme, check with the Theme author for assistance.
- If you are having trouble with your web host or server, contact your web host.
- If you are having a general web design issue, please search the web and visit CSS and web design forums and groups for advice and help.
- Keep the WordPress Support Forums specifically for WordPress-related topics.
Be Kind and Play Nice: The WordPress Support Forums is not a place for egos or rudeness. The majority of those helping you are volunteers, giving freely of their time and WordPress expertise. Treat them kindly and you will get the support you need and the Support Forum will be a nice playground for everyone.
Be Patient: If your question is a general one, they it might get a fast response. If it is the same question asked many times, it may get no response, so search first to ensure you are not being redundant. If it is a sophisticated coding question that requires a specialist, be patient. They might not be online in the forum at the moment. It might take a day or two for a response. Don’t bump the post (make another comment) or leave another request unless several days have passed. Consider searching the web and finding someone with the expertise you need to help you.