By ceci123 on

hi.

I've been told that for upgrading purposes I should be careful where I place downloaded modules.

I understand that modules should be placed under eg. drupal/sites/all/contributed_modules.

I downloaded the "multisite_manager-6" module and dropped on the contributed_modules dir but drupal does not see it.
when I put this module on the drupal/modules drupal is able to see it.

So the question is, where do I really want to put all the modules? eg. CCK, Pathauto, Devel, Gallery..etc.
So do I put these under the contributed_modules folder or the drupal/modules folder?

I am just trying to do things correctly.

thanks

C

⋅ Categories: Drupal 6.x

Comments

nevets’s picture

nevets commented

It should be under sites/all/modules.

lopolencastredealmeida’s picture

lopolencastredealmeida commented

if you have only one site you should put the modules under [your drupal root]/sites/all/modules/[drupal module dir]

Look inside the README.txt in sites/all

This directory should be used to place downloaded and custom modules
and themes which are common to all sites. This will allow you to
more easily update Drupal core files. These modules and themes should
be placed in subdirectories called modules and themes as follows:

sites/all/modules
sites/all/themes

If you have or plan to have more than one site you should put the common modules (i.e. used by more than one site) using the method above and the modules only used by each site under [your drupal root]/sites/[your domain]/modules/[drupal module dir]

Read also your INSTALL.txt at the root of the unpacked drupal tar.gz.

Sites do not have to have a different domain. You can also use subdomains and
subdirectories for Drupal sites. For example, example.com, sub.example.com,
and sub.example.com/site3 can all be defined as independent Drupal sites. The
setup for a configuration such as this would look like the following:

sites/default/settings.php
sites/example.com/settings.php
sites/sub.example.com/settings.php
sites/sub.example.com.site3/settings.php

When searching for a site configuration (for example www.sub.example.com/site3),
Drupal will search for configuration files in the following order, using the
first configuration it finds:

sites/www.sub.example.com.site3/settings.php
sites/sub.example.com.site3/settings.php
sites/example.com.site3/settings.php
sites/www.sub.example.com/settings.php
sites/sub.example.com/settings.php
sites/example.com/settings.php
sites/default/settings.php

If you are installing on a non-standard port, the port number is treated as the
deepest subdomain. For example: http://www.example.com:8080/ could be loaded
from sites/8080.www.example.com/. The port number will be removed according to
the pattern above if no port-specific configuration is found, just like a real
subdomain.

Each site configuration can have its own site-specific modules and themes in
addition to those installed in the standard 'modules' and 'themes' directories.
To use site-specific modules or themes, simply create a 'modules' or 'themes'
directory within the site configuration directory. For example, if
sub.example.com has a custom theme and a custom module that should not be
accessible to other sites, the setup would look like this:

sites/sub.example.com/:
settings.php
themes/custom_theme
modules/custom_module

There is a lot more info really easy to understand there and it covers almost everything to put your site running as expected.

And, of course, you have the handbooks.

Humaneasy Consulting
iPublicis!COM
www.humaneasy.com
www.ipublicis.com

CSM & CSPO

ceci123’s picture

ceci123 commented

as suggested, i placed it on the /sites/all/modules and it works.

thank you all

C