Problem/Motivation

Here is a real UX gotcha. When I visit my Drupal site, and hit the 'Extend' button, there is a list of modules with interesting names, and as a new site builder or site owner with admin permissions, I wonder what what happens if I enable them. I look for a 'Help' link on the modules page, then on the help page. There is none - not even a link to a help page on d.o. Then I 'twig' that the answer is 1. enable interesting looking modules; 2. read help; 3. uninstall said module; 4. repeat for next module whose name excites my curiosity. An explanation on the Help page that help only works for enabled modules would look pretty bad, but would be better for users than what we currently have.

Proposed resolution

Can hook_help be made to run for all the modules found in the relevant paths, not just the enabled ones?

User interface changes

Help links and text will appear for all modules in the codebase, not just enabled ones.

Comments

John_B created an issue. See original summary.

dawehner’s picture

Well, we can't really do this because hook_help() requires a proper module installation as people call out to code / routes of that module. This will break easily otherwise.

john_b’s picture

Good to have that idea put to bed, if only because it means there is a need to look elsewhere for a solution. There is still a significant UX problem. What about putting Advanced Help in core as a replacement for hook_help and Help module, and letting that display Help for all modules in the codebase?

Not sure whether the solution could be linked to #1918856: Put each module's help into a separate Twig file. Although to my mind this is more pressing because I see it as a UX problem whereas that is a DX issue.

jhodgdon’s picture

Version: 8.0.0-rc1 » 8.1.x-dev

Feature requests are 8.1.x material at this point.

I've created a meta-issue to discuss features for the Help system in general, because we have a whole bunch of "improve the help system" issues that are each addressing one little part of the problem. This has been added to it as related. #2592487: [meta] Help system overhaul. Note that this is in the Problems section and not in Proposed Resolution like some of the other issues, because there is not a proposal here for fixing the problem. (As a note, neither Advanced Help nor the Twig file idea would let help be displayed while the module is not enabled; both of these have been added to the summary of that other issue too.)

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

andypost’s picture

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

amber himes matz’s picture

Status: Active » Closed (outdated)
Related issues: +#3360133: Display links to help topics provided by uninstalled modules

We have a new system for help which is replacing hook_help and that is help topics, which is part of the core help module. There is a newer issue (#3360133: Display links to help topics provided by uninstalled modules) that is framed in terms of help topics and displaying related help topics from uninstalled modules that I think is more relevant. So I'm going to close this issue as outdated and add commit credit over on that issue for when it gets worked on.