[BUGFIX] Ensure PageRenderer singleton is set 12/41112/3
authorHelmut Hummel <helmut.hummel@typo3.org>
Sun, 12 Jul 2015 13:10:37 +0000 (15:10 +0200)
committerNicole Cordes <typo3@cordes.co>
Mon, 13 Jul 2015 08:29:01 +0000 (10:29 +0200)
commite0b9d45bd975836909c0509f871e7fed31f634a9
treeed0fa59f2b5d3660e3a1d8ca5421b0f1823c9ab8
parentdbdff8e4861e30884f614681a92774b683c91fbc
[BUGFIX] Ensure PageRenderer singleton is set

Before rendering _INT content objects, the page renderer is unserialized
and stored in a TypoScriptFrontendController property. However this new
object is not updated in the singleton store in GeneralUtility.

This leads to the situation that plugin code that (legally) just instantiate
the page renderer using GeneralUtility::makeInstance() receive the wrong object.

Make sure the singleton store is updated once the page renderer is unserialized
for _INT processing.

Releases: master, 6.2
Resolves: #68061
Change-Id: I162b8a4dc102ffd8cc0fcc4d21ccc271c861b187
Reviewed-on: http://review.typo3.org/41112
Reviewed-by: Nicole Cordes <typo3@cordes.co>
Tested-by: Nicole Cordes <typo3@cordes.co>
Reviewed-by: Helmut Hummel <helmut.hummel@typo3.org>
Tested-by: Helmut Hummel <helmut.hummel@typo3.org>
typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php