User login

Agaric wants easy listing of a site's enabled Drupal modules including missing modules

Searched words: 
drupal list enabled modules drupal module generate list enabled modules drupal devel show enabled modules drupal site recipe modules drupal list modules used module listing enabled_modules module_list list_modules Modules used on this site Here is the current list of major modules in use on this site complete site recipe

Agaric wants our sites to generate a list of enabled modules.

Update: So we made an enabled modules module.

We want each enabled module to be listed even if the module code isn't there. This is convenient when moving messy sites.

Ideally the list of modules could communicate back to a central site and let you know what's up, but that functionality should actually live with update_status.

Two similar needs means we make a module!

From the initial project page:

The enabled_modules module provides two features that serve two purposes:

  1. List all enabled modules (whether the installed code base is present or not– enabled but absent modules are flagged missing).
  2. [Not yet implemented] Provide a block showing recently enabled modules (with links to the module's administration tasks) and provide a list of recently disabled modules.

The first functionality is useful for moving sites to a whole new code base and rebuilding fresh with only the modules actually in use.

The second functionality is very useful to administrators to provide administration links to the modules they just enabled.

The latter feature is not that easy to do, as there are no hooks that I can find that fire to announce the installing, enabling, disabling, and uninstalling of modules (except to call hooks in the affected module itself). The system table itself saves no timestamp data. I am interested in hearing from anyone working on revision functionality for Drupal administration, so we can share the approach and data. I think it will have to be a form_alter function that provides its own submit handler.

Permission to 'view enabled modules'

Notes on the making of

http://api.drupal.org/api/function/drupal_system_listing/5

http://api.drupal.org/api/function/system_get_files_database/5

drupal using theme_table

How to use theme_table
http://drupal.org/node/53065

Resolution

Comments

Also todo

Make the missing enabled modules listing a page of its own, and also a block that automatically appears on the admin/build/modules page if there is a missing module.

Been thinking about this module because I do find it useful:

Do you folks have anything I can pass along about favorite modules of yours?

>I'd love to hear what modules you find useful.
>
> What modules have you "discovered?" that feel
> like little--or
> big--treasures? (especially the ones that are not in the
> top 10 or 20
> here:
> http://drupalmodules.com/top-downloads [2]

My own: http://drupal.org/project/enabled_modules

I'm sure there are better practices, but I like to use it when I move a site-- either before or after-- to see exactly what modules I need to replace.

Enabled Modules Feature Request

I would like to output to a text file a list of all enabled modules.

I would also like the ability to read back such a file and automatically enable all files on that list. This would save a lot of time while doing upgrades to Drupal core, such as the upgrade from Drupal 5.9 to 5.11 which I am about to do.

Then of course if you could create the feature to disable all modules with one button that too would save a lot of time.

I was looking for this

I was looking for this functionality too. I needed it because I'm upgrading Drupal and apparently you need to turn off all your enabled modules before you do the upgrade. I needed an easy way to remember which modules to turn back on.

As a workaround I printed the "/admin/build/modules" page to a PDF file for reference after the upgrade.

Here is a feature request I found that was already in works: http://drupal.org/node/99529

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • Syntax highlight code surrounded by the {syntaxhighlighter SPEC}...{/syntaxhighlighter} tags, where SPEC is a Syntaxhighlighter options string or "class="OPTIONS" title="the title".
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.