Bug #86763
closed
Backend Layout Slide not working in FLUIDTEMPLATE Variables after Upgrade to 9.5.0
0%
Description
I am reading the current backend_layout with a typoscript TEXT object, and pass it to a variable in my FLUIDTEMPLATE like this:
variables{
beLayout = TEXT
beLayout.data = levelfield:-1, backend_layout_next_level, slide
beLayout.override.field = backend_layout
}
In my Fluid-Template I have a s:switch ViewHelper to do some magic. This worked for several years and in the last version of this project with 8.7.19 perfectly.
Now, in TYPO3 9.5.0 the template of the subpage gets selected on the root page. In other words, the sliding mechanism doesn't seem to work anymore.
Any ideas about this?
Updated by Michael Stucki about 6 years ago
- Project changed from 9 to TYPO3 Core
- Category deleted (
Development) - TYPO3 Version set to 9
Wrong project.
Updated by Jasmina Ließmann about 6 years ago
I can't confirm this issue on the current master (9.5.1-dev) neither with backend layouts created via records in the root page nor with backend layouts created via Page TSconfig.
In both ways the variable in the fluidtemplate gets the value of the backend layout correctly (for 'backend_layout' and 'backend_layout_next_level').
Updated by Alexander Jaschke about 6 years ago
I had the same problem with 9.5.0.
I've changed the Typoscript:
belayout = TEXT
belayout.data = levelfield:-2, backend_layout_next_level, slide
belayout.override.data = page:backend_layout
Updated by Georg Ringer about 6 years ago
- Related to Bug #86733: Data in page is invalid if plugin exits added
Updated by Georg Ringer about 6 years ago
- Related to Bug #86837: TypoScript Condition: tree.* broken on cached pages added
Updated by Georg Ringer about 6 years ago
- Related to deleted (Bug #86837: TypoScript Condition: tree.* broken on cached pages)
Updated by Georg Ringer about 6 years ago
- Related to Bug #86703: Page's data partly not available via getText if page has form CE added
Updated by Riccardo De Contardi almost 6 years ago
- Status changed from New to Needs Feedback
Is this one still reproducible? Could you test it on the latest 9.5.x version? Thank you!
Updated by Riccardo De Contardi over 5 years ago
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Simon Köhler)
No feedback since the last 90 days => closing this issue.
If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem, please reopen it or ping me.
Thank you and best regards
Updated by Ernesto Baschny almost 4 years ago
It's closed, but since I reached this issue here too, one note:
Wrong:
beLayout = TEXT beLayout.data = levelfield:-1, backend_layout_next_level, slide beLayout.override.field = backend_layout
Right:
beLayout = TEXT beLayout.data = levelfield:-2, backend_layout_next_level, slide beLayout.override.field = backend_layout
The "-1" will start on the current page first, and thus if the current page also has a "layout_next_level" configured, it will be used instead of "sliding up" the tree. With "-2" the sliding starts at the first parent page, which is what we really want.
There are several snippets on the internet with the wrong code - which works fine as long as your subpage doesn't have a "layout_next_level" set too!