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.
Fix the UX of Entity Reference fields [#2116551]
How to Enforce Selection of Published Contents in Entity Reference
Fix the UX of Entity Reference fields [#2116551]
Libero Config Get File - Colaboratory
Fix the UX of Entity Reference fields [#2116551]
no unique index found for the referenced field of a primary table
Fix the UX of Entity Reference fields [#2116551]
Add Entity reference field [#1801304]
Fix the UX of Entity Reference fields [#2116551]
entities - Use entity reference to target revisions of an an
Fix the UX of Entity Reference fields [#2116551]
Fix the UX of Entity Reference fields [#2116551]
Fix the UX of Entity Reference fields [#2116551]
Add Entity reference field [#1801304]
Fix the UX of Entity Reference fields [#2116551]
Libero Config Get File - Colaboratory
Fix the UX of Entity Reference fields [#2116551]
No search fields to select when creating an entity reference view
Fix the UX of Entity Reference fields [#2116551]
Fix the UX of Entity Reference fields [#2116551]
Fix the UX of Entity Reference fields [#2116551]
Having multiple relations in edit/create form - User Experience
de por adulto (o preço varia de acordo com o tamanho do grupo)