| #
d4f83172 |
| 31-Aug-2023 |
Andreas Gohr <andi@splitbrain.org> |
code style: line breaks
|
| #
177d6836 |
| 31-Aug-2023 |
Andreas Gohr <andi@splitbrain.org> |
coding style: control flow whitespaces
|
| #
d868eb89 |
| 30-Aug-2023 |
Andreas Gohr <andi@splitbrain.org> |
codestyle adjustments: function declaration braces/spaces
|
| #
8c7c53b0 |
| 30-Aug-2023 |
Andreas Gohr <andi@splitbrain.org> |
codestyle adjustments: class declaration braces
|
| #
467c1427 |
| 29-Aug-2023 |
Andreas Gohr <andi@splitbrain.org> |
Apply rector fixes to config plugin
|
| #
0772dde2 |
| 26-Oct-2022 |
Andreas Gohr <andi@splitbrain.org> |
Fix handling of unknown array settings
When a plugin used an array setting and was then installed, the old configuration can remain in local.php. It is handled by the SettingUndefined class. However
Fix handling of unknown array settings
When a plugin used an array setting and was then installed, the old configuration can remain in local.php. It is handled by the SettingUndefined class. However this class used the base out() mechanism which didn't know about arrays. The result was a fatal error resulting in a completely empty config file.
This moves the error handling from the SettingArray class to the base class which fixes the original problem.
It also adds a check if the Writer is about to write a completely empty config file and refuses to do so, throwing an Exception.
Probably related to #3777
show more ...
|
| #
f00299d8 |
| 20-May-2018 |
Andreas Gohr <andi@splitbrain.org> |
extract save checking into own method
Instead of having the out() method return empty strings, a new method tells the writer if a setting should be saved or not. Only then the out() method is called.
|
| #
0a5b05eb |
| 18-May-2018 |
Andreas Gohr <andi@splitbrain.org> |
Moved settings to their own namespace
|