Skip navigation

WordPress 2.7 Upgrade Tips

WordPress NewsWordPress 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 , 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:

  1. Check the WordPress 2.7 Core Update Host Compatibility guide.
  2. Check for updates to your WordPress Theme and Plugins.
  3. 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.
  4. 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.

  1. 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.
  2. 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”.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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 for WordPress 2.7 are related to the following:

  1. 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.
  2. 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.
  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.
  4. 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.
  5. 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.
  6. 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.
  7. 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 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 next to leave a request for help. Follow these guidelines to get the fastest and most appropriate help:

  1. 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.
  2. 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.
  3. 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:
  4. 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.
  5. Be Kind and Play Nice: The 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.
  6. 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.

Here are more tips and guides to finding help with WordPress:

More Information on WordPress 2.7

Honestly, it is worth it. Don’t wait. WordPress 2.7 is the most secure and user-friendly version available. Upgrade to WordPress 2.7 now.



Site Search Tags: , , , , , , , , , , , , ,

Feed on Lorelle on WordPress Subscribe Feedburner iconVia Feedburner Subscribe by Email Visit
Copyright Lorelle VanFossen, the author of Blogging Tips, What Bloggers Won't Tell You About Blogging.

54 Comments

  1. Posted December 11, 2008 at 12:21 pm | Permalink

    Lorelle, Can you clarify what you mean by ‘now supports PHP5′? It has worked on PHP5 every since i’ve been using it, does this mean that PHP5 is now the recommended version for WordPress?

    • Posted December 11, 2008 at 10:04 pm | Permalink

      Mark Jaquith just gave you the answer and filled in the blanks. And he is so right. WordPress 2.7 is totally where the party is happening. Rock on! :D

  2. Posted December 11, 2008 at 12:57 pm | Permalink

    WordPress has worked on PHP5 for as long as PHP5 has been stable. What’s notable is that as the end of 2007, PHP 4.x is no longer being updated… it is a dead branch. So if your hosting provider isn’t yet on PHP5, you should urge them to upgrade — just for the sake of being on a supported branch that’ll get all the latest security updates.

    We may discontinue PHP4 support at some time, but WordPress 2.7 still supports it.

    And to be clear, 2.6.5 is still a secure version, but our development resources are going to be directed towards 2.7.1 and 2.8, so you should start planning an upgrade soon. Plus, 2.7 is totally where the party is happening!

  3. Posted December 11, 2008 at 1:17 pm | Permalink

    Hi Lorelle,

    I’ve written a tutorial on starting fresh with WordPress 2.7, which is basically starting with a clean 2.7 install and importing the older blog posts.

  4. Posted December 11, 2008 at 4:18 pm | Permalink

    Upgrading is always a little nerve racking for people. I test things out on a development site before upgrading my main blog. That way I can find any problems if there are going to be any on a site that does not matter. It has saved me from problems in the past.

  5. Posted December 12, 2008 at 5:23 am | Permalink

    —QUOTE—
    WordPress Auto Upgrade Plugin: If you are using one of the automatic upgrade WordPress Plugins, deactivate it before installing the new version of WordPress.
    —UNQUOTE—

    WPAU (WordPress Automatic Upgrade) plugin does work well to upgrade wordpress to v 2.7. After upgrading one can disable the plugin permanently.

    • Posted December 12, 2008 at 1:39 pm | Permalink

      Glad to know. Unfortunately, reports are that it causes problems for some during the upgrade process. Don’t know what they are upgrading from or what their circumstances are, but some are finding problems. Others not. Better safe than sorry. Backup first, either way. :D

  6. Dan Schulz
    Posted December 12, 2008 at 8:16 am | Permalink

    Hi Lorelle

    I’m surprised you didn’t add Opera (opera.com/download/ for those who are wondering) to the list of recommended browsers. Any chance you can add it to your list?

    • Posted December 12, 2008 at 1:33 pm | Permalink

      It’s not my list. It’s the WordPress Development team who put that list of recommended browsers up. They tested and that’s what they found. Sorry, talk to them. Is Opera working “perfectly” for WordPress 2.7?

  7. Posted December 13, 2008 at 12:20 pm | Permalink

    Actually I just upgraded straight from 2.1 to 2.7 with not a hitch, so I don’t think there is really a need to do all the separate major version upgrades at a time.

    To be extra safe though, what I did was download the whole directory from /wordpress/ and re-upload it as /wordpress-v2.7/. Then I did FTPed the 2.7 upgrade to the /wordpress-v2.7/ directory.

    After that was done, all I had to do was rename /wordpress/ to /wordpress-v2.1/ and /wordpress-v2.7/ to /wordpress/ and I was good to go. Worked like a charm. If there was any problem, though, I could revert in seconds.

    • Posted December 13, 2008 at 1:18 pm | Permalink

      Wow, you must be using a Theme that worked across all the versions as there were MAJOR Theme changes between some of those versions. For instance, you probably lost your post categories in your sidebar, if you were displaying them and using that template tag. You also were probably not using many Plugins that depend upon the changes in the Administration Panels over those different versions. Good for you. That’s great news.

      Unfortunately, that’s not the same for everyone making such a huge jump. It certainly isn’t for me, though the changes were minor between versions.

  8. Posted December 13, 2008 at 9:42 pm | Permalink

    Thanks for the helpful article, Lorelle. I read your post and went to upgrade my WordPress instance but found that I didn’t have a current database backup. Looking into the issue, I ran into a little more technical problem with the plugin WP-DBManager not being able to work on my site at first. I fixed that configuration and wrote up some documentation in hopes that it might be helpful to others:
    PHP Basics with WordPress and phpBB

    Thanks again!
    -Jason

  9. Posted December 14, 2008 at 6:41 am | Permalink

    Very helpful list, I was sweating bullets upgrading one of my busier blogs to 2.7 – fortunately I didn’t use an comment related plugins there but I do on some others… guess I’ll wait to make sure those plugins are updated.

  10. greg
    Posted December 14, 2008 at 10:41 am | Permalink

    I love WordPress and downloaded 2.7 somewhere in the 60,000s, promptly upgrading two personal sites that run on WP. But you should add to your list of reasons not to upgrade “Don’t want to have to retrain content/site managers.” It seems like we just went through a major dashboard reconfig with 2.5, and now it’s happening all over again. I’ve set up a couple non-profits’ websites on WP as a favor, and now when I upgrade them to 2.7 I’m going to have to train their non-technical staff all over again. It seems like there’s a lot of fussing with the dashboard, etc. unnecessarily, and I wonder if the learning curve is considered when deciding to redo it. Anyway, I’m already learning to love much about 2.7, but it’s frustrating to have to ponder the upgrade for my other sites.

    • Posted December 14, 2008 at 1:37 pm | Permalink

      Among my clients and the many multi-blogger sites I’m a part of, there has been NO retraining. The administrators have had questions, but those who are just contributors have had very few questions and only eager embracing of the new, very easy-to-use interface. The non-technical folks “got it” faster than the experienced folks. I found that refreshing, and a bit daunting as, honestly, I was looking forward to some income from training. :D

  11. Posted December 14, 2008 at 7:11 pm | Permalink

    Thanks for this post! I have been waiting patiently to upgrade!

  12. Posted December 15, 2008 at 11:05 pm | Permalink

    Thanks for info…

  13. Posted December 16, 2008 at 3:21 am | Permalink

    Thanks for putting together this collection of information to help with any upgrade issues.

    I upgraded all my plug-ins last night and backed up my databases. WordPress 2.7 is all set to copy across to my ISP to upgrade from 2.5.

    Fingers crossed that all goes well :-)

    • Posted December 16, 2008 at 9:55 am | Permalink

      Glad you upgraded your WordPress Plugins, and I hope you made the Theme changes that happened between WordPress 2.5 and 2.7. :D I hope the upgrade went well for you.

  14. Posted December 16, 2008 at 4:45 am | Permalink

    Great post Lorelle. I spent this past Saturday upgrading 7 WordPress installs to 2.7, and all went without a hitch. Following the extended WordPress upgrade instructions to the letter would save a lot of folks from post-upgrade headaches.

    One of the biggest headache-causers comes from not deactivating plugins before upgrading. It only takes one incompatible plugin to throw a monkey-wrench in the upgrade process.

    Another common upgrade problem I’ve seen on the WordPress forum are FTP issues where all the 2.7 files didn’t get uploaded for some reason, and the user wasn’t aware of it.

    Having been part of the wp-testers group, I was already familiar to the 2.7 admin interface, and actually found it painful to have to go back and use 2.6.5. Yes, it is different, but once you get over the initial shock, you’ll love it! :)

  15. Posted December 16, 2008 at 6:15 am | Permalink

    Lorelle,

    I just did my first WP 2.7 upgrade. I own or help others on a total of 14 WP sites, some that have been around for a couple of years (WP 2.1 days), others built in the last month. So of course, I picked a simple one first! I moved a WP 2.6.1 up. The site had only 3 posts, no comments, and a (modified, but still) compatible theme. Not too hairy a plugin load either, nothing that manages comments, for instance. Here’s what I did and what I found:

    I backed up the database; then updated all plugins that needed that; then deactivated all plugins.
    I deleted the old site files, leaving the /wp-content/ folder intact. All images, uploads, etc., were there.
    Of course, I didn’t delete the .htaccess or wp-config files!
    I uploaded WP 2.7 files: /wp-admin/, /wp-includes/, and the root directory files.
    My browser was still showing the WP 2.6.1 Dashboard; so I clicked on the Dashboard link (upper left), and crossed my fingers.
    The site paused a moment, then said I needed a Database Update. I clicked that, and seconds later the new Dashboard appeared.

    It was that easy!

    I found only 1 plugin I use that WP 2.7 objected to, one that I dearly love under previous WP installs: Admin Management Xtended by Oliver Schlöbe. A great time-saving tool, but apparently mostly superseded by the new interface…

    Thanks for a great writeup on WP 2.7!

    The Chile Doctor

  16. Posted December 16, 2008 at 6:48 am | Permalink

    I have been using bluehost for a few months because, like you wrote, wordpress recommends.

    Just found out that they do not support wildcard subdomains which, although is not mandatory in order to have wordpress mu installed, lets say, would be interesting.

  17. Posted December 16, 2008 at 7:41 am | Permalink

    raju said: WPAU (WordPress Automatic Upgrade) plugin does work well to upgrade wordpress to v 2.7. After upgrading one can disable the plugin permanently.

    While many have been able to use this without issues, I have seen several cases where the WPAU plugin did not correctly perform the upgrade, and left the site in a broken state, or was missing many files. Maybe these were old versions of the plugin, I don’t know. Regardless, I would highly recommend against using any sort of automatic upgrader to transition to WordPress 2.7. Upgrade manually. It’s easier than you think, and hey, with the new auto-upgrade functionality built in to WP 2.7, it may be the last time you ever have to do it yourself.

    • Posted December 16, 2008 at 9:40 am | Permalink

      I agree, but watched many people using it at the WordPress 2.7 Release Party in Portland, Oregon. They were using the new version of the Plugin. I recommended not using it, but from all the quick testing we did, using the latest version of the WPAU seemed to have no problems. I still agree with my original statement and with you, Otto.

  18. joshbransoncom
    Posted December 16, 2008 at 9:53 am | Permalink

    Should be pointed out that those upgrading Themes will find a WTF? when they don’t do a copy of the theme first. All modifications of the theme will be lost when doing the upgrade.

    Some issues with the HTTP API on some hosts will prevent those from accessing areas that use the HTTP API, which are actually a lot. Should be a small amount of people affected with these bugs.

    • Posted December 16, 2008 at 10:06 am | Permalink

      For this upgrade, the same rules apply for upgrading Themes that have from the beginning of WordPress time. If you upgrade a Theme, all customizations are lost. You will have to add them back in. This isn’t news. It’s how it has been.

      Fortunately, the parent/child feature now in WordPress 2.7 will protect those modifications. See the articles referenced from here.

  19. Posted December 16, 2008 at 10:15 am | Permalink

    I’m still very wary about 2.7. I don’t have plugins (save for Akismet), so that’s not a problem, but the theme I’m using is very old but I don’t want to change it. It was made for 2.0 apparently, I started using WordPress at 2.1 and so far kept up with updates as soon as they were released without a problem, but now I’m a bit scared…
    Thing is that I modified it a lot, basically just took it as a “blueprint”, changed pretty much everything in the CSS and poked around some of the PHP files too, so installing an updated version would mean quite a lot of work to get it back to how it is and I’m not even sure where I should start even if I was inclined to (I don’t know PHP, just poked around those files with a “let’s see what happens” attitude until it seemed to work right). And there’s no 2.7 version anyway, apparently the author put coding on hold for the past few months due to personal problems.
    Also, I’m not going to stop using IE for WP! Never got along with FF (yes, I tried) and have more issues with Google than with Microsoft so Chrome is out of the question even before getting into the features that wouldn’t work for me.

    • Posted December 16, 2008 at 2:45 pm | Permalink

      If you have kept things updated all the way along, then upgrading to WordPress 2.7 will be a non-event, unless you have really customized the comment area, and then the WordPress Codex article on Migrating Plugins and Themes to WordPress 2.7, focused on the new enhanced comment display has the tips you need to make your site totally work with WordPress 2.7.

      Honestly, it will work with your old Theme, just not with old Plugins that interact with comments and the Administration Panels. Hundreds of thousands are upgrading without any problems.

      As for the issue of using Internet Explorer, you might want to rethink that fast. An announcement has gone out the IE 7 has a huge vulnerability and even Microsoft is recommending people not use it’s web browser until this is fixed. FireFox really works well for beginners, better than IE, so with your experience on the web, I’m sure change is tough but you can do it.

      Also, people change their web design without suffering, often for the improvement of the site. Switching to a new WordPress Theme, even if temporary, might generate some new energy on your site. Change is energy. Doing nothing gets you nothing. :D

  20. Posted December 16, 2008 at 12:07 pm | Permalink

    I took the plunge, upgraded to 2.7 using WPAU, took less than a minute, all seems to be working ;-)

    One Happy Bunny

  21. Posted December 16, 2008 at 3:22 pm | Permalink

    Actually, MS isn’t recommending that, others are. And I just don’t like FF…
    And I don’t adopt that view of change at all. [Babble follows.] Might seem weird for someone “trying to change the world” to say that he dislikes change but there you have it. When something doesn’t work, take it apart, figure out why it wasn’t working and build something new in its place which will avoid all those problems without creating new ones in their place. But when something works leave it well enough alone. All too often good things are “improved” all the way to destruction while bad ones are left as they are.
    Back on topic, I’ll likely wait at least a few weeks this time. Just have a bad feeling about it *shrug*
    I’ll shut up now.

  22. camsnetw
    Posted December 17, 2008 at 12:19 am | Permalink

    this makes me decide to upgrade to this version. Thanks for the good words.

  23. Posted December 17, 2008 at 12:26 am | Permalink

    hello,
    is there any document or papers which can outline if there is any changes in theme files or not.

    Means i have a custom theme and if i could know what changes should be done in order to make it compatible with latest version ,then i will be able to update wordpress.

    thanks for your help.

    • Posted December 17, 2008 at 10:15 am | Permalink

      Check the documents included in this article for migrating from one version to the other. That is the “papers” you are looking for with all the details you need to know. Beyond that, check with the Theme designer for upgrades, as well as with the Plugin authors.

  24. kosngo
    Posted December 17, 2008 at 12:29 am | Permalink

    this great guide on upgrading to WordPress 2.7

  25. Posted December 17, 2008 at 3:03 am | Permalink

    Installed WordPress 2.7 and it went on just as easily as previous versions. A database upgrade is required so be sure to back up database first, which we should do anyway :-)

    New interface looks great and it works fine with my Mimbo theme.

    The only problem found so far is that Lightbox is not inserting the appropriate code. After a quick search I discovered this is being discussed on the forum so there is no resolution yet. However it is very easy to add the code manually until the issue is resolved.

    • Posted December 17, 2008 at 10:13 am | Permalink

      The answer will probably come from the Plugin author. Be sure and check their site first. Glad you didn’t have any trouble with your upgrade.

  26. Posted December 17, 2008 at 4:32 pm | Permalink

    Do you know of any reason why the “Press This” functionality has been scaled back to not include the “Quote” and “Photo” tabs? Obviously the “quote” is an easy one to do, but I loved the ability to magically pull an image from the site I was on at the time, and unless I’m losing my mind – I couldn’t see it there.

    • Posted December 17, 2008 at 8:03 pm | Permalink

      I wondered the same thing. It’s really frustrating not to be able to add an image or put the quick post in a category. EVERYTHING you publish using the QuickPress or Press This bookmarklet puts the post in Uncategorized or whatever your default category is. I hope they improve this soon.

  27. Posted December 19, 2008 at 3:50 am | Permalink

    Nice article. Thanks. I have upgraded about six blogs to 2.7 and have only experienced errors with one of the blogs; after changing the theme the blog worked fine on WordPress 2.7.

  28. Posted December 19, 2008 at 8:24 am | Permalink

    I’m new to WordPress and I’ve been browsing your site. You have some great info and tips here.
    Just wanted to say Thank You. :)

  29. Posted December 19, 2008 at 9:46 am | Permalink

    This is a little bit out of topic, but just wanna ask if anyone else experiencing missing trackbacks to previous posts from your own posts?

    • Posted December 19, 2008 at 3:07 pm | Permalink

      Yes, way off topic as this needs to be addressed on the WordPress Support Forums so those looking for similar help and solutions will find yours. I appreciate you asking here, but that only confuses and dilutes the process of making WordPress better for everyone. Thanks.

  30. Posted December 20, 2008 at 2:51 am | Permalink

    thanks Lorelle.. I had trouble viewing the Dashboard.. and that was purely due to the drop down plugin. Thanks again. That saved me a headache

  31. GM
    Posted January 7, 2009 at 6:14 am | Permalink

    I already moved to 2.7.
    I love the new Look in the Admin Page.
    Makes me wonder, what the Future of WordPress holds.

  32. Posted January 9, 2009 at 4:43 pm | Permalink

    I’ve been using WordPress 2.7 for a few weeks now without problems until yesterday. Unfortunately, I’m not able to find information regarding the issue I’m having in either the WordPress support or search engines. I did start a new thread stating my problem, but so far no response.

    Starting yesterday, I am unable to write new posts or to edit posts because the page reloads and never finishes. Leaving me with a blank white screen. My other admin pages do not do this, only the write new post and the edit post pages.

    Over the past few days, I did install three plugins, but deactivating those plugins has not resolved the problem.

    I just find it rather odd that this only started yesterday, even though I upgraded to 2.7 a couple of weeks ago. I have also contacted my server through a support ticket, but I seriously doubt this problem is related to them.

    In meantime, I am unable to write new posts for my site. So I’m feeling a little desperate.

    • Posted January 10, 2009 at 2:35 pm | Permalink

      First of all, be sure and head to the WordPress Support Forum for immediate help. I’m on the road a lot and can’t respond immediately often. Second, the issue could be a server issue. I’m hearing some reports of server errors, so the issue may rely upon your web host. If you added a new Plugin or made a change, then that might have broken your blog. Please check the forums for others who might be having the same problem, and to ask for help. They can give you the individual help you need. Thanks.

  33. landpakchong
    Posted January 23, 2009 at 10:15 pm | Permalink

    Thank you so much for the insihts on wordpress.

  34. landpakchong
    Posted January 23, 2009 at 11:01 pm | Permalink

    I have agree for this is the good article. This makes me decide to upgrade to this version too.

    Thank you.

  35. usacopy
    Posted January 26, 2009 at 1:43 pm | Permalink

    I am having the same problems with my Food Blog, Nibbles of Tidbits — I upgraded to 2.7 about a week ago — All was working fine until yesterday. I NOW cannot write and save new posts, nor can I edit, and comments are not being registered/posted. The only plug in I use is Akismet, which was deactivated during the upgrade — I subsequently re-activated it, but don’t think that caused the problem because it was working fine after that.

    I’m not sure what to do now. I’ve read a lot, but I’m confused what to do. HOW DO I FIX IT? I only have a little technical knowledge. It appears this is a common problem right now. PLEASE HELP!!!!!!

    • Posted January 26, 2009 at 7:23 pm | Permalink

      You need to start asking for help in the WordPress Support Forums, not on other people’s blogs. The issue could very well not be WordPress issue and be a server issue, so contact your server and ask them for help, too. If you did nothing to WordPress, then it’s probably a server issue. Contact them.

      Good luck with this.

  36. usacopywriter
    Posted January 26, 2009 at 7:49 pm | Permalink

    Hi Lorelle. I thought I did write this to wordpress. I had done so many searches and been on so many forums that I thought I was still on WordPress. I certainly didn’t mean to direct this to an individual’s blog. Sorry. And it definitely isn’t a server problem, but I’ll go from here. Thanks.

    • Posted January 27, 2009 at 1:35 am | Permalink

      LOL. The forums are definitely different from a WordPress.com blog. WordPress.com is the free blog hosting service. WordPress.org is the full version of WordPress and where that support is found. Good luck with your issues.

  37. Posted February 19, 2009 at 1:53 pm | Permalink

    Lorelle: Your site has been valuable to me in the past with WordPress issues. I really appreciate your work! This time though, I’m stumped. I ungraded to 2.7.1 from 2.3 and my sidebars have disappeared and have this error message:

    Fatal error: Call to undefined function: tla_ads() in …sidebar.php on line 45

    My footer is also gone (no error message). I am sure it is something in the code I need to update. If you can assist, I’d be so grateful!

    • Posted February 19, 2009 at 11:30 pm | Permalink

      The problem is related to whatever Plugin or script you are using for your advertising. Check with the Plugin author or the WordPress Support Forum for more help on this. I’m sure the footer is gone because of the error in the sidebar.

      Also, when you post errors like that, you open the door to a hacker getting into your site by the code you reveal. I’ve edited the code, but take care publicizing that kind of detail when you ask for help. Why open the door to trouble you don’t need. :D


41 Trackbacks/Pingbacks

  1. [...] WordPress 2.7 Upgrade Tips Lorelle has posted an insane amount of tips tricks and gotchas when it comes to upgrading to WordPress 2.7. Check it out before you touch yours. [...]

  2. [...] Check out this post from Lorelle VanFossen (Lorelle on WordPress). It will tell you everything you need to know! [...]

  3. [...] Go to this great guide on upgrading to WordPress 2.7 [...]

  4. [...] Here are some WordPress 2.7 upgrade tips from Lorelle. [...]

  5. [...] WordPress 2.7 Upgrade Tips (Lorelle VanFossen) [...]

  6. [...] WordPress 2.7 upgrade tips (tags: WordPress tips list 2.7) [...]

  7. [...] você ainda não fez o upgrade do WordPress, eu recomendo ler este texto da Lorelle que tem as melhores dicas de como fazer seu upgrade com [...]

  8. [...] WordPress 2.7 Upgrade Tips « Lorelle on 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. [...]

  9. [...] self-hosted WordPress.org blogs, I’ve finally decided to make the jump. After reading some helpful tips regarding the 2.7 upgrade over at the Lorelle on WordPress blog, I began making my own preparations for the upgrade and ran into a little more technical [...]

  10. [...] WordPress 2.7 Upgrade Tips [...]

  11. [...] I also did not discuss anything about the features and other problems here except host compatibility problem as I know a lot of people have written about it already. For example, Lorelle have written a very good article, some tips on upgrading to WordPress 2.7, hop on to Lorelle on WordPress – WordPress 2.7 Upgrade Tips. [...]

  12. [...] WordPress 2.7 Upgrade Tips Lorelle has posted an insane amount of tips tricks and gotchas when it comes to upgrading to WordPress 2.7. Check it out before you touch yours. [...]

  13. [...] Antes de actualizarlo, mejor mira estas instrucciones. 3. En inglés también recomiendo estas: WordPress 2.7 Upgrade Tips. 4. Es necesario saber qué plugins están actualizados para esta versión. Puede que no te [...]

  14. [...] from 2008-12-15] Lorelle VanFossen has some nice upgrade tips for WordPress 2.7 – of course. I should have looked there earlier. Nice article, [...]

  15. [...] Oficial: Lorelle WordPress: Trucos para actualizar a WordPress 2.7 Etiquetas: actualización, actualizar, alojamiento, ayuda, oficial, plugin, plugins, referencias, [...]

  16. [...] WordPress 2.7 Upgrade TipsLorelle on WordPress [...]

  17. [...] discussing upgrade concerns to WordPress 2.7, Lorelle mentioned a link to another blog that suggests a series of WordPress plugins that work [...]

  18. [...] I just came across this post by Lorelle VanFossen, full of useful WordPress upgrading tips. Check it out if you experience any upgrading problem. [...]

  19. [...] extra tips for Upgrading WordPress to 2.7 comes from Lorelle . Copyright © 2007 – 2008 | Cenay Nailor | All Rights Reserved Except As Stated Below [...]

  20. [...] It helps to read about the new release before performing updates. Here’s a good overview provided by Lorelle: WordPress Upgrade Tips. [...]

  21. [...] to Improve WordPress Security How to: redirect WordPress RSS feeds to feedburner with .htaccess WordPress 2.7 Upgrade Tips Publikační systémyPublikační systémyPublikační systémy – Simple PHP Blog [...]

  22. [...] Lorelle’s post on “WordPress 2.7 Upgrade Tips” and the strong case she presents on why it’s a good idea to upgrade now – I have made [...]

  23. [...] WordPress 2.7 Upgrade Tips « Lorelle on WordPress [...]

  24. [...] WordPress 2.7 Upgrade Tips WordPress 2.7 has been released, and in addition to the information I provided in “WordPress 2.7 Available [...] [...]

  25. [...] couple days after WP 2.7 was announced, I read a nice piece by Lorelle on the new system. She convinced me to try, so I took my new, baby site and upgraded. I took risky [...]

  26. [...] WordPress 2.7 Upgrade Tips [...]

  27. [...] on WordPress has a great post here on upgrading, with a nice collection of links to more info for specific issues & [...]

  28. [...] Posted in WordPress News, WordPress Tips       Go to Original Source [...]

  29. [...] an upgrade to 2.7. and configured some plugins. Prepared my upgrade, checked this site for example: http://lorelle.wordpress.com/2008/12/11/wordpress-27-upgrade-tips . So far the [...]

  30. [...] En Lorelle on WordPress hay un magnífico post acerca de la migración a 2.7: WordPress 2.7 Upgrade Tips. [...]

  31. [...] WordPress 2.7 Upgrade Tips [...]

  32. [...] WordPress 2.7, take advantage of the automatic built-in upgrade. If you are not, then consider upgrading to WordPress 2.7. Sixty-five files were modified with 68 bug and feature fixes and [...]

  33. [...] WordPress 2.7, take advantage of the automatic built-in upgrade. If you are not, then consider upgrading to WordPress 2.7. Sixty-five files were modified with 68 bug and feature fixes and [...]

  34. [...] WordPress 2.7, take advantage of the automatic built-in upgrade. If you are not, then consider upgrading to WordPress 2.7. Sixty-five files were modified with 68 bug and feature fixes and [...]

  35. [...] WordPress 2.7, take advantage of the automatic built-in upgrade. If you are not, then consider upgrading to WordPress 2.7. Sixty-five files were modified with 68 bug and feature fixes and improvements, and I covered more [...]

  36. [...] WordPress 2.7, take advantage of the automatic built-in upgrade. If you are not, then consider upgrading to WordPress 2.7. Sixty-five files were modified with 68 bug and feature fixes and improvements, and I covered more [...]

  37. [...] WordPress 2.7, take advantage of the automatic built-in upgrade. If you are not, then consider upgrading to WordPress 2.7. Sixty-five files were modified with 68 bug and feature fixes and improvements, and I covered more [...]

  38. [...] WordPress 2.7, take advantage of the automatic built-in upgrade. If you are not, then consider upgrading to WordPress 2.7. Sixty-five files were modified with 68 bug and feature fixes and improvements, and I covered more [...]

  39. [...] 2.7, tirar partido da built-in automático actualização. Se não estiver, então considerar fazer o upgrade para WordPress 2,7. Sessenta e cinco arquivos foram modificados com 68 bugs e funcionalidade correções e [...]

  40. [...] WordPress 2.7 Upgrade Tips(WordPress 2.7 升级技巧) Lorelle 发布数量狂多的升级到 WordPress 2.7 的技巧。升级之前要查看一下哦。 [...]

  41. [...] WordPress 2.7 Upgrade Tips by Lorelle [...]

Post a Comment

Follow

Get every new post delivered to your Inbox.

Join 21,167 other followers

%d bloggers like this: