Issue Task Closed

#92803Intransparent configuration path (e.g. for LocalConfiguration.php)

Daniel Haring 11/09/20, 14:30 updated 11/03/22, 11:40

Description

According to the documentation, configuration files (e.g. LocalConfiguration.php) will be put in {$projectRootPath}/config if set up via Composer.

See documentation

However, this does not seem to be the case.

Whenever I create a fresh TYPO3 CMS instance using Composer, the configuration files are stored in {$publicPath}/typo3conf.

I have already been able to trace this back to TYPO3\CMS\Core\Configuration\ConfigurationManager. While TYPO3\CMS\Core\Core\Environment::getConfigPath() returns the correct path, the ConfigurationManager seems to ignore this setting and uses Environment::getLegacyConfigPath() instead.

Either the ConfigurationManager should respect the path correctly, or the documentation (including PHPDoc from Environment::getConfigPath) should be adapted accordingly.

Reviews 0

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