update notification system doesn't recognize update 7.10 ➔ 7.12

Having the exact same issue. SUBSCRIBE

same issue

I checked on IRC and got scolded and told to roll back to a backup that is pre-update. This unfortunately isn't a viable option since I have since added boatloads of content and would lose all of this. Now I have to just deal with the status notification. I wish this would get resolved. Maybe with the 7.13 update it will go away?

Unless of course the gurus know an easy way to get rid of this?

You didn't actually upgrade the site. What the message tells you is that there's an old core module (or modules) still in use.

Possible causes:

• You accidentally restored the old modules folder from a backup.
• You tried to overwrite the older install, but this failed for some reason (common on ftp).
• You made a backup of core modules inside the modules or sites folder.
• You copied a core module to sites/default/modules or sites/[site]/modules to override a core module.
• You are looking at the wrong server (embarrassing, but it happens).

Also, please search before posting.

Heine THANK YOU!!!! You are a genius. I knew a guru would pull through.

I came from Drupal Gardens and I think they have certain modules in development that must rely on certain versions they stick in the sites/all/modules folder to override the core modules.

You copied a core module to sites/default/modules or sites/[site]/modules to override a core module.

was exactly what it was.

1. I deleted the duplicate modules found in sites/all/modules using /modules as a reference. Don't delete any modules in /modules!
2. Ran update.php and it found 3 pending updates.
3. 7.12 is now reflected in the update status.

Thanks again Heine. I'd like to buy you a Heine!

Had the same problem in Drupal 6.26 -->2.27/6.28

You made a backup of core modules inside the modules or sites folder.

I accidentially made a copy of all core directories (modules, scripts, include, etc) into the sites/modules folder.
Didn't see it as I have many modules activated and they blended into the mass of others ;-)

deleted them, all clean.
Thanks very much, Heine!

What happened to me: created a custom module, and copied and pasted a core module's info file as a template. Be sure to take these out:

; Information added by drupal.org packaging script on 2013-08-08
version = "7.23"
project = "drupal"
datestamp = "1375928238"