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]
Lookup] Records shown for some entities but not others - Microsoft
Fix the UX of Entity Reference fields [#2116551]
Solved: Resource at '/sites.html/content' not found: No re
Fix the UX of Entity Reference fields [#2116551]
EVA and Entity Reference Use Case How-to
Fix the UX of Entity Reference fields [#2116551]
Source: For Each Message: Object reference not set to an instance
Fix the UX of Entity Reference fields [#2116551]
Solved: VISA: (Hex 0xBFFF0011) Insufficient location information
Fix the UX of Entity Reference fields [#2116551]
Libero Config Get File - Colaboratory
Fix the UX of Entity Reference fields [#2116551]
entities - How to use the Render Views filters as select list
Fix the UX of Entity Reference fields [#2116551]
Lookup] Selected record tag is emtpy or shows No name
Fix the UX of Entity Reference fields [#2116551]
Federated search for Splunk platform remote deployments - Splunk
Fix the UX of Entity Reference fields [#2116551]
c# - System.Data.Entity.Infrastructure
Fix the UX of Entity Reference fields [#2116551]
Improve entity reference validation error messages [#3138631
de por adulto (o preço varia de acordo com o tamanho do grupo)