Issue Bug New

#91984Extension configuration prefills from additional.php and saves values to settings.php, behaving different than the normal configuration UI

S P 08/12/20, 07:19 updated 11/11/26, 17:03

Description

Our extensions use ext_conf_template.txt to define extension settings.

Some settings for the development systems are overriden in a local devevelopment additional.php.

When changing the extension configuration in the backend UI the fields get prefilled with the values from additional.php and are moved to settings.php when hiting “save”.

This is a major issue if the live system should use the values from settings.php which then suddenly are overriden with local dev values.

The extension configuration UI should use the same mechanims as the regular configuration UI and show a message like this:

> Note that $GLOBALS[‘TYPO3_CONF_VARS’] currently contains a different value. This could mean that the value is overwritten in additional.php.

It should not blindly pass values from additional.php to settings.php.

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
[BUGFIX] Extension configuration prefills from additional.php and saves values to settings.php, behaving different than the normal configuration UI Resolves: #91984 Releases: main

History 11

  1. S P commented and changed TYPO3 Version 12 13 <span data-processor="relativetime" data-value="2024-12-19T09:19:10+00:00" > 12/19/24, 09:19 </span>

    Still present in v13.

  2. Julian Hofmann commented <span data-processor="relativetime" data-value="2025-01-24T10:46:07+00:00" > 01/24/25, 10:46 </span>

    The extension configuration from ext_conf_template.txt seems to be always used as soon as the settings.php is rewritten by TYPO3.

    We have observed this in two ways
    1. installation of another extension that writes its default Extconf settings to settings.php
    2. changing the installtool password via the BE module

    Under no circumstances should values in the settings.php be manipulated/changed by TYPO3 (unless they are migrations/cleanups)

  3. S P changed subject Extension configuration prefills from AdditionalConfiguration and saves values to LocalConfiguration, behaving different than the normal configuration UI Extension configuration prefills from additional.php and saves values to settings.php, behaving different than the normal configuration UI <span data-processor="relativetime" data-value="2025-01-24T10:53:40+00:00" > 01/24/25, 10:53 </span>

  4. S P commented and changed TYPO3 Version 13 14 <span data-processor="relativetime" data-value="2026-06-11T07:00:51+00:00" > 06/11/26, 07:00 </span>

    Still present in v14.

  5. Franz Kugelmann commented <span data-processor="relativetime" data-value="2026-11-11T17:03:33+00:00" > 11/11/26, 17:03 </span>

    In v14 the values from additional.php are already written to settings.php, if you just open the settings module (/typo3/module/system/settings).
    See \TYPO3\CMS\Install\Controller\LayoutController::executeSilentExtensionConfigurationSynchronizationAction