Fix the UX of Entity Reference fields [#2116551]

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.

Remove Taxonomy term reference field in favor of Entity reference

8 - How to display entity label using entity reference field

8 - Entity Reference: Filter by an entity reference view not

Federated search for Splunk platform remote deployments - Splunk

8 - View for Entity Reference reverse, backwards forwards - Drupal

Add Entity reference field [#1801304]

Add Entity reference field [#1801304]

8 - View for Entity Reference reverse, backwards forwards - Drupal

Solved: VISA: (Hex 0xBFFF0011) Insufficient location information

8 - Entity Reference: Filter by an entity reference view not

Add Entity reference field [#1801304]

UD Field Assistance - Post E9->E10 Migration - ERP 10 - Epicor

Fix UX of entity reference field type selection [#1847590

How to Enforce Selection of Published Contents in Entity Reference

Entity Reference Ajax Formatter