[support] Many many modules

[Walt Daniels]

For the more obscure ones that you have enabled and don't know if they are
in use, disable them and test if anything is broken. If something breaks,
reenable them. Nothing is lost in the process. After running for awhile you
are pretty safe in uninstalling them. That does delete any data they may
have saved and there is no going back other than to a backup. You did
backup before doing any of the above playing around, right?


On Wed, Jan 30, 2013 at 9:47 PM, Richard Damon <Richard at damon-family.org>wrote:

> On 1/30/13 8:54 PM, Al Sessions wrote:
> > Thanks, Cindy.
> >
> > My problem is that I'm not sure what modules are in use.
> >
> > There are dependencies upon dependencies and I'm hesitant to remove
> > anything.
> >
> > What I was looking for is a module or snippet that would let me know
> > *every* module actually in use.
> >
> A module that is "Enabled" is in one sense "In use", as part of it is
> potentially run on every page access. A module that is disabled can't be
> in use.
>
> If you go to the admin/module page, it will list every module loaded on
> you site, and if it is enabled, and what it depends on and what depends
> on it.
>
> To my knowledge, there isn't an easy way to tell if disabling/removing a
> module will actually break any functionality for a site (of course many
> will clearly cause problems because you know they are being used, but to
> prove that an enabled module is safe it remove is hard to do.
>
> --
> Richard Damon
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20130130/f12e1fe7/attachment.html