Fix the UX of Entity Reference fields [#2116551]

Por um escritor misterioso
Last updated 22 dezembro 2024
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.
Fix the UX of Entity Reference fields [#2116551]
Custom Action Invalid Argument Error : Entity Reference cannot
Fix the UX of Entity Reference fields [#2116551]
Fix the UX of Entity Reference fields [#2116551]
Fix the UX of Entity Reference fields [#2116551]
No unique index found for the referenced field of the primary
Fix the UX of Entity Reference fields [#2116551]
Entity Reference Referential Integrity
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]
Add Entity reference field [#1801304]
Fix the UX of Entity Reference fields [#2116551]
Solved: VISA: (Hex 0xBFFF0011) Insufficient location information
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]
Entity Reference Ajax Formatter
Fix the UX of Entity Reference fields [#2116551]
Add Entity reference field [#1801304]

© 2014-2024 immanuelipc.com. All rights reserved.