- Issue created by @prudloff
- Merge request !66Issue #3359679: SettingsForm should not use overridden config → (Closed) created by prudloff
- last update
over 1 year ago 32 pass - Status changed to Needs review
over 1 year ago 1:18pm 11 May 2023 - Status changed to Postponed: needs info
over 1 year ago 12:29pm 2 June 2023 - 🇩🇪Germany gbyte Berlin
Your reasoning makes sense but I wonder if you know of any other places (like core) known to do it your way?
- 🇫🇷France prudloff Lille
It is explained here → .
The core uses it for example in
GDToolkit::buildConfigurationForm()or inThemeExperimentalConfirmForm.🐛 Prevent saving config entities when configuration overrides are applied Needs work also talks about preventing saving the configuration when it contains overrides.
- Status changed to Needs work
over 1 year ago 12:59pm 2 June 2023 - 🇩🇪Germany gbyte Berlin
This makes sense. I'm happy to merge this as soon as all forms are taken under account (including submodules). Feel free to grab it!
- First commit to issue fork.
- last update
over 1 year ago 32 pass - Status changed to Needs review
over 1 year ago 5:01pm 5 June 2023 -
gbyte →
committed 8b4c37a2 on 4.x authored by
prudloff →
Issue #3359679 by prudloff, elber, gbyte: SettingsForm should not use...
-
gbyte →
committed 8b4c37a2 on 4.x authored by
prudloff →
- Status changed to Fixed
over 1 year ago 6:46pm 8 June 2023 Automatically closed - issue fixed for 2 weeks with no activity.