By viametiers on

Hi,

I did an upgrade form 6.9 to 6.10 on my local test site.
The update .php worked fine but the status reports still says drupal is 6.9.
Other modules or themes are dispalyend as 6.10
In my system.modules file, I have define('VERSION', '6.10');

Any idea of what I did wrong ?

Thanks.

⋅ Categories: Drupal 6.x

Comments

cog.rusty’s picture

cog.rusty commented

Look for and remove any backups or copies of your old drupal installation from inside the new one. Examine the "system" table with phpmyadmin and check the paths, especially of the system module, in case they refer to a forgotten copy. After removing any copies run update.php again.

viametiers’s picture

viametiers commented

I've already done that. The backup copie are outside the "www folder" where my new installation is.
I alos checked the system table. The path is sites/all/modules/system/system.module which corresponds to the new version.
very strange...

cog.rusty’s picture

cog.rusty commented

The path is wrong. It should be just modules/system/system.module

It is not acceptable to move the core modules. This is probably a duplicate copy of the system module causing confusion, because if it was the only one it wouldn't work at all.

viametiers’s picture

viametiers commented

You're right. Thank you.
The guy who did the first installation has copied all the core modules to the /sites/all/modules directory. It was a copy not a move.
When I upgraded to 6.10, the latest version of the modules were in www/modules but I copied all the "old" verison of the modules in sites/all/modules. Now in this directiry I have the contributed modules and the "old" version of core modules.
The problem is that if I remove the core modules from this directory I get the following error message : Fatal error: Call to undefined function node_load() in C:\wamp\www\includes\menu.inc on line 410

I don't know wat to do.

cog.rusty’s picture

cog.rusty commented

After removing the duplicates try running update.php and visiting the admin/build/modules page (which updates the paths). If that is impossible, edit the paths in the system table.

Also make sure that all 5 "required" core modules (system, node, user, filter, block) are enabled (status=1) in the system table.

viametiers’s picture

viametiers commented

I can't run the update.php after removing those modules

viametiers’s picture

viametiers commented

I can't find user module in the system table

cog.rusty’s picture

cog.rusty commented

This is very strange if the site was ever working. I can't explain it.

viametiers’s picture

viametiers commented

Thank you for your help.
I finally reinstalled the new modules and changes the paths in the system table and everything is working now.

HTF’s picture

HTF commented

Just picked up on this thread as I had the same problem (not much fun when it happens at the end of the day on a Friday) thanks for the advice cog.rusty just got my site working again when I was just beginning to give up hope.

Robert S’s picture

Robert S commented

that caused this error in my case: after some unsuccessful experiments with version control systems, I ended up with file system.module of older version, while system.info was newer version.
Very confusing indeed!