Make "These settings apply to the field everywhere it is used" clearer

Created on 26 March 2013, over 12 years ago
Updated 3 April 2025, 3 months ago

Problem

Currently the field settings on every field contain the intro:

These settings apply to the Body field everywhere it is used.

For example, see admin/structure/types/manage/page/fields/body/field-settings

Consider, though, a situation where:

  • we have a field field_description
  • in node type Basic Page it is called "Main Area"
  • in Article it is called "Description"
  • in User it is called "Bio"
  • In the taxonomy term Category it is called "Category Summary"
  • In Article there is another, unrelated field field_xyz called "Main Area"

In the above example it is misleading to say, in admin/structure/types/manage/page/fields/field_description/field-settings, "These settings apply to the Main Area field everywhere it is used"

Proposed solution option 1

  • Do not put, as a field label, the label of one of its random instances. (Fields have no label; field instances do).
  • In admin/structure/types/manage/%/fields/%/field-settings, change the intro to something resembling what is in the enclosed image

Related: #1916738: Make it more obvious to those new to the concept of field translation that all instances of the field are translatable β†’

Proposed solution option 2

To avoid cluttering the field settings page, provide a link to admin/reports/fields; and specify the field machine name instead of (or in addition to?) the label of one of its instances.

✨ Feature request
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

field system

Created by

πŸ‡¨πŸ‡¦Canada alberto56

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 sharing your idea for improving Drupal.

    We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. 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!

  • Status changed to Closed: outdated 3 days ago
  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Since there's been no follow up in 3+ months going to close out. If still a desired feature please re-open updating any missing information

    Thanks!

Production build 0.71.5 2024