I would add one little thing to that query:
SELECT name FROM system WHERE type='module' AND status='1' AND
filename NOT LIKE 'module/%';
That way you don't get Drupal's core modules in the list.
Jamie Holly
http://www.intoxination.net
http://www.hollyit.net
On 1/9/2011 2:26 PM, Cameron Eagans 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