- Issue created by @tstoeckler
- 🇩🇪Germany tstoeckler Essen, Germany
Note that for Config Ignore there is a weird message that shows up in the UI at least, see ✨ Misleading message on "admin/config/development/configuration" about configurations handled via config_overlay Active .
I did see some issues with the old Config Split on a project, but didn't investigate yet, so possibly the resolution here will be just to add a Composer conflict with the older versions, but not sure yet.
- Merge request !25First stab at fixing tests for Ignore 2.x and Split 1.x → (Merged) created by tstoeckler
- Status changed to Needs work
over 1 year ago 11:38am 26 February 2024 -
tstoeckler →
committed b96de409 on 2.x
Issue #3422934 by tstoeckler: Revamp Config Ignore...
-
tstoeckler →
committed b96de409 on 2.x
- 🇩🇪Germany tstoeckler Essen, Germany
This was quite a ride. In the end we cannot support Config Ignore 1.x and 2.x because we cannot properly hook into the order at the right places with Config Filter and we cannot support Config Split 1.x because that in turn only supports Config Filter 1.x which does even allow us to run after any of the filters.
As part of this crazy adventure trying out various combinations I did end up simplifying things a bit by introducing the
$settings['config_overlay_priorities']setting and revamping the documentation quite a bit. Automatically closed - issue fixed for 2 weeks with no activity.