This is a followup to #1953568: Make the bundle settings for entity reference fields more visible..

On entity reference bundle settings, if "Create referenced entities if they don't already exist" is checked and multiple target bundles are allowed, a dropdown "Store new items in" appears. However, it appears above the bundle selection checkboxes, which is weird:

Screenshot

it's weird having something change *above* the element you just interacted with...

That's why the reference method has to be on top. But for the same reason the allowed target bundles have to be next, right below the reference method, only then followed by the "Create referenced entities if they don't already exist" checkbox and possibly the "Store new items in" dropdown.

Also, per agreement in UX meetings, more important, particularly required elements should generally be at the top:

Moving these options closer to the top of the page is a good idea. We should normally put required elements first.

Problem: The very pragmatic reason for the current order seems to be that the single "Create referenced entities..." checkbox doesn't have a header, so if placed below the target bundle checkboxes, it would look like just another target bundle checkbox.

I'm not sure how to solve this, but we should figure out if there's a better approach to all of this.

In the end, I'm not even sure the "Create referenced entities..." checkbox belongs here at all. Finally, it seems only relevant to autocomplete widgets, so should possibly be a widget setting.

Issue fork drupal-3038199

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

Pancho created an issue. See original summary.

pancho’s picture

Issue summary: View changes
StatusFileSize
new16 KB
pancho’s picture

StatusFileSize
new18.88 KB

How about this?

proposal

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

smustgrave’s picture

This came up as the daily BSI target.

Can confirm this is still the case. Probably just need to play with the weight value so tagging for novice.

This will 100% need a summary update.

antojose’s picture

Issue tags: -Novice +Rotterdam2026

The Drupal Contribution Mentoring team is triaging issues for DrupalCon Rotterdam 2026, and we are reserving this issue for Mentored Contribution during the event.

After October 3, this issue returns to being open to all. Thanks!

Figure out where to make the change in the code, and make the merge request.

helga.cheberakha’s picture

DrupalCon Rotterdam 2026, I will be working on this issue.

helga.cheberakha’s picture

Status: Active » Needs review

The `auto_create_bundle` element in `DefaultSelection` had `weight: -1`. This property was removed to return the element to its usual order.

quietone’s picture

Component: entity_reference.module » entity system

The entity_reference module is no longer in core.