- 🇬🇧United Kingdom catch
Marking duplicate of 🐛 Add proper deprecation notices in config entity presave bc layers Active which is a much newer duplicate issue opened by me, but has more up-to-date info on it.
Opening as a follow-up from #2810097: Allow views to provide the canonical entity URL of all entities, not just nodes. → but this applies to other previous issues too.
When we have bc layers for configuration entities, we've implemented those by implementing a presave hook so that the config saves correctly. This covers both load/save upgrade paths, but also default configuration from modules.
In 9.x we'll want to remove those bc layers, but to actually warn module authors that they're relying on deprecations, we'll need to trigger_error() when outdated configuration is saved.
Putting in configuration entity system since it's a general issue.
Closed: duplicate
11.0 🔥
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Marking duplicate of 🐛 Add proper deprecation notices in config entity presave bc layers Active which is a much newer duplicate issue opened by me, but has more up-to-date info on it.