Problem/Description¶

There are situations where an AdditionalConfiguration.php needs to be migrated too, even if a settings.php is in place:

One problematic scenario is DDEV: It's actually not really straight forward for newcomers or contributors to work on the core due to the AdditionalConfiguration.php generation. Since there are big changes in core's file structure, DDEV will wait for any modifications in the TYPO3 integration part until TYPO3 v12 lts is released. This was recently (jan 2023) discussed between @Benni Mack and @Simon Gilli.

Instead of adding infos in the documentation of the TYPO3 contribution guide, I walked through the code and believe that this fix should be right in the core.

ToDo(s)¶

• Add a check if AdditionalConfiguration.php needs migrated even if settings.php is already in place
• Add a "silent" migration like it is already in place for the "LocalConfiguration.php"

Acceptance Criteria¶

• main-installation with DDEV migrates typo3conf/AdditionalConfiguration.php even if the recently introduced settings.php is already in place.

Scenarios for Testing¶

$properlyConfigured = TRUE
```
new:
    settings.php
legacy:
    -
```

$properlyConfigured = TRUE
```
new:
    settings.php
    additional.php
legacy:
    -
```

$properlyConfigured = FALSE
```
    new:
        settings.php
    legacy:
        AdditionalConfiguration.php
```

$properlyConfigured = TRUE
```
    new:
        settings.php
        additional.php
    legacy:
        AdditionalConfiguration.php
```

$properlyConfigured = FALSE
```
    new:

    legacy:
        LocalConfiguration.php
        AdditionalConfiguration.php
```

$properlyConfigured = FALSE
```
    new:

    legacy:
        LocalConfiguration.php
```