Bug #102332
openconfig/system/settings.php is not writable error in Install Tool after Upgrade to TYPO3 v 12.4.7
0%
Description
Might be related to https://forge.typo3.org/issues/100353, which is resolved.
After updating from 12.4.6 to 12.4.7 uppon the first call to the install tool I got the error "config/system/settings.php is not writable" again when trying to call the Install Tool on the life site to make a database compare.
After making the file "config/system/settings.php" writable the error went away. Even when I turned the write protection for "config/system/settings.php" back on the error stays away so I suspect it is caused by some Magic Upgrade Wizard once more
Updated by Lina Wolf about 1 year ago
It seems like the cause was solr trying to write something to the settings.php a fact that I had missed because on the development system I deleted caches and compared database with the cli. So on the dev system The settings.php did not get changed.
Now on the life system with logs and everything turned of for security reasons it just blew up the install tool with a 503 which is not a nice reaction for such a small cause.
I would suggest in such a case to just give a warning like "Your config/system/settings.php needs to be updated by Extension XY"...
Updated by Soren Malling about 1 year ago
I've found it happening because of missing EXTCONF values of installed extensions, so TYPO3 silently writes them when entering the maintenance module.
In my case, the scheduler was installed, we ran extension:setup, and we deployed it. In the production I entered the maintenance module and found the error about the file not being writable.
It's done through
$extensionConfiguration = new ExtensionConfiguration();
$extensionConfiguration->synchronizeExtConfTemplateWithLocalConfigurationOfAllExtensions();