Allow buttons for all destination bundles

Created on 23 October 2024, 7 months ago

Problem/Motivation

Currently, when the entity reference allows for more than one target bundle, this module's widget creates a dropdown to select what bundle to use when creating an entity to reference:

Particularly if there are only a small number of choices available, it would be better UX to have separate buttons instead. In the example above, it would be better to have buttons labelled "Add new link" and "Add new location".

Steps to reproduce

On a content type, create an entity reference field that allows for two or more target bundles. Use a complex IEF widget for the form display.

Proposed resolution

Allow a site builder to have multiple buttons instead of a dropdown. Perhaps it would be easier if this was a configuration option on the current widget, but creating a new widget would be another possibility to consider.

✨ Feature request

Status

Active

Version

3.0

Component

User interface

Created by

🇨🇦Canada mandclu

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @mandclu
Comment 7 months ago →
🇨🇦Canada mandclu
Comment 3 months ago →
chrisac
Comment 3 months ago →
chrisac
Comment 20 days ago →
chrisac
I think it looks good when only new nodes are allowed, but if user can also add existing nodes it may gets a bit confusing:

Should the "Add new" and "Add existing" buttons be grouped together by bundle for clarity (eg vertically)?
Or would it be better to keep the "Add new" buttons for each bundle, while merging all "Add existing" buttons to one that will refer to any bundle?
From what I can tell filtering by bundle is not applied to the results of autocomplete field in the add_existing form, so would different buttons for each existing bundle really be needed?

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024