Fix the UX of Entity Reference fields [#2116551]
Por um escritor misterioso
Descrição
Problem/Motivation [#1757452] added config entities back into the selection here, after this was deliberately taken out in [#1801304] taken out of the UI since the initial ER pach didn't support config entities. This leads to completely silly lists of possible things to reference like this: Here you have your "90% case" stuff (Content, Users, Files, etc.) buried hopelessly in amongst a bunch of "1% or less case" stuff like "Editor" and "Text format" and "Breakpoint group." This needs to be fixed, because it makes what's already a challenging field to use about 600x more difficult.
Add Entity reference field [#1801304]
c# - System.Data.Entity.Infrastructure
Error in Action for missing values
entities - How to use the Render Views filters as select list
Prioritize 'add existing' in nested entity creation UX to prevent
drupal - How can I limit an entity reference selection to a
Remove Taxonomy term reference field in favor of Entity reference
How to Enforce Selection of Published Contents in Entity Reference
Entity Reference Views
Custom Action Invalid Argument Error : Entity Reference cannot
Entity Reference view to populate select list for reference field
Inspect the configured ER component to prevent runtime issues
Error in Action for missing values
Customize Entity Reference Autocomplete Results using Views in
de
por adulto (o preço varia de acordo com o tamanho do grupo)