Bug #82745

fluid resolving an unexpected layout file

Added by Peter Niederlag 6 days ago. Updated 1 day ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
Fluid
Target version:
-
Start date:
2017-10-12
Due date:
% Done:

0%

TYPO3 Version:
8
PHP Version:
7.1
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

We run into an Exception during rendering an Extension:

Uncaught TYPO3 Exception
Section "main" does not exist.

Actually something is going wrong during resolving the proper layout file.

Page Template

page.10 = FLUIDTEMPLATE
does use a layout "Default", with a section "content" (but no section "main")

layoutRootPaths is set properly in TS.

This is working just fine on almost all pages.

Plugin Template

plugin.tx_xxx does use a layout "Default" as well, however here we use a section "main" (but no section "content").
layoutRootPaths,and alike are set properly in TS.

However during rendering this extension for some weird(and yet unknown) reason the layout file from the page is used (which obviously is missing the section "main".

During debugging I found AbstractTemplateView of typo3fluid ll 190 through 200 responsible. $paths->getLayoutSource($layoutName) does return the proper source at first but however at some later point a wrong file will be served from cache.

The most weird thing, we use Layout Default for other extensions as well where we don't have this problem.

Templates and Layouts are all stored in a site-package (EXT:xxx-site)


Related issues

Related to Core - Bug #76675: Layout Filename must be unique or frontend crashes Closed 2016-06-17

History

#1 Updated by Peter Niederlag 6 days ago

  • Related to Bug #76675: Layout Filename must be unique or frontend crashes added

#2 Updated by Susanne Moog 1 day ago

  • Category set to Fluid

Also available in: Atom PDF