[development] Defining additional search paths for modules?

Justin Davis justindavis at mail.utexas.edu
Mon Nov 16 20:06:45 UTC 2009

Thank you for the response.

I love that systemmask would allow the root administrator to mark some modules as 'required', preventing a site admin from disabling something security related or such, although it would incur quite a bit of overhead whenever a new module was made available -- to run through each of the sites & hide is as needed.

Ideally, I'd be able to download a new organic group related module, place it in a folder (something like sites/all/bundles/og), thus making the new module available to any of my sub-sites that are configured to include 'sites/all/bundles/og' in their module path.

On Nov 16, 2009, at 1:23 PM, Daniel F. Kudwien wrote:

> http://drupal.org/project/systemmask 
>> -----Original Message-----
>> From: development-bounces at drupal.org 
>> [mailto:development-bounces at drupal.org] On Behalf Of Justin Davis
>> Sent: Monday, November 16, 2009 7:55 PM
>> To: development at drupal.org
>> Subject: [development] Defining additional search paths for modules?
>> Hello All.
>> My apologies if this belongs in "support" rather than "development".
>> I am managing a multi-site drupal installation and would like 
>> to be able to offer groups of modules to a sub set of our 
>> sites without having to have them installed in each 
>> sites/sitename/modules folder.
>> Basically, there are some advanced and developer modules that 
>> my more adept users need but that I would rather not be 
>> available to some of our novice site managers.
>> Ideally, I would be able to define something in the 
>> settings.php that told drupal to look in:
>>    sites/all/modules
>>    sites/all/modules_advanced
>>    sites/sitename/modules
>> The only possible solution that I've found would be to create 
>> a custom module that defined it's own "module_rebuild_cache" 
>> (maybe "extra_module_rebuild_cache" or such) that used a 
>> slightly modified "drupal_system_listing" that would be able 
>> to look outside of "sites/all/modules" and "sites/sitename/modules"
>> Does this make sense? Has anyone else come across a similar issue?
>> Thank you kindly,
>> Justin Davis
>> Liberal Arts ITS
>> University of Texas at Austin

Justin Davis
Liberal Arts ITS Sr. System Analyst
justindavis at mail.utexas.edu

More information about the development mailing list