Deprecation: #95139 - Extbase ControllerContext

See Issue #95139


The Extbase related class TYPO3\CMS\Extbase\Mvc\Controller\ControllerContext has been used in the past to transfer data between extbase controllers and fluid views. It has been superseded by class TYPO3\CMS\Fluid\Core\Rendering\RenderingContext with various preparation patches. To further decouple Fluid from Extbase, class ControllerContext has been marked as deprecated.


Accessing ControllerContext and consuming information carried in it has been marked deprecated. The class will be removed in v12. The object is bound to various Fluid view related classes and all occurrences have been marked with an @deprecated annotation.

To retain backwards compatibility, accessing ControllerContext does not actively trigger a deprecation level error in most cases, though.

Affected Installations

Instances with extensions that access ControllerContext are affected. This typically affects extensions which provide own view helpers. The extension scanner should find possible matches.


Two getters of the class have already been deprecated with previous patches, namely ->getUriBuilder() as documented with ->getFlashMessageQueue(). Classes should inject instances of these objects instead, or should makeInstance() them.

Method getRequest() is available in controllers directly, and view helpers receive the current request by calling RenderingContext->getRequest().

Method getArguments() returns the Extbase Arguments created by the ActionController. The getter has become mostly useless within fluid context since argument validation of forms is abstracted differently since various core versions. If that object construct is still needed, it should be transferred differently to consuming classes, for instance by assigning it as variable to the view and accessing it in a view helper using the variable container. In many cases it should be sufficient to directly work with the request object instead.