upgrading from 6.26 to 6.27 will not be recognized by Updatemanager

Posted by 1mr1k on January 3, 2013 at 9:38am

I have searched all over, google and drupal.org, and I cannot seem to find reference to this specific issue.

I am trying to update to 6.27 for the security fixes. I have followed the standard update procedure.
I have put the site in maintenance mode, turned of all modules, put the theme, and admin theme to Garland, cleared the cache in the database, replaced drupal with the new version, ran update.php, even did a clean install of 6.27 and then imported the database again, but whatever i do, updatemanager keeps insisting my 6.26 version needs to be updated to 6.27.

I've looked in /modules/system/ at system.info and system.module, and both files say version = "6.27"

Am I missing something here? I've done several upgrades before, and never encountered this. Can I assume it upgraded, and just ignore it, since it's in the system.[files]? (assuming i can't)

Any help would be much appreciated.
Thanks

Comments

Same problem

Posted by droetker on January 4, 2013 at 4:20am

I have exactly the same problem with two sites. No idea how to solve this - can anyone help?

wait for anyone can help

Posted by zhiguocai on January 6, 2013 at 1:43am

Really hope someone can help solve this problem.

upgrading problems

Posted by niki v on January 18, 2013 at 5:30pm

This may be some use to you: http://heine.familiedeelstra.com/drupal-shows-old-version-after-update
or this http://drupal.org/node/1561708#comment-6256226

I upgraded successfully from 6.26 to 6.27, or so I thought, it all looked fine but then I discovered that I couldn't install or update my modules. I was referred to the above link by support but my server files are all where they should be and I have upgraded this site successfully in the past.
Testing on a WAMP server indicates that a clean install of 6.27 using the problem site's existing downloaded modules can be updated to 6.28 but when I updated the live site to 6.28, same problem with the modules and update manager doesn't recognise the core update.

fixed, kind of

Posted by 1mr1k on February 5, 2013 at 10:18am

That first link, http://heine.familiedeelstra.com/drupal-shows-old-version-after-update , really helped in tracking down the problem, thanks!

Turns out, there was a 2nd drupal version "hidden" in a directory in "/sites/all/modules", that shouldn't have been there, but for some reason got in there, and would've been very hard to find manually.

Updating that hidden version to 6.28 fixed the report message, the next step offcourse is cleaning up the rest.
Thanks for your reply :)