TYPO3 Core

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.

• https://github.com/benjaminkott/bootstrap_package/issues/1425
• https://www.typo3forum.net/discussion/85682/upgrade-von-11-auf-12-funktioniert-nicht-ganz