Bug #100660
openWrong resources links when using env variable path_root
0%
Description
When TYPO3 is installed with typo3-composer-installers v3.1 and the installation using enviroment variable: TYPO3_PATH_ROOT, the TYPO3 set all resources with _assets/.
If you leave out the variable everything works fine.
Updated by Kay Strobach about 1 year ago
with the old composer installer and previous TYPO3 versions it was possible to install typo3 in a way, that resources are loaded from
public/typo3conf/ext/
With the newer core and the same old installer (v3) this works fine as long as you use composer in the root folder and do not use the constant TYPO3_PATH_ROOT, otherwise the resources are loaded from
_assetswhich is fine for newer installations, but breaks with the old installer.
The change happend somewhere in the v11 releases, will try to pin that down further.
Worked for v9, v10, upgrade to v11 broken
Btw. for v12 we switched to the
_assetsfolder, but as our instance works a template for many installs, it would be nice to find a solution.
Updated by Garvin Hicking 11 months ago
- Related to Bug #101911: TYPO3 composer mode does not properly respect installations in a subdirectory added
Updated by Helmut Hummel 11 months ago
- Status changed from New to Needs Feedback
Stefan Bublies wrote:
When TYPO3 is installed with typo3-composer-installers v3.1
I assume TYPO3 11, like set to the bug report. correct?
and the installation using enviroment variable: TYPO3_PATH_ROOT,
Can you explain what you want to achieve with setting this environment variable in Composer mode
and especially to what value you are setting this compared to the value that TYPO3 calculates for this path?
Updated by Stefan Bublies 11 months ago
Helmut Hummel wrote in #note-3:
I assume TYPO3 11, like set to the bug report. correct?
Yes, correct.
and the installation using enviroment variable: TYPO3_PATH_ROOT,
Can you explain what you want to achieve with setting this environment variable in Composer mode
and especially to what value you are setting this compared to the value that TYPO3 calculates for this path?
In this setup, the vendor (and a few other) folders are not in the document root. The variable is set to the document root. This worked fine under v9 and v10.
Updated by Riccardo De Contardi 7 months ago
- Status changed from Needs Feedback to New
Updated by Helmut Hummel about 2 months ago
- Status changed from New to Needs Feedback
Stefan Bublies wrote in #note-4:
In this setup, the vendor (and a few other) folders are not in the document root. The variable is set to the document root. This worked fine under v9 and v10.
Can you please provide a full and reproducible example of what exactly you are doing preferably with an explanation of what you are trying to achieve.
Updated by Helmut Hummel about 2 months ago
In general changing these environment variables is discouraged, as it bypasses all validation that happens, when configuring the paths via composer.json settings. Violating validations, will lead to unexpected behaviour.