Thanks, Cameron - doesn't that just show which modules are enabled, though? Say I'd enabled a module but then found that it wasn't necessary for the launched site, but had forgotten to disable that module. As I understand it, that module would still show up with status='1' but the site wouldn't actually be using it.
--Jim
--
My IM and Skype details are at http://state68.com/contact
On 9 January 2011 19:26, Cameron Eagans
<cweagans@gmail.com> wrote:
I don't think you'd even need a module to do this. You can get a list of currently used modules by doing:
SELECT name FROM system WHERE type='module' AND status='1';
You could likely write a quick script to compare the list returned by that SQL statement to your modules list.
Thanks,
Cameron
On Sun, Jan 9, 2011 at 12:04, James Benstead
<james.benstead@gmail.com> wrote:
I have a list of 60+ modules that I download, via drush, to each new Drupal site that I build. I then enable whatever modules are needed for the specific site I'm working on as I carry out the build.
This means that once the site is launched, there may be modules that are not being called by Drupal core but that are still enabled and/or installed.
Is there an automated way - a specific module, for example - that will tell me which of the modules that are enabled on a site are being called by Drupal core?
Secondly, is there any performance implication for having lots of modules installed on a site if they are not enabled?
The answer to the second question seems to be "no". And It doesn't seem that such a module does exist - would it be technically possible to write this module for D6?
--Jim
--
My IM and Skype details are at http://state68.com/contact