By ludo1960 on

Hello,

I've been learning drupal for a few months now. I've decided on the final configuration, after much reading in the forums and documentation. During that time I installed lots and lots of modules (too many!) to find out their suitablity for my purposes. Now that I've identified the modules I want and their correct locations for a multi site configuration, which is the /sites/all/modules folder and not the /modules folder that comes with the default Drupal 6 installation.

So here's the question:

I tried the uninstall module admin page only to find:

"The uninstall process removes all data related to a module. To uninstall a module, you must first disable it. Not all modules support this feature." ........Luckily for me all the modules I want to get rid of don't appear after being disabled.

Then I tried to cut and paste a certain module from /modules folder to the /sites/all/modules folder but it didn't work! I changed the filepath in Systems table for that module and after a bit mucking about I got it to work. I am reluctant to continue using this method. So can anybody tell me if there is a recommended way of deleting/moving modules in Drupal 6?

Thanks....in advance!

⋅ Categories: Drupal 6.x

Comments

cog.rusty’s picture

cog.rusty commented

No need to change any filepaths in the database, or to uninstall/reinstall anything.

Just move them and then run update.php or visit the admin/build/modules and admin/build/themes pages. That should be enough for the paths to be updates.

Note: Never move core modules. Especially for the "required" ones, their paths are hard-wired.

ludo1960’s picture

ludo1960 commented

Thank you Sir,

Works a treat!

You said "Note: Never move core modules. Especially for the "required" ones, their paths are hard-wired."

Ok I've got that, I moved my chosen theme to the sites/all/themes and it all works well, what about the themes/engines folder, should that be sites/all/themes/engines? I've tried to move it, but was unable to run update.php, so I moved it back. Should I move it? How do I do it? And is this the correct procedure for a multi-site installation?

Thanks Again.

cog.rusty’s picture

cog.rusty commented

Don't move anything which comes with the core Drupal installation. The theme engines is one of these things.

The whole point of using a separate sites/all directory for your additional and your own customized modules and themes is that (a) Drupal core is in one place so that you can update it without messing with the additional or customized modules and themes, and (b) your own custom stuff is again in one place.

If you want to customize a core theme, for example Garland, the most clean method is to make a copy, for example, in sites/all/themes/garland2 and customize that copy instead.

ludo1960’s picture

ludo1960 commented

Great help,

I was a bit confused with the fact that the engines are a sub directory of the /themes folder and should not be part of the /sites/all/themes folder, now I understand why, thanks to your info. Maybe this point should be re-inforced within the Drupal site somewhere.

One teensy weensy question though:

You said:

"The whole point of using a separate sites/all directory for your additional and your own customized modules and themes is that (a) Drupal core is in one place so that you can update it without messing with the additional or customized modules and themes, and (b) your own custom stuff is again in one place."

I thought the reason for putting the files in the /sites/all directory was to enable a multi-site configuration?

Cheers!

cog.rusty’s picture

cog.rusty commented

Sure, it does help with multisite configuration.

Although technically you could have a multisite by putting only the different settings.php files under sites/ and all modules and themes together with the core modules, the separations makes it more tidy.

ludo1960’s picture

ludo1960 commented

Tell me you're a woman!

I think I love you...tell me more!

At least tell me where I can find more info on multi-site configuration.

Many Thanks,

Cliff...

cog.rusty’s picture

cog.rusty commented

Heh, you'll be fine, no need to get desperate ;)

There is a lot of stuff on multisites in the good book but a bit disorganised and mixed regarding Drupal version.

http://drupal.org/node/43816

rogermcallen’s picture

rogermcallen commented

Thanks a lot! You save me! It works!!

msmarko’s picture

msmarko commented

I dove into Drupal without much thought and put all my added modules into the modules folder. I recently discovered that they should go under the sites folder and moved them. Now I can't get to them. I have run update a number of times to no avail. I only see the core modules in the admin page. HHHHHEEEEEEELLLLLLLLLP!!!!!!!

TIA,

Marko

msmarko’s picture

msmarko commented

Ha. I had written the modules folder name with a captial m. Once I changed to a lower case everything was fine.