Often when managing a site with lots of modules, it gets difficult to enable a module, as even when you find it, it's dependencies can be hidden throughout the page. This patch makes each dependency listing into a link; when you click it, you are directed to that module on the page. If the module is missing, it links to the drupal.org project page instead.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | 260806-linkify.patch | 3.13 KB | bfroehle |
| #9 | module_page_links_02.patch | 4.38 KB | cwgordon7 |
| #2 | cuts_off_module_titles.png | 36.33 KB | senpai |
| usability_modules_page_links_01.patch | 2.81 KB | cwgordon7 |
Comments
Comment #1
senpai commentedGreat idea. Bookmarking for a test.
Comment #2
senpai commentedInstalled and tested on a freshly updated 7.x HEAD with clean db.
Clicking on 'required by' and 'depends on' links works pretty well. Unfortunately, the resulting display in FF2 Mac is half cut off by the hovering table header.
The attached picture shows what happened when I clicked on Locale.module's 'Required by: Content translation'.
Comment #3
senpai commentedWoops! Reset to CNR
Comment #4
cwgordon7 commentedHm. Any suggested workarounds?
Comment #5
Susurrus commentedYou could either use an in-page link to the module above it or you could use some javascript to find the position factoring in moving table headers and scroll the page to that position. I'm not so sure how elegant a JS solution would be, but I don't like the other suggestion I made either.
Comment #6
cwgordon7 commentedModule above it is out of the question because that won't line up properly in all cases, so I guess a JS solution...
Comment #7
senpai commentedTarget the id of the enclosing div, but scroll the page +25px to compensate for the floating table header?
Comment #8
Jaza commentedIn the case of the module not being in the site's codebase, we have no guarantee that a particular module has its own drupal.org project page, it may be part of a package of modules. So simply linking to http://drupal.org/project/modulename will result in plenty of broken links.
I doubt that this will make it into D7 (if indeed it's appropriate to go in at all), but bumping and leaving in the D7 queue anyway.
Comment #9
cwgordon7 commentedUpdated and fixed patch attached. Note that this will not work in the overlay at the moment for the same reason the tableheader won't work in the overlay - once the patch at #649662: Sticky tableheaders don't work in Overlay is committed, this patch should work in the overlay as well.
Comment #10
realityloop commentedEven with overlay disabled this still moves the desired element off top of the page.
Comment #11
casey commented#787940: Generic approach for position:fixed elements like Toolbar, tableHeader
Comment #12
bfroehle commentedUploading a re-rolled version of #9 but without the JS.
It is the responsibility of tableheader.js not to mess up every link to an anchor in the table, not the responsibility of everybody using a sticky header table. This is going to be dependent on #787940: Generic approach for position:fixed elements like Toolbar, tableHeader (or some other tableheader fix), so I'm bumping to 8.x-dev.
Comment #13
yoroy commentedOverall this seems symptom fixing to me. I would hope we can improve this workflow on a more fundamental level than this. Modules page in its current state is not helped with adding bits and pieces to it. Handling dependencies more elegantly is definately something to pursue. Adding links that make the page jump up and down is probably not the best option there. Could we for example filter or group modules that share dependencies?
Comment #20
dpiComment #29
quietone commentedIt has been thirteen years since there has been activity on this issue. In the last comment yoroy pointed out that adding links that make the page jump up and down is not the best option and suggested some kind of filtering or grouping modules that share dependencies? There has been no discussion here on that point.
Is there interest in pursuing the filtering or should this issue be closed? I am setting the status to Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Comment #30
quietone commentedAH, found the issue about redesigning the page, #2035079: [PP-1] Figure out what to do with the install/uninstall modules page.
Comment #31
quietone commentedThanks for the work on this issue. There has been no work on this task for 14 years, except to ask if this issue is still relevant. Therefor, closing.
If there is work to do here, then either re-open the issue or open a new issue and reference this one. If the choice is to use this issue then add a comment change make sure to change the issue status to 'Active'.