WordPress.org

Ready to get started?Download WordPress

Forums

3.0 upgrade message still showing after upgrade (19 posts)

  1. audub
    Member
    Posted 4 years ago #

    I have upgraded to WP 3.0 manually. The site seems to work fine, and the new wp-admin looks nice. But I keep getting the "WordPress 3.0 is available! Please update now."-message on top of the page. I have searched for a while now, but cant find anyone with the same problem.

    Anyone know how to solve this?

  2. bh_WP_fan
    Member
    Posted 4 years ago #

    That's usually caused by a file bearing the 3.0 text not being properly updated. Try the upgrade again, or do it manually.

  3. audub
    Member
    Posted 4 years ago #

    Thank you for the quick response.

    I've copied the files manually again, but I still get the upgrade message. Everything seems to work as it's supposed to.

    The dashboard also shows "You are using WordPress 3.0." with a button next to it saying "Upgrade to 3.0". Strange..

  4. fwray
    Member
    Posted 4 years ago #

    I'm having exactly the same problem. I've reinstalled the update, but still get the error message. The site seems to be up and running, and wp-admin is definitely 3.0 -- so help! I'm obsessing.

    (I assume that WP automatically updated my other sites because when I went to check out my non-updated site ... it had been mysteriously converted to 3.0 without being told. Could a "blanket" auto install be the culprit behind the "error" message in the initial update?)

  5. kwdavids
    Member
    Posted 4 years ago #

    I ran the automatic reinstall and this went away.

  6. audub
    Member
    Posted 4 years ago #

    My problem is that the automatic upgrade fail, and all guides tell me to upgrade manually :(

  7. MichaelH
    Member
    Posted 4 years ago #

    If 3.0 is installed (you see version 3.0 in the bottom right of each admin screen) then install the Core Control plugin and use that to 'check for updates'.

    http://wordpress.org/extend/plugins/core-control/

    Note to audub - manual upgrade instructions are at Upgrading WordPress.

  8. audub
    Member
    Posted 4 years ago #

    MichaelH: I've already followed the upgrade instructions you refer to. The problem is that the alert-message on top of each admin screen won't go away. I'll try the Core Control plugin. That will probably work for now.

    Thanks!

  9. bearqst
    Member
    Posted 4 years ago #

    Ver 3.0 is installed and everything works fine, but I also still see the notice:

    "An automated WordPress update has failed to complete - please attempt the update again now."

    I disabled and then completely removed all plugins from the plugin directory, re-ran the updater and still get the error message with "no" plugins at all.

    Any ideas appreciated.

  10. storyfirst
    Member
    Posted 4 years ago #

    I have the same problem as bearqst: did an automatic upgrade, got

    "An automated WordPress update has failed to complete - please attempt the update again now."

    So I went ran the auto update again. Still getting

    "An automated WordPress update has failed to complete - please attempt the update again now."

    Then I went through the manual download/upload process, and pulled up the setup.php screen. Which told me that 3.0 had already been installed.

    Back to the dashboard, where

    "An automated WordPress update has failed to complete - please attempt the update again now."

    is still hanging out. Any suggestions much appreciated.

  11. MichaelH
    Member
    Posted 4 years ago #

    If 3.0 is installed (you see version 3.0 in the bottom right of each admin screen) but you are still being prompted to update to 3.0, then install the Core Control plugin and use that to 'check for updates'.

    At least that worked in the past.

  12. bearqst
    Member
    Posted 4 years ago #

    Core Control hits a snag as well. Here's what I got back:

    You are currently using 3.0, The latest available version is
    You are currently using an internationalised version of WordPress:
    Check for core updates Now
    Checking for updates...
    An unexpected condition was hit

    So it says I have 3.0 but also hits an Unexpected Condition.

    Ideas where I should look to find out what the Unexpected Condition is ?

  13. Andrew Nacin
    Lead Developer
    Posted 4 years ago #

    In order to remove the "failed to complete" after performing a manual upgrade, simply remove the .maintenance file.

    If that file isn't getting removed after an auto-upgrade, then that's a bug report and we would need details of your server setup.

  14. bearqst
    Member
    Posted 4 years ago #

    That did it. the ,maintenance file was still present, del it and the "failed to complete" went away.

    What info and were to send it ?

  15. antikat
    Member
    Posted 4 years ago #

    Where do I find the .maintenance file?
    I cant find it in my root catalog for my wordpressinstallation.

  16. bearqst
    Member
    Posted 4 years ago #

    It was under the root directory.

  17. still giving
    Member
    Posted 4 years ago #

    I am guessing that the problem with having to remove the .maintenance file manually is due to the upgrade script timing out.

    Is there any chance folk suffering this issue are on shared hosting and their web host has some time limitations for running php scripts? Or is it browser related?

    I have seen the problem more than once now (I use Safari). Is there anyway of knowing IF the upgrade has completely run?

  18. Andrew Nacin
    Lead Developer
    Posted 4 years ago #

    @nonegiven: The .maintenance file is created at the start of an auto-upgrade and deleted upon completion. If it remains, then the auto-upgrade didn't complete, and you'll see the error. If you try an auto-upgrade again, and it works, the file will be deleted.

    However, if you do a manual upgrade, we have no way of knowing that we need to remove the .maintenance file. Deleting that file if it exists has been added to the instructions for Upgrading WordPress on the Codex.

  19. MPalmerDesign
    Member
    Posted 3 years ago #

    I was having the same trouble. Removing the .maintenance file worked for me as well after all else failed. Now I just have to figure out why it is I'm getting all this spam suddenly...

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.