#85484Feature-79409 renderAssetsForRequest doesn't honor {parsing off} processor
Description
Fluid in TYPO3 has a feature to add assets to footer/header of the page when used inside a Controller.
https://docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/Feature-79409-AutorenderAssetSectionsInFluidTemplateWithController.html
However when the fluid template has a processing instruction {parsing off} this will make the content of the template appear in header and footer section of the page, which is an unexpected behaviour for the developer.
As a workaround you can override function renderAssetsForRequest() in your controller.
See https://github.com/TYPO3/Fluid/issues/392 for the original bug-report and an example extension to demonstrate the problem.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 1
History 4
-
Mathias Brodala commented and changed attached fluid_parsing_off.zip <span data-processor="relativetime" data-value="2018-07-05T10:20:28+00:00" > 07/05/18, 10:20 </span>
-
Riccardo De Contardi commented <span data-processor="relativetime" data-value="2020-01-31T15:17:26+00:00" > 01/31/20, 15:17 </span>
Maybe I am totally wrong, but I wonder if this issue is valid: I report here the comment by Claus Due on https://github.com/TYPO3/Fluid/issues/392
> Just a side note:
{parsing off}used in a template is the same as doing$content = str_replace('{parsing off}', '', file_get_contents($myTemplateFile));because no calls to f:render or designations of f:layout will be active. So it is definitely reserved for Partials or special cases where one might render a template with Fluid but sometimes feed it non-Fluid source.> But the conclusion is that using this modifier disables the parsing which means the template is no longer a Fluid template, technically. Which in turn means that implementations which require a Fluid template (such as the automatic rendering of header/footer asset sections) may not work if you intentionally disable Fluid.
-
Susanne Moog changed tracker
BugFeature category Sprint Focus Needs Decision <span data-processor="relativetime" data-value="2020-03-26T11:15:18+00:00" > 03/26/20, 11:15 </span> -
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-02-26T20:34:05+00:00" > 02/26/26, 20:34 </span>hey peter!
with #107057 in 14.0 this has been deprecated, so nothing will happen anymore and I will close this issue
Here’s the test extension copied from Github.