Commit 732910b3 authored by Helmut Hummel's avatar Helmut Hummel Committed by Nicole Cordes
Browse files

[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-by: Wouter Wolters's avatarWouter Wolters <>
Tested-by: Wouter Wolters's avatarWouter Wolters <>
Reviewed-by: Nicole Cordes's avatarNicole Cordes <>
Tested-by: Nicole Cordes's avatarNicole Cordes <>
parent 43466399
......@@ -987,15 +987,6 @@ class TypoScriptFrontendController {
return $this->pageRenderer;
* This is needed for USER_INT processing
* @param PageRenderer $pageRenderer
protected function setPageRenderer(PageRenderer $pageRenderer) {
$this->pageRenderer = $pageRenderer;
* Initializing, resolving page id
......@@ -3394,7 +3385,8 @@ class TypoScriptFrontendController {
if (!empty($this->config['INTincScript_ext']['pageRenderer'])) {
/** @var PageRenderer $pageRenderer */
$pageRenderer = unserialize($this->config['INTincScript_ext']['pageRenderer']);
$this->pageRenderer = $pageRenderer;
GeneralUtility::setSingletonInstance(PageRenderer::class, $pageRenderer);
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment