#101911TYPO3 composer mode does not properly respect installations in a subdirectory
Description
This is a grouping ticket.
Several bugs can occur because TYPO3v12 introduced asset-collecting and at some places does not properly reference the directory, where those assets are retrieved, when in composer-mode.
This can lead to doubling parts of the actual path.
Example:
Composer project path: /var/www/html/typo3_v12/ TYPO3 public root: /var/www/html/typo3_v12/public/ DocumentRoot: /var/www/html TYPO3 Backend URI: https://example.com/typo3_v12/public/typo3/index.php
When assets are retrieved, the workflows may use combinations Environment::getPublicPath and Environment::getAbsoluteWebPath to i.e. first resolve a EXT:bootstrap_packages/Resources/Public/Css/bootstrap5-rte.min.css file, and then later AGAIN prepend paths.
This would resolve the above to:
/var/www/html/typo3_v12/public/ -> /var/www/html/typo3_v12/public/typo3_v12/public/_assets/9b80d86a98af3ecc38aabe297d2c3695/Css/bootstrap5-rte.min.css
I am trying to set-up an installation to easily reproduce this.
External references:Reviews 1
Related issues 6
- Task #96887Allow only Resources/Public in PathUtility->getPublicResourceWebPath
- Bug #100660Wrong resources links when using env variable path_root
- Bug #100661Wrong resource links to symlinked _assets unsing base with appending path segment
- Bug #101918CKEditor5 migration for contentsCss with cache busting query string does not load the actual CSS file
- Bug #103157Image referenced by `EXT:` does not work in TYPO3 subfolder installation
- Bug #104460Asset ViewHelper does not take config.forceAbsoluteUrls into account