Issue Bug Closed

#105325Nested StandaloneView (FluidTemplate) inherits Extbase request from TemplateView

Markus Klein 10/16/24, 14:55 updated 05/04/26, 13:24

Description

Setup

Extbase Extension with a Controller “Seminars” and an action “Show”.
The corresponding “Show.html” Fluid template contains:

<f:cObject typoscriptObjectPath="lib.someContent">

So it renders some regular content:

lib.someContent < styles.content.get
lib.someContent.select.pidInList = 123

The selected content contains an Extbase Plugin.

Expected behavior

Browser should display the content loaded via lib.someContent.
This works just fine up to v11.

Actual behavior

Exception that “Seminars/Show.html” can’t be found in paths. (where the paths are the regular Fluid Styled Content paths)

Analysis

The Fluid template setup above creates technically a nesting of TemplateView (Show-Action) and StandaloneView (FluidTemplate via f:cObject).

Unluckily, the StandaloneView gets passed the Extbase-Request from the Show-Action, which causes this request being passed down to the TYPO3\CMS\Fluid\Core\Rendering\RenderingContext::setRequest causing the Controller/Action of the FluidTemplate to be overwritten.

While it is desirable that StandaloneView itself can handle Extbase Requests for other use cases like E-Mail and stuff, this should not be the case when an isolated context is required, like in the f:cObject case.

Ideas for solution

Fix CObjectViewHelper to “revert” the request properly, e.g. by using the initial requst from $GLOBALS[TYPO3_REQUEST] instead of the more specific one in its own renderingContext.

Reviews 3

History 914

  1. Markus Klein commented <span data-processor="relativetime" data-value="2024-10-16T15:10:11+00:00" > 10/16/24, 15:10 </span>

    Probably better change in the viewhelper

    - $request = $renderingContext->getRequest();
    + $request = $renderingContext->getRequest()->withoutAttribute('extbase');
  2. Markus Klein commented <span data-processor="relativetime" data-value="2024-10-17T07:10:27+00:00" > 10/17/24, 07:10 </span>

    The fix above works for v12, I’ll try to do some testing in v13 too.

  3. Markus Klein commented <span data-processor="relativetime" data-value="2025-03-17T15:23:22+00:00" > 03/17/25, 15:23 </span>

    The content of this issue evolved over time, I’ll try to provide a new warp up.

  4. Markus Klein commented <span data-processor="relativetime" data-value="2025-03-17T19:52:55+00:00" > 03/17/25, 19:52 </span>

    This issue is only present in v12. To reproduce:

    1. Install ext:news
    2. Install ext:plain_faq (or any other extbase-based extension)
    3. Install fluid_styled_content
    4. Add necessary base TS templates (FSC, news, plain_faq)
    5. Configure a default extension name for FSC in TypoScript: lib.contentElement.extbase.controllerExtensionName = Sitesetup
    6. Create a sysfolder “data”
    7. Create 1 FAQ record
    8. Create 1 News record: Add a content element there with the plainfaq list plugin (select storage folder “data”)
    9. Add “news detail” plugin to a page and select the created news article there
    10. View the page

    The error will be:

    > #1257246929 TYPO3Fluid\Fluid\View\Exception\InvalidTemplateResourceException
    > Tried resolving a template file for controller action “News->detail” in format “.html”, but none of the paths contained the expected template file (News/Detail.html). The following paths were checked: /var/www/html/vendor/typo3/cms-fluid-styled-content/Resources/Private/Templates/, /var/www/html/vendor/reelworx/sitesetup/Resources/Private/Templates/Content/

    Note: This error does not occur if lib.contentElement.extbase.controllerExtensionName is NOT set!

    (The code is gone in v13 with https://review.typo3.org/c/Packages/TYPO3.CMS/+/85348/3/typo3/sysext/frontend/Classes/ContentObject/FluidTemplateContentObject.php#b219. Code-wise v13 still passes along the “extbase-enriched” request through the cObject-ViewHelper, but it won’t matter here.)

  5. Benni Mack commented and changed status Under Review Closed <span data-processor="relativetime" data-value="2026-05-04T13:24:31+00:00" > 05/04/26, 13:24 </span>

    support for 12.4 version in the free version has been dropped.