Bug #23744
closedA new TypoScript cObject: FLUIDTEMPLATE
0%
Description
This is a result of some enthusiastic guys (Steffen Ritter and me) from the code sprint. Something we wanted for a long time, and this is our first version: a new Typoscript Object Type called "FLUIDTEMPLATE". Guess what it does: Yes, it can be used as a replacement for TEMPLATE, with (almost) all the glitter that Fluid has to offer.
The fluid template syntax will look like this:
page = PAGE
page.10 = FLUIDTEMPLATE
page.10 {
- the FLUID template, has stdWrap functionality
file = fileadmin/mytemplates/mytemplate.html
- setting a specific partials path, usually it's layouts/ underneath the template file
partialRootPath = fileadmin/partials/
- setting a specific layout path, usually it's layouts/ underneath the template file
layoutRootPath = fileadmin/layouts/
- setting variables that should be available in
- the fluid template
variables {
mytitle = TEXT
mytitle.data = page:title
}
}
(issue imported from #M16008)
Files
Updated by Ingo Renner about 14 years ago
How about a shorter name, like just plain and simple FLUID?
Another idea I once had which is somehow related: I planed to redo TIMTAB with extbase and fluid, however , it should still work with tt_news. This results in needing a fluid + classic marker connector / adapter / thingy. The idea is to have a template file with both markers. TIMTAB would take care of pushing the template through fluid and providing its data. Fluid would return the result to TIMTAB, the regular, classic markers would still be in, not modified by fluid. tt_news could then go on and replace the remaining classic markers...
Maybe that could also be an idea for transparent processing of core templates... sticking with the known TEMPLATE cObject, but having it enhanced with the ability of rendering fluid markers...
Updated by Sebastian Kurfuerst about 14 years ago
Hey,
I'll have a look into this as well :-) I'm on holidays now, but you can expect my feedback on Thursday at latest.
Greets,
Sebastian