Bug #68061
closed
Ensure PageRenderer singleton is set
100%
Description
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.
Updated by Gerrit Code Review over 9 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/41109
Updated by Helmut Hummel over 9 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 732910b3c9e3b860ad064eb559e943bd41d333cc.
Updated by Gerrit Code Review over 9 years ago
- Status changed from Resolved to Under Review
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/41112
Updated by Gerrit Code Review over 9 years ago
Patch set 2 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/41112
Updated by Helmut Hummel over 9 years ago
- Status changed from Under Review to Resolved
Applied in changeset e0b9d45bd975836909c0509f871e7fed31f634a9.
Updated by
Updated by Daniel Goerz over 5 years ago
- Related to Bug #89445: FooterAsset are not loaded added