Keep Name field visible & editable

Created on 19 October 2018, almost 6 years ago
Updated 30 January 2024, 8 months ago

I think there is a use case for keeping the Name field visible in the site_setting_entity form - e.g. where the type allows multiple entities (e.g. Department contact details), a user may wish to name each entity for clarity (e.g. "Dev team", "UX team").

Site builders could choose to then use something like AutoEntity Label to auto-generate & hide the Name field if desired.

Patch attached keeps the name field visible & editable for entities of site setting types with the 'multiple' option checked.

✨ Feature request
Status

Closed: outdated

Version

2.0

Component

Code

Created by

πŸ‡¨πŸ‡¦Canada bgilhome Victoria

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

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 calebtr

    This patch still applies to the 8.x-1.x branch.

    I'd be happy to work on screenshots and tests.

    Maintainers, would you prefer to see this against the 2.x branch?

  • πŸ‡¬πŸ‡§United Kingdom scott_euser

    Sorry completely lost track of this (5 years ago it seems!). Yes please to 2x if you're willing to help out, thank you!

  • Assigned to calebtr
  • πŸ‡ΊπŸ‡ΈUnited States calebtr
  • πŸ‡ΊπŸ‡ΈUnited States calebtr

    calebtr β†’ changed the visibility of the branch 3007994-keep-name-field to hidden.

  • Issue was unassigned.
  • πŸ‡ΊπŸ‡ΈUnited States calebtr

    I took a closer look at the 2.x branch and I don't think we need to change anything. The administrative description field is sufficient to distinguish one site setting from another of the same type.

    The Autoentity Label module seems to integrate just fine, after a cache refresh.

    I recommend you close this as outdated, or else if a release for the 1.x branch is planned, we can leave it Needs Work and switch the version back on this ticket to that branch.

  • Status changed to Closed: outdated 8 months ago
  • πŸ‡¬πŸ‡§United Kingdom scott_euser

    Thanks for checking! Given there is an upgrade path to 2x seems like someone needing this can just upgrade so I think we can close. Thank you!

Production build 0.71.5 2024