That's really interesting - would be an interesting problem to try and define the metric for such a module. Almost certainly something for any version 2+. Thanks. --Jim -- My IM and Skype details are at http://state68.com/contact
On 11 January 2011 11:32, Franz Glauber <franz.glau...@gmail.com> wrote: > I guess this is almost an AI module, as it would take a whole set of > parameters (like Gábor said) and somehow classify the modules according to a > certain "degree of use". The monitor could then issue some report about all > modules below a certain threshold, to which it would expect a reaction from > the site administrator wethere to mark them as "needed" or to disable them. > This later reaction could even be a learning process for the classifier > itself, or just a "don't mess with nuclear missiles" flag on that specific > module, causing it to miss the next round of classifying. > > > On Mon, Jan 10, 2011 at 7:10 AM, Giovani Spagnolo < > giov...@telematicsfreedom.org> wrote: > >> I agree with Carl it is an administrative task and should be let to site >> Admins, but could the modules list page feature a "last used" timestamp >> column to help site admins know when it was the last time a module was used? >> This info could be helpful for the auditing purposes James explained in >> his other posting. >> >> Inviato da iPad >> >> Il giorno 09/gen/2011, alle ore 20:55, Carl Wiedemann < >> carl.wiedem...@gmail.com> ha scritto: >> >> 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> >> 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> >>> james.benst...@gmail.com> wrote: >>> >>>> Originally posted to <http://drupal.org/node/1017416> >>>> 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> >>>> http://state68.com/contact >>>> >>> >>> >> > > > -- > Franz > > http://ciudaddelpico.com > > Sent from my laptop >
