- 🇳🇿New Zealand quietone
This is changing the UI so adding tags and updating the issue summary.
#2494989: Don't render main help pages on modules page just to generate help links - can lead to high memory usage on form submit → removes the call for field_hook, though we have the issue of calling all module's field/widget/formatter, just to render help content.
Remove the list of modules from field_help() and place it as separate page and link it from help content.
Convert to an MR
Review
Screenshots available from the issue summary
No list of field type/widget/formatter-providing modules on the field help page. Will be listed in separate page.
Needs work
11.0 🔥
Last updated
Makes Drupal easier to use. Preferred over UX, D7UX, etc.
Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This is changing the UI so adding tags and updating the issue summary.