Keeps asking me to upgrade to 3.7.1 (32 posts)

  1. bwooster47
    Posted 2 years ago #

    Even though I've already upgraded to 3.7.1. I get repeated messages at the top of the admin pages:
    WordPress 3.7.1 is available! Please update now.
    And when I click on that, it says is it all upgraded.
    I've used Network Admin -> Dashboard, and clicked on Updates -> Available Updates where it always says:
    You have the latest version of WordPress. Future security updates will be applied automatically.

    So at that point, the system knows it has been upgraded. Not sure why every hour or so, it "forgets" that and both my sites end up reporting that it is out of date.

    The dashboard periodically shows:
    You are using WordPress 3.7.1. [Update to 3.7.1]
    Which makes no sense.
    Clicking on [Update to 3.7.1] says:
    You have the latest version of WordPress.
    and that everything is up to date.

    This does not seem to cause any functional problems, but is just annoying. Is there any manual fix to suppress this incorrect message?
    I noticed this or similar issues have been reported for nearly every release of WordPress, so this seems like an ongoing bug. But none of the issues have any fix or workaround suggested, so hoping someone can provide some tips on how to fix this now.

  2. Tara
    Volunteer Moderator
    Posted 2 years ago #

    Have you tried:
    - To rule out any theme-specific issue, try switching to the unedited default, core-bundled Theme (such as Twenty Twelve or Twenty Thirteen) for a moment using the WP dashboard. If you don't have access to your admin area, you can switch to the default theme by renaming your current theme's folder in wp-content/themes and adding "-old" to the end of the folder name using via FTP or SFTP or whatever file management application your host provides. Alternately, you can remove other themes except the default theme. That will force your site to use it.
    - resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems (because the hooks remain unless plugins completely removed or some plugins stick around in cached files. So by renaming the folder, you break them and force them inactive).

  3. bwooster47
    Posted 2 years ago #

    The steps above would be quite painful - I'd have to take my site down, wait for hours to see if that message pops up again.

    Clearly, this should be bug - showing a message like this:

    You are using WordPress 3.7.1. Update to 3.7.1

    Both are same values! Using X and Update to X. Why show the Update in this case?

    Are there some files on disk I can look at or database values to see why WordPress is showing this on the top:
    WordPress 3.7.1 is available! Please update now.

    It is not asking me to upgrade any plugin - it is asking to update WordPress itself.

    I did see a plugin update message once, but that was legitimate, and there was a update for a plugin available. Once plugin was upgraded, I never saw the plugin update message again, but continue to see the "Update to 3.7.1" again and again.

  4. esmi
    Forum Moderator
    Posted 2 years ago #

    Clearly, this should be bug

    Actually, it indicates that there is a problem on your site. There is no magic bullet in these situations. The steps outlined above are just the start of basic troubleshooting and is a process of elimination deliberately designed to locate the root cause as quickly as possible by first removing the most obvious and common culprits via a series of (often) temporary steps.

    Do you want to locate and, hopefully, fix the problem on your site? If "yes", then please help us to help you and carry out the changes that we suggest.

    Your theme & plugin settings are saved in your database and should be retained for future use.

  5. bwooster47
    Posted 2 years ago #

    Thanks, so according to you this is a user problem and no way for WordPress to help debug this.

    I guess you can close this issue and I'll just live with this.

    For those who build WordPress and are interested in helping fix this without asking users to take their site down for hours, here's what I can suggest:
    1) Add a debug flag. And/or always log somethings to a file. When that message fires, and it looks suspicious (string match "from" and "to" should be the trigger), it should note what data is used to fire that message.
    2) Then ask users to look at the log and report what they see in the log.

    For now, I suspect it has to do with multi-site install and/or multiple languages. This is not the first time people have reported this - a search shows a number of users reporting this issue over various versions.

  6. Tara
    Volunteer Moderator
    Posted 2 years ago #

    As @esmi explained: "it indicates that there is a problem on your site. There is no magic bullet in these situations..."

    - If the above troubleshooting steps fail to resolve the issue, you may try manually updating WP and see if that resolves the issue.

    Try manually re-uploading all files and folders EXCEPT the wp-config.php file and the /wp-content/ directory from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones. Read the Manual Update directions first!
    - Always backup everything (including your database) before doing any actions, just in case.

  7. esmi
    Forum Moderator
    Posted 2 years ago #

    Add a debug flag.

    There already is one but we do not recommend using it on a live, production site. Did you try checking your site's error logs for messages?

  8. bwooster47
    Posted 2 years ago #

    Another person reported this (in the
    multisite switcher forum)

    I have started to dig into the code - my main objective is to hack it so that this "crying wolf" buggy message is never seen. That would suppress the buggy code in WordPress, and still allow me to use the correct code in WordPress which does know when something is really available for upgrade (the button for Update works fine, it is the update-count and update-nag div class that is buggy).

    For now, found this HTML that I hope to suppress by whatever it takes:

    <div class='update-nag'><a href="http://codex.wordpress.org/Version_3.7.1">WordPress 3.7.1</a> is available! <a href="http://mp.aczoom.com/wp-admin/network/update-core.php">Please update now</a>.</div>
    	<ul class='wp-submenu wp-submenu-wrap'><li class='wp-submenu-head'>Updates <span class='update-plugins count-1' title='1 WordPress Update'><span class='update-count'>1</span></span></li><li class="wp-first-item"><a href='update-core.php' class="wp-first-item">Available Updates</a></li><li><a href='upgrade.php'>Upgrade Network</a></li></ul></li>
  9. teszter
    Posted 2 years ago #

    Same problem on our site. We were never had problems with the updates before 3.7
    Nothing has changed on our server so I guess it is a WordPress bug.
    Still looking for solution...

  10. claudi.fa
    Posted 2 years ago #

    Same problem on my site! Any ideas??

  11. ozaklad
    Posted 2 years ago #

    I'm having the exact same problem.
    In fact, I have two sites that mirror each other in every way (theme, plugins, structure, content) with the exception of language. One is fine, the other keeps on asking me to update to 3.7.1, even though it's already 3.7.1. But when I go into the update tab, the request to update disappears.

    Switching to another theme is not an option for me, as too much of the website functionality is tied to the theme (Headway 2.0.15.) I just can't afford losing it all.

  12. Tara
    Volunteer Moderator
    Posted 2 years ago #


    Despite any similarity in symptoms, your issue is likely to be completely different because of possible differences in physical servers, hosts, plugins, theme, configurations, etc. Posting in an existing topic prevents from being able to track issues by topic. Also, it's easier for volunteers to help you if you have your own topic. Thus, if you start your own thread per the forum guidelines , it is likely you may get more responses specific to your issue. :-)

  13. Dave Naylor
    Posted 2 years ago #

    I have seen this issue on two sites that I manage. In both instances I use the en_GB version of WordPress since I wanted to change some text in language files. I've noticed that if I upgrade (using wp-cli), my installations are upgraded with the en_US version of WordPress. So, WordPress reports that it's up to date, 3.7.1, but wants to update to the latest version, 3.7.1.

    If I download the en_GB version and overwrite the installed files, WordPress stops nagging me to update.

    I maintain all my sites with version control therefore I am able to see which files were updated. The only change of any significance was wp-includes/version.php. The single change was this:

    * @global string $required_mysql_version
    Add a comment to this line
     $required_mysql_version = '5.0';
    +$wp_local_package = 'en_GB';
  14. bwooster47
    Posted 2 years ago #

    That looks like a good tip. But couldn't you just change WPLANG in wp-config.php instead of in version.php (since wp-config.php won't get overwritten on update, while version.php will).

    Not fully sure yet, but this bug feels like it is a issue related to wp-content/languages and/or WPLANG.

    I have the default English version installed, but have fr_FR language files copied from the fr package into wp-content/languages - manual install.

    I can't change WPLANG in config because this is a multisite. And for the same reason, changing version.php seems incorrect since I need both English and French. (Maybe I can set WPLANG to a array?)

    But maybe getting close to figuring this bug out ... hopefully...

  15. claudi.fa
    Posted 2 years ago #

    Hey folks,

    here is what helped me:
    Go to the wp_options table in your database and find:


    I removed the entry there which looks something like this:


    WordPress now automatically builds a new entry.
    That solved the problem for me.
    ... hope that helps

  16. jibiel
    Posted 2 years ago #

    Any updates on the issue, guys?

    I seems to be having the same symptoms that both @WPRanger and @bwooster47 had.
    It started with 3.7.1 and persists until now — 3.8.

    Neither claudi.fa's solution nor copying over updated language files (wp-content/languages) haven't worked out for me.

  17. teszter
    Posted 2 years ago #

    This bug still persists here too.

  18. WPyogi
    Forum Moderator
    Posted 2 years ago #

    Everyone except the OP - I"d suggest starting your own threads if you need help -


    If the solution posted did not work for you, it's not the same issue.

  19. bwooster47
    Posted 2 years ago #

    I disagree. It is the same issue, and there is no "posted solution".

    There is some silly form-letter answer "turn off plugins" etc.
    Please try to understand - we have working sites, and there has to be a better way to respond to issue instead of asking people to create hundreds of threads.

    Whoever thought of this extremely fragile "let's warn in big colored letters" feature on an upgrade check should have tested this with a multi-site install. Have they? And this is type of check that is primed to have bugs in it - it is just not possible to get such things right.

    And having it cry wolf warning about false updates is a huge, serious issue. People will lose faith in that warning. It is extremely irritating and I could not find an easy way to disable it in code. Can you or someone tell me how to disable it in code? I am now at a stage where I don't mind hacking the core wordpress code.

    The common thread among all these posts is something about having additional language files copied over to the wp-content folder. That seems to confuse the version checking code. And given the number of variations in code, plugins, themes that WordPress allows, there will continue to be new combinations that confuses the version checking code.
    Worse, there are two different code checks in WordPress and the one that is crying wolf is different from the one that does the checks on the update page (which knows there is nothing to upgrade). Primed for bugs, this code is. It is crying out for a config option to disable, or better still, just rip it out until it really works.

  20. jibiel
    Posted 2 years ago #

    Some really [redacted] rules you got here. Off to StackExchange then — http://wordpress.stackexchange.com/questions/126796/wordpress-3-8-keeps-asking-me-to-upgrade-to-3-8

  21. bwooster47 - You need to understand that the number of people having this issue are SMALL and limited. We're smart, we're bloody brilliant, but we aren't magicians :) We have to do trial and error most of the time, unless we've seen this before.

    Are you perchace using a server side cache like memcached or APC?

  22. Per Mattsson
    Posted 2 years ago #

    Same problem here on 3.8, I'm running nine sites on 3.8. They all keep asking for update to 3.8 despite beeing upgraded already.

    I have not had the time to manually reinstall those sites to see what happends.

    3.7.1 does not have this behaviour.

  23. Dwenaus
    Posted 2 years ago #

    @claudi.fa deleting _site_transient_update_core in wp_options solved it for me! thanks!

  24. Bas Schuiling
    Posted 2 years ago #

    If somebody is doing body-counts; I have this problem as well across multiple sites.

    In my case I'm suspected it's caused by the IcanLocalize language plugin ( the small one, not WPML ) since it sets different locale for front and backend. But that's just speculation.

    I think that the comment WP should check on which version is on makes sense though, since it displays the correct version number in the bottom.

  25. phpsharma
    Posted 2 years ago #

    I am having the same problem..
    I guess tempera theme causing this issue.

    Any Tempera Theme users.


  26. @phpsharma Can you please start your own topic? This one is months old and doesn't involve any current version of WordPress.

  27. phpsharma
    Posted 2 years ago #

    Its Ok, Jan Dembowski..

    Sorry about that. I thought it would help someone.


  28. Arno Welzel
    Posted 2 years ago #

    JTFR: I have this problem as well - the dashboard tells me about an available core update and as soon as I go to the updates in the backend it tells me that my version is up to date.

    My current setup:

    1. WordPress 3.9 with multisite setup (but the issue already started to appear with 3.8)
    2. Multisite language switcher
    3. My own customized theme
    4. Primary site is language 'de_DE' with manually added language pack for version 3.9 from http://wpde.org/download/sprachdateien/
  29. bwooster47
    Posted 2 years ago #

    3.9.1 has the same problem.

    The irritating message says "upgrade available" and when I click on it, it goes to a page that says everything is ok and no upgrade is available.

    After a week of observing this message in 3.9.1, it finally went away today.
    But that was because for the first time, clicking the "upgrade available" message showed a real upgrade available:
    You can update to WordPress 3.9.1–fr_FR automatically or download the package and install it manually

    Which leads me to the reason why this is so buggy - the code is unable to detect multi-site versions correctly.
    So take a site that has both en and fr installed. An update comes along, and it is always the en package that is first. Once that is updated, the fr site probably has some files which indicate an older version.
    So the admin page nags about an update.
    But the fr update is not available yet.
    So the admin page first nags about "update available", and clicking on it goes oops, sorry, no update available.
    Eventually there is a fr.zip WordPress available and then it can apply the update, and only then does this nagging message stop.

    So a tip for the engineer developing this buggy feature - if you have not tested in a multi-site site, please do so, and allow us to disable it if this can't be fixed.
    Install both en and fr and see what happens when fr update is not yet available.

  30. rajlaksh
    Posted 2 years ago #

    Its due to permission apache unable to overwrite CORE files. Try using change directory permission.

    chown -R apache:apache /home/public_html

    Note: /home/public_html === complete path of wordpress

Topic Closed

This topic has been closed to new replies.

About this Topic