Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I'm only reporting a bug.
Update Status module shows version 5.7 availability, but drupal 5.7 is correctly installed and working...
You can check the attached images.
| Comment | File | Size | Author |
|---|---|---|---|
| ScreenShot002.png | 19.9 KB | enli | |
| ScreenShot001.png | 21.96 KB | enli |
Comments
Comment #1
dwwI bet if you searched all the .info files on your site, you'd find some that still think your site is running 5.5, not 5.7. update_status just looks at the .info files. Sadly, it doesn't have code to warn you when it finds different modules from the same project (in this case, core), that have different version strings. See http://drupal.org/node/166333
Also, are you using the "localizer" module? See http://drupal.org/node/215442
Comment #2
enli commentedWell all of 5.5 modules are not anymore on my site and were substituted by 5.7 drupal core modules.
I'm not using "localizer" module, I'm using the following modules but nevere had problems with previous updates of drupal:
contact forms, google analytics, meta tags, node as block, spam, token, update status, colorpicker, image, lightbox2, gmap, simplenews, jquery update, xml sitemap.
I'm not running localizer. All these modules are updated.
Comment #3
dwwCore is composed of a lot of separate modules. I'm talking about the .info files for all of those:
For example:
Comment #4
dwwNo reply in over 6 months, must not be a problem anymore.