It would be helpful if this module could show us where modules are stored. I am aware of at least three locations:

  • /sites/all/modules
  • /sites/[sitename]/modules
  • /modules

Sometimes we're not able to strictly use only one of those three locations for module storage. E.g., I use multisite but sometimes need a local version of a module that's different than the "stock" version I deliver to the rest of my sites.

Comments

dww’s picture

dww
we/he/they
commented
Status: Active » Postponed (maintainer needs more info)

Can you propose where in the UI this information would be printed? A mockup screenshot would be most helpful. Thanks.

gpk’s picture

gpk commented

http://drupal.org/project/sitedoc says it provides ability to see the path of each module. It may also highlight situations where a module is uploaded into 2 or more of those places.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

subscribing...

aren cambre’s picture

aren cambre commented
Status: Postponed (maintainer needs more info) » Active

Proposal in #2.

dww’s picture

dww
we/he/they
commented
Status: Active » Postponed (maintainer needs more info)

I asked where in the UI it should go. I've never used sitedoc. Can someone post a screenshot or a mockup or at least explain an actual proposal for where this would go in the UI? Thanks.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

One idea is to place the extra path info in the 'Available updates' page (../admin/reports/updates), like so:

Drupal core/Modules/Themes
--------------------------------------------------------------------------------
[project_name (link)] [project_version] ([release_date])        [project_status]

Recommended version: [version (link)] ([release_date])         - Download (link)
                                                          - Release notes (link)


Development version: [version (link)] ([release_date])         - Download (link)
                                                          - Release notes (link)

Includes:
- Enabled: [submodule1], [submodule3], ...
- Disabled: [submodule2], [submodule4], ...

Path: [module_path]
--------------------------------------------------------------------------------

This would provide a path for the main module and its submodules in one place.

Idea #2 is to move this feature to the Moduleinfo project. Here's a screenshot that shows what the module does. It feels like the best place for this feature to go is the modules list (../admin/modules) + we will also be able to display paths for submodules as well. OTOH, that project seems abandoned and it will take (A LOT) longer for this feature to get implemented.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented
Status: Postponed (maintainer needs more info) » Active

...and I believe the right thing is to set this back to active.

Leeteq’s picture

Leeteq commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
aohrvetpv’s picture

aohrvetpv commented
Issue summary: View changes

Personally I would not want filesystem paths displayed in the modules list as suggested in #6. I have no need for that information. So I would hope this feature could be configurable (on or off) if implemented that way.

Leeteq’s picture

Leeteq commented

Personally, I think it would be most useful on the main modules page, perhaps as a filter tick mark beside the other selections? ("show enabled", "show disabled", "show module paths", ...)

It would be practical to be able to filter on this criteria to get a list of (enabled or disabled) modules stored in just one of those locations.
That would make this feature extra useful.

helmo’s picture

helmo commented

#2403371: Add option to display module path on admin/modules table adds paths to the main modules page. Having it also on the status update page would be convenient though.