This issue is spun off from 📌 Adopt PluginExists validator in relevant places RTBC .
In that issue, we added validation for the field.field_settings.entity_reference:handler property in config schema, validating that the entity reference selection handler does, in fact, exist.
To manage scope and prevent potential backwards compatibility breaks, we are currently allowing the fallback plugin ID (broken) to be stored in config. But that's not really okay - config should never be referring directly to a fallback plugin, except in very limited circumstances (like block_content:UUID plugins, which might refer to a block content entity that doesn't exist).
Remove the allowFallback: true line from field.field_settings.entity_reference:handler's PluginExists constraint. Then fix any tests that break because of that, and create an update path if necessary.
Shouldn't be any.
Unclear, but there shouldn't be.
Possible; TBD.
TBD
Postponed
11.0 🔥
Last updated
Hmm, not sure about this fix, think I need some help here.
Not sure why but javascript tests seem to be consistently failing, even after a re-run.