Actions
Feature #87185
open
Ideas to improve cooperation between BE "All Config" and AdditionalConfiguration.php
Status:
New
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2018-12-17
Due date:
% Done:
0%
Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:
Description
If an AdditionalConfiguration.php is in place, values entered in the backend will still be added to LocalConfiguration.php where they will be ineffective. This can lead to confused debugging.
I propose a few approaches:
- Simple: display a global warning message if AdditionalConfiguration.php is detected
- Medium: disable fields where the value is overwritten in AdditionalConfiguration.php
- Best: Read AdditionalConfiguration.php as well when building the "All Configuration" list and show those values in read only fields, along with a hint that they have to be edited manually in the code.
PS: the category "Install Tool" is outdated for TYPO3 9.5, should I have picked another?
Updated by Riccardo De Contardi over 1 year ago
- Related to Feature #94650: Show actual configuration value if configured in AdditionalConfiguration.php added
Updated by Riccardo De Contardi over 1 year ago
Urs Braem wrote:
- Simple: display a global warning message if AdditionalConfiguration.php is detected
According to what I see on #94650 this is already in place: There is a yellow note that warns the user that there might be an AdditionalConfiguration.php file that overrides the value written in the field below.
Actions