#94156Configuration Presets - Debug settings should reflect custom changes
Description
When the configuration preset is set to (e.g.) “live” and some (of this presets related) values are changed using AdditionalConfiguration.php, the backend form still shows “live” (the same for “debug”).
This is confusing, espacially in case of any custom values being deployed using AdditionalConfiguration.php.
Possible improvement: As soon as any of a presets related values differs from the original preset value, the preset “custom” should be marked as active. If all preset values match the original preset, this preset should be marked as active.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[FEATURE] Configuration Presets - Debug settings should reflect custom changes Resolves: #94156 Releases: main