[BUGFIX] Reinitialize PageRenderer after deserialization
Do not swap the global singleton instance, as that would only update new classes that are retrived though GeneralUtlity::makeInstance). Existing ones (cached in already initialized classes, or initialized via the symfony DI container would not be updated). Releases: master, 10.4 Resolves: #91316 Related: #87402 Related: #88179 Change-Id: Ibcd4ecd3418dd047861b83685a6664e391a8f66b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64419 Tested-by:Helmut Hummel <typo3@helhum.io> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Helmut Hummel <typo3@helhum.io> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
Showing
- typo3/sysext/core/Classes/MetaTag/MetaTagManagerRegistry.php 24 additions, 0 deletionstypo3/sysext/core/Classes/MetaTag/MetaTagManagerRegistry.php
- typo3/sysext/core/Classes/Page/AssetCollector.php 24 additions, 0 deletionstypo3/sysext/core/Classes/Page/AssetCollector.php
- typo3/sysext/core/Classes/Page/PageRenderer.php 38 additions, 5 deletionstypo3/sysext/core/Classes/Page/PageRenderer.php
- typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php 2 additions, 3 deletions...ntend/Classes/Controller/TypoScriptFrontendController.php
- typo3/sysext/frontend/Classes/Http/RequestHandler.php 2 additions, 0 deletionstypo3/sysext/frontend/Classes/Http/RequestHandler.php
Please register or sign in to comment