Issue Feature Closed

#87185Ideas to improve cooperation between BE "All Config" and AdditionalConfiguration.php

Urs Braem 12/17/18, 12:51 updated 11/13/26, 11:18

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?

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 3

  1. Riccardo De Contardi commented <span data-processor="relativetime" data-value="2023-05-28T15:34:04+00:00" > 05/28/23, 15:34 </span>

    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.

  2. Benni Mack commented and changed status New Closed <span data-processor="relativetime" data-value="2026-11-13T11:18:25+00:00" > 11/13/26, 11:18 </span>

    Closing this issue – see the last comment from Riccardo 3 years ago.