On fresh instances, the install tool may fail if path EXT/extConf
which is written as b/w compat layer does not exist, yet.
Patch catches the (generic) exception from ArrayUtility->getValueByPath()
and initializes the value to an empty array to continue in this case.
Resolves: #83298
Related: #82368
Releases: master
Change-Id: Iffac458a9e42183139ab4425082abb6f78944ffd
Reviewed-on: https://review.typo3.org/55044
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Susanne Moog <susanne.moog@typo3.org>
Tested-by: Susanne Moog <susanne.moog@typo3.org>
public function executeSilentLegacyExtConfExtensionConfigurationUpdateAction(): ResponseInterface
{
$configurationManager = new ConfigurationManager();
- $oldExtConfSettings = $configurationManager->getConfigurationValueByPath('EXT/extConf');
+ try {
+ $oldExtConfSettings = $configurationManager->getConfigurationValueByPath('EXT/extConf');
+ } catch (\RuntimeException $e) {
+ // The old 'extConf' array may not exist anymore, set to empty array if so.
+ $oldExtConfSettings = [];
+ }
$newExtensionSettings = $configurationManager->getConfigurationValueByPath('EXTENSIONS');
foreach ($oldExtConfSettings as $extensionName => $extensionSettings) {
if (!array_key_exists($extensionName, $newExtensionSettings)) {