Project

General

Profile

Actions

Task #92803

closed

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

Added by Daniel Haring about 4 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
System/Bootstrap/Configuration
Target version:
-
Start date:
2020-11-09
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Sprint Focus:

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.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #98319: Move configuration files outside of document root when running in composer modeClosedBenni Mack2022-09-09

Actions
Actions #1

Updated by Benni Mack about 2 years ago

  • Status changed from New to Closed

Hey Daniel,

I totally get this and we've solved this in v12 finally:

https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Breaking-98319-NewFileLocationForLocalConfigurationphpAndAdditionalConfigurationphp.html

I will now close the issue now, hope that's OK with you.

Actions #2

Updated by Benni Mack about 2 years ago

  • Related to Task #98319: Move configuration files outside of document root when running in composer mode added
Actions

Also available in: Atom PDF