By sharper1968 on

I have just completed (for about the 4th time!!!) an upgrade from 7.10 to 7.14

Although the upgrade seemed to complete successfully, and running update.php subsequently gives "No pending update" I am still getting a message which tell me that I need to upgrade from 7.10 to 7.14 and most (not all) of my modules still show 7.10

I've been banging my head of a wall all day - can anyone help?

Many thanks.

Stephen.

⋅ Categories: Drupal 7.x

Comments

jegger79’s picture

jegger79 commented

I'm having the exact same issue trying to go from 7.14 to 7.17. Did you ever figure it out?

Jeff Jones’s picture

Jeff Jones commented

I'm having the exact same issue trying to go from 7.14 to 7.17. What's up?

webtalist’s picture

webtalist commented

I have the same issue , anyone help ?

LucacHumach’s picture

LucacHumach commented

What kind of help have need clear please .

discount cartridge

new123456789’s picture

new123456789 commented

Upgrading 7.18 to 7.19 and having the same issue :(

inkuyo’s picture

inkuyo commented

has anyone gotten any answers here?

drupal a11y’s picture

drupal a11y commented

I am not really sure, but maybe the alert on the "admin/reports/status" is wrong, when you have an older module version in the "all"-folder than in a "default"-folder.

inkuyo’s picture

inkuyo commented

This is what I figured out. I have at sometime copied some of the core modules into the /SITE/modules folder. So at each upgrade I kept copying over the old core modules.

SOLUTION:
Delete the duplicate core module folders one by one. After each deletion I run the update.php to make sure the system is up to date. This will take a little time. Double check that the modules page have the latest versions listed (7.20 for me).

I hope this helps.

Chim’s picture

Chim commented

I had this issue, and it was caused by linux permissions/owners on the folders

I'm not sure what changed the owners? It could have been "drush up drupal" on the local site prior to deploying the repo on to stage

jegger79’s picture

jegger79 commented

This is still an issue for me and now some modules wont update as they require a new version of drupal than the one detected. I can confirm I now have 7.22 as far as core files but my site still says I am using 7.14. What is Drupal looking at when it checks for version?

John_B’s picture

John_B commented

Normally clearing cache_update fixes it. If for some reason it is not getting cleared when update is run, you can clear it from phpmyadmin or with command line mysql query or with drush. For more explanation, which I think is right, not 100% sure though I have researched it, see my latest post in this thread http://drupal.org/node/1962282#comment-7416062.

'No pending updates' is the wording normally indicating no database updates are required. Of course some module or core updates include database updates and others do not, so this may indicate that a successful module update does not need a database update, or that if it needs one, it has already been performed.

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors