Problem/Motivation

In creating a Custom Field where the 'primary' field inside it is a term reference field, are only:

  • Autocomplete
  • Hierarchical Select
  • Radios
  • Select

For our use case and i expect many others, Inline Entity Form - https://www.drupal.org/project/inline_entity_form - is an important option to have. (Actually the need is for IEF Complex Open - https://www.drupal.org/project/ief_complex_open - which i am a maintainer on, so if the change has to be made somehow on a per-specific-widget itself, i can do that.) Presumably there is a strong reason that all entity reference supporting widgets are not automatically allowed?

Imagine the submodule for entity browser may have some clues but also think this widget swap could/should be simpler?

Thanks!

Side note, removing D11 support from the 3.x branch results in people with Drupal 11 getting version 3.1.15, not the latest 4.x release candidate, until that becomes the recommended branch and/or has a stable release (i think only the latter matters for usual composer settings). I am riding the wave with 4.0.x now; release candidates are for the faint of heart.

Thank you for this remarkable module!

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

mlncn created an issue.

apmsooner’s picture

apmsooner commented

Hi,

The standard field widgets are not a one to one adaptation for this module and in most cases I’ve tried to avoid extra dependencies and handle my own way when i can simply do it better. IEF is a little more complex however so will have to look at this when i get time. Im aware of the composer issues and a stable 4.x version will be released next week that will resolve that.

mlncn’s picture

mlncn commented

Thanks! Yes, i am looking at https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... and realizing the expectation is that both widgets and formatters extend from a Custom Field base, rather than existing Drupal widgets being able to easily "opt in"— but your outline in this case of how the twain should meet would be greatly appreciated, and i hope open up the path for more contrib widgets/formatters to work with Custom Field.

apmsooner’s picture

apmsooner commented

The sub-fields have their own plugin system for valid reasons but extending them are simple: https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib...

That being said, there shouldn’t be much need for widgets beyond what is provided particularly when next release is out that will introduce some new date field features.