The "Manage display" tab label when editing an entity should be "Manage displays" (plural) instead.

Created on 31 January 2014, over 11 years ago
Updated 11 March 2025, about 2 months ago

I'm merely suggesting this for UI text posterity/consistency. That tab doesn't let people manage a single display but all available displays (default, teaser, full content, RSS etc.). Having it as plural helps to convey that there's more than one display available and actually more exist waiting to be configured. The "Manage form display" tab on the other hand is fine as is because it handles only one form.

I initially thought of suggesting "Manage display settings" or even "Manage display modes" instead because the fieldset with the rest of the display modes has a "Custom display settings" label and the help text in the same fieldset says "Use custom display settings for the following modes"). In fact I think that the use of the word "modes" would make much more sense and would help in educating people of what these things are actually called. I didn't go ahead with suggesting it though because it would be a "drastic" change from the text we now have in place.

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

user interface text

Created by

πŸ‡¦πŸ‡ΊAustralia klonos 90% Melbourne, Australia - 10% Larissa, Greece

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024