[TASK] Clean up usages of ContentObjectRenderer request attribute
ContentObjectRenderer is now added as request attribute in certain cases. But since the signature of obtaining an attribute from a request correctly states, that the attribute can be null, consuming code should account for that and defensively fall back to defaults, when the object can not be obtained. Releases: 12.4, main Resolves: #101201 Change-Id: I3b3145794cafd8f5a8c1081e97599f9862be8b99 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79572 Reviewed-by:J�rg B�sche <typo3@joergboesche.de> Reviewed-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
core-ci <typo3@b13.com>
Showing
- typo3/sysext/extbase/Classes/Configuration/FrontendConfigurationManager.php 3 additions, 3 deletions...se/Classes/Configuration/FrontendConfigurationManager.php
- typo3/sysext/extbase/Classes/Mvc/Web/Routing/UriBuilder.php 2 additions, 2 deletionstypo3/sysext/extbase/Classes/Mvc/Web/Routing/UriBuilder.php
- typo3/sysext/form/Classes/Controller/FormFrontendController.php 2 additions, 2 deletions...sysext/form/Classes/Controller/FormFrontendController.php
- typo3/sysext/form/Classes/Domain/Runtime/FormRuntime.php 7 additions, 10 deletionstypo3/sysext/form/Classes/Domain/Runtime/FormRuntime.php
Loading
Please register or sign in to comment