By jim0203 on

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?

⋅ Categories: Drupal 6.x

Comments

jaypan’s picture

jaypan
Location Victoria, BC
commented

I don't think there is any automated way to tell which modules are enabled but not in use, as it would take a human touch to know if/when a module is being used.
There are no performance issues with having unused modules on the site if they have been uninstalled and not just disabled. They need to be uninstalled though in order to remove the tables from the database. But if they are just in the modules folder (and uninstalled), the only performance hit will be on the modules page itself when it has to load them all to give the option to install them.

Contact me to contract me for D7 -> D10/11 migrations.

jim0203’s picture

jim0203 commented

Thanks for this, Jay - I cross-posted to the Development mailing list and it seems that you're correct: there isn't a module that does this, yet. If and when I get the time I might have a go at writing it.

xaa’s picture

xaa commented

hi,
maybe tries the module_filters here : http://drupal.org/project/module_filter. I think that it's going on the way you want.

kclarkson’s picture

kclarkson commented

I think this would be an important module for us who take on old projects. Also I am famous for forgetting to disable a module after I have found a better way to do something.

subscribe

Kaleem S. Clarkson
www.kaleemclarkson.com

hugeknot’s picture

hugeknot commented

I could definitely use something like this!
Subscribe.

john_b’s picture

john_b commented

Does this module help http://drupal.org/project/sitedoc ? No D7 version but it is a D6 thread.

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors

jim0203’s picture

jim0203 commented

Not according to the module maintainer: http://drupal.org/node/1412752

Still looking for a solution ...

cilefen’s picture

cilefen commented

drush -y @sites pmi module_name|grep Status

jaypan’s picture

jaypan
Location Victoria, BC
commented

I just re-read my original post, and I wanted to add to it:

Modules can provide any number of types of functionality. For example, I may create a module that only does one thing - it creates a page called 'page', that prints out the one word, 'page'. Anyone clicking a link to my page page, would see the word page.

This module is not being used though - no one ever visits this page. How would you ever automate this to know if it is being used or not?

Another module may do one single thing - it changes the title of a form element from 'Username' to 'name'. This can be done with about 20 lines of code in a module. Maybe this isn't necessary anymore - there is no way to automate the decision on whether or not this is necessary.

Modules can provide any number of functionality. Some of it may be working but unnecessary. It requires a human to go in, look at what the module does, and determine whether or not it should be turned off. Because of the vast possible functionality that a module can implement, a machine couldn't effectively determine which functionality is (un)necessary or (un)used.

Contact me to contract me for D7 -> D10/11 migrations.

raulmuroc’s picture

raulmuroc commented

The module is called Unused Modules

Drupal Association individual member