By pacoverde on

From where does the "Admin -> Logs -> Status" page get the Drupal version number?

After updating my multi-site Drupal installation from v5.7 to v5.17, the main site still reports the version number at 5.7 -- even though the other site in the installation correctly reports v5.17 on its status page.

The "system.info" file of the system module reads:

; Information added by drupal.org packaging script on 2009-04-30
  version = "5.17"
  project = "drupal"
  datestamp = "1241050830

I've verified that the symlink in my webroot points to the v5.17 files and no longer at the v5.7 files, and I've done a graceful restart of Apache.

In short, I'm 99% sure the main site is now running v5.17 but I don't understand why the status page still only shows v5.7. Any ideas?
--
Thanks,

Glenn Gillis
Information Technology Manager
Environmental Law Alliance Worldwide
U.S. Office
http://www.elaw.org

⋅ Categories: Drupal 5.x

Comments

vm’s picture

vm commented

the system.module I think.

marcvangend’s picture

marcvangend
he/him
Primary language Dutch
Location Amsterdam
commented

That's correct, in system.module you will find

define('VERSION', '5.18');

On api.drupal.org you can trace back the version number on the status page to this constant. If your drupal installation shows the wrong version, I guess something went wrong when uploading/copying/extracting the new files.

cog.rusty’s picture

cog.rusty commented

Also, make sure to run update.php for each site of the multisite separately, to update each site's database. Don't rush to change the value in the system table because some update may not have been really done on a site's database.

agarwal.sudhanshu’s picture

agarwal.sudhanshu commented

It should be automatically updated if you upgraded your site correctly and replaced all old core modules with newer version.
(you can refer video tutorial http://drupal.org/node/287824 ).
Also every module has its info file and drupal version is listed in info file.
You should check in some of the module’s info files to make sure you have modules of new version. You can also check changelog.txt to make sure. Please ensure that you run update.php

pacoverde’s picture

pacoverde commented

Thanks for all the suggestions, but I've just updated again to 5.18 and the status page still reports 5.7.

The contents of the system module's "system.info" file definitely says 5.18:

[glenn@pan:system]$ less ./system.info
; $Id: system.info,v 1.3 2006/11/21 20:55:35 dries Exp $
name = System
description = Handles general site configuration for administrators.
package = Core - required
version = VERSION

; Information added by drupal.org packaging script on 2009-05-13
version = "5.18"
project = "drupal"
datestamp = "1242244862"

and the system.module file also defines the version as 5.18:

[glenn@pan:system]$ grep VERSION ./system.module
define('VERSION', '5.18');

I don't know how to update the sites in the multi-site configuration separately: I don't see any options for that when running the update.php script, even when choosing to "select versions". Anyway, the main site is the one showing the old version number; the second site is showing 5.18 as it should.
--
Glenn

cog.rusty’s picture

cog.rusty commented

You can run update.php for each individual site by using each site's domain name URL to run update.php.

Never use the manual selection of updates except if you know exactly which update queries you want to run. If you make a wrong manual selection Drupal may lose track of which updates it has already done.

If you still have the problem, try another possibility: Go to the database of the site which refuses to update. Browse the "system" table and find the row where name="system". Check the path in the "filename" field. Is it "modules/system/system.module"? If the path is different, check if there is an old copy of the system module in the path that you found, remove the duplicate files completely and correct the path in the database.

quentinsf’s picture

quentinsf commented

Many thanks, cog.rusty!

I had somehow managed to get a copy of the drupal 6.11 distribution in my sites/all/modules directory! When I upgraded to 6.13, the system table was still picking up all the modules from this deeply-buried directory and so told me I was still on 6.11.

In my case, the fix was to delete the rogue directory and run a bit of SQL:

UPDATE system SET filename =  substr(filename, 31) where `filename` like "sites/all/modules/drupal-6.11/%"

All happy now!

Phloyd’s picture

Phloyd commented

Hi there,

I have a similar issue.

I moved a database from an old standalone install to my multisite install.

The status for everything remains like it was with the old install, whereas the multisite install files are all up to date.

When I browse to update.php for the broken site, it says that there is nothing to update (which is true!) so the problem simply remains.

Any thoughts on a way to refresh the version and other system info? I have moved the domain to the new multisite server, so it is difficult to update the database and then move again to get around this...

vm’s picture

vm commented

update.php should be run all the way through regardless of whether or not there is something states that it needs updating.

the version information is taken from the system.modue file in modules/system

check that file for the proper version information.

Phloyd’s picture

Phloyd commented

The update process shows 'Updating 0 of 0', when there are many modules that need to be updated.

/**
* The current system version.
*/
define('VERSION', '6.13');

The version reports as 6.10, which was the version from the old install on the other server...

Oddly it also still complains about PHP register globals Enabled ('1'), when in fact that is not true on this server either...

Phloyd’s picture

Phloyd commented

Sorry, it looks like it was a case of cached DNS information in the browser and I was still looking at the old host even though other subdomains had transferred to the new one.

So most pages were up on the new site and Drupal remained on the old site.

No wonder nothing was updating! Sorry for the confusion.