Upgraded to 7.31 but getting "no pending updates" message

By stylecramper on 19 Aug 2014 at 19:28 UTC

After copying over the files for 7.31 (was 7.26) and running update.php, the result is "no pending updates." I followed the instructions at https://www.drupal.org/node/1494290 properly - any thoughts about what to do next? Thanks.

Comments

double check modules

marksward commented 19 August 2014 at 21:32

Check non of your core module folders have found their way into one of the sites/* folders. I slip up on a copy did this to me a long while back, took a while to spot it. Also check file and folder permissions.

Checked modules

stylecramper commented 19 August 2014 at 21:50

Thanks, I did compare the /modules folder with /sites/all/modules and there's no duplication. What do you recommend for file and folder permissions to be?

The permission fixed the issue

norislee commented 25 August 2014 at 17:56

Have the same issue. The permission got messed up. Fix the permission, fix the issue.

Thanks.

That's because there are no

Jaypan commented 19 August 2014 at 22:04

That's because there are no database updates to be made between these two versions (as far as I can remember).

There were updates

stylecramper commented 20 August 2014 at 17:19

Actually I performed the update on a local copy of the site, and there were about a half dozen database updates performed.

Overriding core component?

Bojalay commented 27 October 2014 at 17:23

I have inherited a Druapl site that I know am maintaining am having a similar issue with seeing the "no updates available" after swapping out the core files on the FTP.

When you talk about changing permissions is that server side or through the Drupal Admin?
There is a folder on the FTP named "test" and it contains a settings.php file. When I try and remove it from the server I am getting an error due to permissions, which I have changed. Could this be causing the issue?

I am still a bit new to Drupal, but if I can get this figured out it would make my day.

Thanks for any help.

=-=

VM commented 27 October 2014 at 18:20

A) please don't crosspost the same question on multiple threads.
B) see the other thread where I've already answered your question

Not quite sure what you are asking. For clarification the database doesn't always need to be updated. What update.php is telling you is that there aren't any database updates to perform with the 7.32 update. Difficult to state if you missed any since you didn't take the time to inform what version you were updating from. Regardless, if registration was open on your site and you were late to update 7.32 you really need to work through the database and make sure there aren't any backdoors left open per the doc already linked in my previous comment.