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
I would go low-tech and just create symlinks to sites/all/modules-advanced in each of the desired sites/sitename/modules . For mor etech, maybe write a shell script to add & remove these links automatically from a config file, if frequent maintenance is required. -Matt On Mon, Nov 16, 2009 at 10:55 AM, Justin Davis <justindavis@mail.utexas.edu>wrote:
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
Thank you for the quick response. I've been using symlinks thus far, but would like to use something that I could manage either through the admin interface or the settings.php file. In theory, if it were a module with a config interface, I could allow the sub-site administrators to enable or disable blocks of modules without giving them write access to the filesystem. One of our goals/requirements is to manage all modules centrally & prevent site admins from potentially installing an unmaintained or unpatched module. Unfortunately this means that each site's admin/build/modules page has a significant load time and with enough modules/categories listed to hinder an admin's ability to quickly find something suited to a specific task. On Nov 16, 2009, at 1:15 PM, Matt Chapman wrote:
I would go low-tech and just create symlinks to sites/all/modules-advanced in each of the desired sites/sitename/modules . For mor etech, maybe write a shell script to add & remove these links automatically from a config file, if frequent maintenance is required.
-Matt
On Mon, Nov 16, 2009 at 10:55 AM, Justin Davis <justindavis@mail.utexas.edu>wrote:
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@mail.utexas.edu
http://drupal.org/project/systemmask
-----Original Message----- From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Justin Davis Sent: Monday, November 16, 2009 7:55 PM To: development@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
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@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Justin Davis Sent: Monday, November 16, 2009 7:55 PM To: development@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@mail.utexas.edu
On Mon, Nov 16, 2009 at 1:55 PM, Justin Davis <justindavis@mail.utexas.edu>wrote:
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
Try sites/all/modules sites/all/modules/advanced sites/sitename/modules
Doesn't module_rebuild_cache automatically recurse all subdirectories within sites/all/modules and sites/sitename/modules? I might have misunderstood this part of the bootstrap process, but using CCK as an example, downloading the CCK project archive includes several sub folders with additional dependent modules, each of which shows up separately at admin/build/modules. On Nov 16, 2009, at 1:51 PM, Earl Dunovant wrote:
On Mon, Nov 16, 2009 at 1:55 PM, Justin Davis <justindavis@mail.utexas.edu>wrote:
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
Try sites/all/modules sites/all/modules/advanced sites/sitename/modules
-- Justin Davis Liberal Arts ITS Sr. System Analyst justindavis@mail.utexas.edu
On Mon, Nov 16, 2009 at 3:11 PM, Justin Davis <justindavis@mail.utexas.edu>wrote:
Doesn't module_rebuild_cache automatically recurse all subdirectories within sites/all/modules and sites/sitename/modules?
Yes it does. The simple way to do what I think you're trying to do is put global modules in sites/all/modules, keep site specific modules in site specific subdirectories (sites/sitename-1/modules, sites/sitename-2/modules...) and assign permissions to user roles as appropriate.
participants (4)
-
Daniel F. Kudwien -
Earl Dunovant -
Justin Davis -
Matt Chapman