I believe the original question is not whether a module is enabled or not but whether an enabled module is actually being used *at all.*
It's up to the site builder to pay attention and know the purposes of each enabled. To me this seems like is an administrative issue, rather than a technical issue. On Sun, Jan 9, 2011 at 11:26 AM, Cameron Eagans <cweag...@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.benst...@gmail.com>wrote: > >> Originally posted to http://drupal.org/node/1017416: >> >> 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 >> > >
