TYPO3 Core

Summary:

Whenever TypoScriptFrontendController is instanciated (e.g. by an extension) it also instanciates PageRenderer (which is a Singleton!) and sets the backPath to ``typo3/`` which is a change in behaviour which also affects URL creation of Backend Assets.

Tested with:

• TYPO3 CMS 7.5-dev 8f540ffbf880691a17d6d4c3ca4f184abba84d22
• PHP 5.6.9-0+deb8u1, Debian 8, running with Docker in native mode (without virtualization, Host Kernel 3.19 provided by ubuntu 14.04.3), Chromium Version 44.0.2403.89 Ubuntu 14.04 (64-bit)

Reproduce with:

• instanciate TypoScriptFrontendController in the backend
• => Some Javascript/CSS assets will have URL prefix typo3/typo3 instead of typo3/ and will be 404'ed.

Impact:

Any extension which instanciates TSFE is affected.

This is a regression in TYPO3 CMS 7.4.0 introduced with commit 43ab6508e7eb01a5b9cca294257349d3e4a53995
https://review.typo3.org/#/c/41239/
https://review.typo3.org/#/c/41239/5/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php

Deprecation message does not include the breaking change we are faced with here.
https://docs.typo3.org/typo3cms/extensions/core/latest/Changelog/7.4/Deprecation-68074-DeprecateGetPageRenderer.html

Details, Stacktrace and Workaround available at https://github.com/mblaschke/TYPO3-metaseo/issues/150