This came up a few times before in #1891126: Extend / Modules page disabled red signal concerned usability participants as well as other various UX studies/issues.

When there is a missing module required in order to enable others, the next natural thing for users is to visit d.o and search for that module in order to download it. Why not improve this UX by making the names of missing modules be actual links to the project in question so that users skip the searching part of this task.

This may sound as a feature request, but I'd like to see it as a UX task.

Comments

internetdevels’s picture

Status: Active » Needs review
StatusFileSize
new1.09 KB

Status: Needs review » Needs work

The last submitted patch, 1: drupal-core-missing-required-module-link-2182493-1.patch, failed testing.

rootwork’s picture

Status: Needs work » Needs review
StatusFileSize
new2.25 KB
new1.16 KB

This adds matching test coverage (which is why the testbot was failing).

Status: Needs review » Needs work

The last submitted patch, 3: drupal-core-missing-required-module-link-2182493-3.patch, failed testing.

klonos’s picture

The logic behind this patch seems mostly right, but we need to account for cases where the required dependency is a submodule of a project. In such cases we need a way to know which the parent project is because the generated URL would be http://d.o/project/[submodule_name] and that would lead to a missing page.

Just a heads up.

pasqualle’s picture

and what about modules not hosted on drupal.org?
drupal project can define its url with "project status url" in module info file

D8 UpdateFetcher::getFetchBaseUrl()
D7 module info file handbook

klonos’s picture

Status: Needs work » Closed (duplicate)

I agree. This is a duplicate of #210243: Allow for an optional 'download link' entry in the .info/.yml files so that missing module dependencies can be rendered as links.. The title of the other issue is too vague though and I missed it when I check for already filed issues.

klonos’s picture