Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.after the upgrade to 5.6 started the update module showing the incorrect information. today, after upgrading to the version 5.7 it shows the installed version 5.2 and recommendation to upgrade to the version 5.7.
i am running several sites on one installation. usually this problem was not present, only there was an error in the other sites after main upgrade and also their upgrade. the main site was usually showing the version correctly, but the other sites were not showing the info correctly. now - all the sites shows this info. on the other side - the version of modules is ok.
i am not sure, what can be wrong ;) maybe i did something wrong, but i really don't know what ;)
mirek
| Comment | File | Size | Author |
|---|---|---|---|
| screenshot.png | 39.89 KB | mirek_ |
Comments
Comment #1
dwwa) There are a number of bugs that I've recently fixed related to some of these sorts of problems. Please install the latest 5.x-2.x-dev version of update_status and see if the problems go away. http://drupal.org/node/143593
b) If the problem persists after using the latest code, I'd have to see copies of pretty much all of your .info files and where they're installed in your directory tree.
Comment #2
mirek_ commentedit's still the same also after upgrade. so - what information do you need to know?
Comment #3
dwwa tarball of your entire drupal code source tree would be the easiest.
basically, i want to see all your .info files and where in the filesystem they are.
Comment #4
mirek_ commentedok - here it goes. without some specific directories and files (themes directory, files directory and settings files). because its 2.6 megs, download it from here: http://www.cnl.tuke.sk/all.in.one.tgz
Comment #5
dwwhere's your problem: sites/all/modules/localizer
It contains the following modules and info files that claim your version of core is running 5.2:
./sites/all/modules/localizer/block/block.info:version = "5.2"
./sites/all/modules/localizer/menu/menu.info:version = "5.2"
./sites/all/modules/localizer/taxonomy/taxonomy.info:version = "5.2"
update_status can only rely on the .info files to know what's going on. if they're lying, update_status gets confused.
I don't know how localizer module works. it seems like it's forking core in some bizzaro way. I'd probably not use it at all.
Comment #6
mirek_ commentedok - great - i take a look at the module. thanks also for recommendation, but at the moment, there are not so many possibilities in 5.x to make mulitilanguage page. we were trying to use internationalization module in the 4.6.x, but it was really horrible, so i decided to use something else and localizer just works fine. at the moment, we are waiting for the official release of the version 6, so hopefuly - no more problems with multilanguage pages ;)
anyway - thanks for help ;) take care - you are doing good job ;) i like the update module ;)
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.