Hi, I've just taken over a Drupal project which has had contributed modules places in the core modules directory.
I'd like to move them out of there to /sites/all while keeping all the settings.
Having never put modules in the core directory myself I'm not sure how to fix it ...
Any tips on how it should be achieved would be much appreciated.
On Dec 6, 2007 12:11 PM, Sean Burlington sean@burlington.me.uk wrote:
Having never put modules in the core directory myself I'm not sure how to fix it ... Any tips on how it should be achieved would be much appreciated.
Have you tried simply moving the files to /sites/all ?
IIRC it just works, the system table is updated with the new module paths. If not, you have to update the "system" table (look for paths)
hth
Philippe
Philippe Jadin wrote:
On Dec 6, 2007 12:11 PM, Sean Burlington sean@burlington.me.uk wrote:
Having never put modules in the core directory myself I'm not sure how to fix it ... Any tips on how it should be achieved would be much appreciated.
Have you tried simply moving the files to /sites/all ?
IIRC it just works, the system table is updated with the new module paths. If not, you have to update the "system" table (look for paths)
Thanks - I did try that - it worked OK for themes and files but not modules.
I did this to try and fix the database values I could see
update system set filename = concat('sites/all/', filename) where name in (...);
But I no longer got the content from these modules I was expecting - so I moved it all back again.
It just seemed like a common enough error that there might be a "right way" to fix it ...
Quoting Sean Burlington sean@burlington.me.uk:
Hi, I've just taken over a Drupal project which has had contributed modules places in the core modules directory.
This was the way to do it before 5.x.
I'd like to move them out of there to /sites/all while keeping all the settings.
Shouldn't be a problem.
Having never put modules in the core directory myself I'm not sure how to fix it ...
Any tips on how it should be achieved would be much appreciated.
0. Put site offline. 1. Disable the module before moving it 2. Truncate cache* tables 3. Truncate sessions table 4. Move and enable the module 5. Review the variables and system tables for any likelihood issues, e.g. the old path. 6. Put site online.
And be a good sport and take a backup before proceeding.
Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
On Thursday 06 December 2007 04:56:19 Earnie Boyd wrote:
Quoting Sean Burlington sean@burlington.me.uk:
Any tips on how it should be achieved would be much appreciated.
- Put site offline.
- Disable the module before moving it
- Truncate cache* tables
- Truncate sessions table
- Move and enable the module
- Review the variables and system tables for any likelihood issues,
e.g. the old path. 6. Put site online.
And be a good sport and take a backup before proceeding.
While Earnie's 'best practice' is probably the safer more sane way of doing it, I will say that I have been successful on my development system by simply moving the modules and then going to the modules page to refresh the system table. That doesn't mean there won't be a module or two that won't comply. Simply moving the modules and then expecting things to work correctly isn't enough.
i've had success with that method as well.
Jason Flatt wrote:
While Earnie's 'best practice' is probably the safer more sane way of doing it, I will say that I have been successful on my development system by simply moving the modules and then going to the modules page to refresh the system table. That doesn't mean there won't be a module or two that won't comply. Simply moving the modules and then expecting things to work correctly isn't enough.
-
Earnie Boyd -
Jason Flatt -
Philippe Jadin -
sander-martijn -
Sean Burlington