In my effort to learn Drupal quickly, I neglected to place contributed modules into the module folder instead of the sites/all/modules folder. Now that I have installed dozens of contributed modules, can I / should I move the contributed modules to the sites/all/modules folder? What are the implications? Everything seems to be working fine as it is.

Comments

saepl’s picture

It is recommended that you put them in /sites/all/modules to separate core from contributed files. I think if you uninstall them, move the files, reinstall them you should be good to go - but I am not sure, I have never had to move them before. I am sure you are not the first one to experience this problem and if you search here or on google you should get an answer.

Codeblind’s picture

The implications are updating Drupal core is going to be pain in the rear. A module will normally correct its own paths if you disable it, then move it into the sites folder, and finally re-enable the module. I recommend you do one or two at a time and see how it goes. It's easier to debug that way.

LobiJani’s picture

Can anyone please tell me where to put the "sites" folder?

nevets’s picture

It should already exist under the sites root folder.

LobiJani’s picture

I haven't found it

nevets’s picture

When you unpack/unzip the Drupal download, there should be a sites folder in the new folder created.

LobiJani’s picture

Ok so I've downloaded 7.10 and now I'm installing it on the server and in the new install I've found the sites folder, BUT the server doesn't allow me to copy it . so I can't create it.

ayesh’s picture

This is because to protect settings.php file (/sites/default/settings.php) which is a very important and must-keep-securely file.
You will have to change permissions of /sites folder to allow write access to "user" and "group" or specific item if you know)

LobiJani’s picture

what is the exact command line that I should modify?