[drupal-docs] [task] Installing new modules

[Kobus]

Issue status update for 
http://drupal.org/node/29180
Post a follow up: 
http://drupal.org/project/comments/add/29180

 Project:      Documentation
 Version:      <none>
 Component:    Installation
 Category:     tasks
 Priority:     normal
 Assigned to:  Anonymous
 Reported by:  dopry
 Updated by:   Kobus
 Status:       active

How about just creating a folder *inside* the modules folder, say,
"contrib" and put all the modules in there? Drupal is able to read
through a directory structure to detect modules placed in there?


Regards




Kobus



Previous comments:
------------------------------------------------------------------------

Fri, 19 Aug 2005 06:46:45 +0000 : dopry

regarding:
http://drupal.org/node/17473


for easier upgradability I should drupal users should be directed to
install contrib modules in sites/default|/modules instead of modules. 


1) it allows users to get a better view of which modules they have from
contrib.
2) Its really easy to copy the sites folder to an upgraded drupal
install. 


It isn't a solution to major upgrades where modules need to be upgraded
as well, but would make the bug fix upgrades easier for most users. 


Does anyone know if sites/default/modules gets loaded for all sites
sharing the same codebase? I couldn't really tell browsing through the
code today. Just thinking of ways to make the upgrade path easier.




------------------------------------------------------------------------

Fri, 19 Aug 2005 08:21:09 +0000 : sepeck

-1 contirb modules should be in a named sub directory of modules (e.g.
modules/image/image.module).  This makes them available to all sites in
a multisite install and identifies them as contrib modules.  Individual
modules under default or other sites directories are for modules that
are custom or not to be generally available.




------------------------------------------------------------------------

Fri, 19 Aug 2005 08:25:57 +0000 : Boris Mann

Actually, I partially disagree, sepeck.


For single-site installs, this is a great solution, and does indeed
separate all of contrib nicely from core. It's probably worthy of a
best practices write up specifically for single sites.