Project

General

Profile

Actions

Feature #39767

closed

FLUIDTEMPLATE should accept template from content objects as TEMPLATE does

Added by Martin Bless over 11 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
Start date:
2012-08-13
Due date:
% Done:

100%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

It seems that FLUIDTEMPLATE misses a feature that would really be useful. It is something you would expect to have and it's good for TYPO3.

Currently you HAVE TO provide a physical file as template for FLUIDTEMPLATE. This is in contrast to the normal TEMPLATE object which takes the template from other content objects as well.

Please see this thread as well:
http://lists.typo3.org/pipermail/typo3-dev/2012-August/045745.html

I would like to write for example:

  ### does not work currently!!!
  page {
    10 = FLUIDTEMPLATE
    10 {
      file.cObject = TEMPLATE
      file.cObject {
        template =< plugin.tx_automaketemplate_pi1
        workOnSubpart = DOCUMENT_BODY
      }
    // ...
  }

Quoting Xavier's answer to my question:

Hi Martin,

But this doesn't work because in class.tslib_content_fluidtemplate.php around line 69 there is:

/** * 1. initializing Fluid StandaloneView and setting configuration parameters **/ $view = t3lib_div::makeInstance('Tx_Fluid_View_StandaloneView'); // fetch the Fluid template $file = isset($conf['file.']) ? $this->cObj->stdWrap($conf['file'], $conf['file.']) : $conf['file']; $templatePathAndFilename = $GLOBALS['TSFE']->tmpl->getFileName($file); $view->setTemplatePathAndFilename($templatePathAndFilename);

$templatePathAndFilename will be set to FALSE when I provide something else than a legal path to an existing file. And then there is no template which gives an error.

You're right. Seems indeed like a missing feature that would really be useful for FLUIDTEMPLATE (a bit less for standard Fluid I guess). I would contact the Fluid team ASAP and see with them for a tangible solution to be integrated into 6.0 (no way to get it into 4.7 or 4.6 as it'll be a new feature). But it has to probably be kept in sync with the version in FLOW3 and the feature freeze of 6.0 is coming soon.

It would be really great if we could do something about this missing feature. Otherwise many usecases of TEMPLATE can't be rewritten using FLUIDTEMPLATE. I'm missing that feature very much as I usually use directly the HTML "clickdummy" a web designer has provided as template source. This avoids lots of work and discussion: I can always click the "clickdummy" and verify that the HTML of the template works.

Actions

Also available in: Atom PDF