Contrib.social

UX: Editing a CER: first/second field option list

Open on Drupal.org →
Created on 17 February 2020, over 5 years ago
Updated 16 June 2025, 12 days ago

Problem/Motivation

The form for editing a single corresponding entity reference (form#corresponding-reference-edit-form) would be way more user-friendly if the "first field" / "second field" select lists included the label/human-readable name as a prefix, like how the bundles list has the entity type as a prefix.

I know human-readable names are per field instance, but the Views admin interface handles it somehow (they seem to use the "default" field label, which I imagine is the first one that existed? and then "also known as" -- which doesn't seem important here, I'm just explaining), so maybe we can use that as a model?

Alternatively, maybe just changing the option-list sort to be alphabetical by machine name, since that's what's shown as the choices.

Proposed resolution

Add human-labels to "first/second fields"
OR
Order the "first/second field" options alphabetically by machine name.

Remaining tasks

decide... do...

User interface changes

Depends on decision, but: changes to user interface text would be included.

Release notes snippet

(Major and critical issues should have a snippet that can be pulled into the release notes when a release is created that includes the fix)

Original report by [username]

(Text of the original report, for legacy issues whose initial post was not the issue summary. Use rarely.)

✨ Feature request
Status

Needs work

Version

5.0

Component

User interface

Created by

🇺🇸United States alison

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

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

  • Comment about 2 years ago →
    🇩🇪Germany Anybody Porta Westfalica

    Totally agree here. Just had the same points. The machine name could still be kept as first value in the select, having the human readable name in brackets second.

    Sorting the field names alphabetically totally makes sense!

  • First commit to issue fork.
  • Merge request !20Sort fields by machine name → (Open) created by mortona2k
  • Pipeline finished with Success
    12 days ago
    Total: 205s
    #523100
  • Comment 12 days ago →
    🇺🇸United States mortona2k Seattle

    Sorting the field machine names was easy, and a big QOL improvement when you have lots of fields.

    We could check this MR in now and improve it further later. Or create a separate issue?

  • Pipeline finished with Success
    12 days ago
    Total: 195s
    #523122
  • Comment 4 days ago →
    🇺🇸United States erutan

    Can confirm that #7 works on 10.5.

    Here's a quick patch that includes the labels as well if someone wants to take a look and possibly clean it up.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024