By alexmoreno on

This is the question. i dont know how, but i´ve found an old installation of drupal with some core modules in /sites/all/modues. When i try to upgrade this web i get a lot of differnt errors,so i suppose that the first thing to do is correct this... but how?

Is it possible to move and then correct the database? How then?

Thanks a lot in advance.

⋅ Categories: Drupal 5.x

Comments

cayenne’s picture

cayenne commented

I had a similar problem.

Put the modules where they belong. Then, go to the database using, say PHPadmin. In the systems table, you'll find the paths to the modules. manually change the paths to what they should be. You can write a query to do this, but it should never happen again, right?

:)

yan’s picture

yan commented

You can edit the 'system' table in your database and replace the values in the 'filename' field of the core modules.

alexmoreno’s picture

alexmoreno commented

ah, ok, the sql querys which i have to modify are all in system, right? I'm going to try, i'll keep you informed with my advances.

Thanks a lot

dman’s picture

dman commented

Visit the admin module page. Leave it open.

Shift your modules around, anywhere you want.

save the admin modules page. The system will auto-detect the new locations and self-repair.
Very very few modules will have a problem with this. It's possible with any that use remembered links to themselves in the UI (font files or flash libraries?), but I've not seen one of those for ages.

Worst-case, you get an error message, press refresh(re-send) and it will be gone.

Same works with themes.

.dan. is the New Zealand Drupal Developer working on Government Web Standards

alexmoreno’s picture

alexmoreno commented

thanks a lot for your answer.

it didn´t work:

Fatal error: Call to undefined function system_region_list() in /var/www/vhosts/*****.com/httpdocs/themes/engines/phptemplate/phptemplate.engine on line 154

dman’s picture

dman commented

You had a moved version of system module? eep.
I guess my experience has mainly been with contrib or at least core-optional ones. Ah well.

.dan. is the New Zealand Drupal Developer working on Government Web Standards

dman’s picture

dman commented

Note that core modules in sites/all/modules means one thing - hacked core.
That's OK, because doing it like that is actually the safe way to 'modify' core. And may make sense.
But will certainly get in the way of upgrades.
Diff the private core vs the distro core first to see what they are doing. Then remove the private ones to a safe distance.

.dan. is the New Zealand Drupal Developer working on Government Web Standards