[TYPO3-english] Image rendering in Extbase/Fluid

Martin Wagner martin.wagner at iue.tuwien.ac.at
Tue Apr 23 17:15:17 CEST 2013

Hi Tobi,

sorry for the delayed answer.  Yes, exactly the described problem.  Do you have any hint for me how to circumvent the issue?  I don't feel very comfortable with not updating to the latest version because of such an issue...  Perhaps any core developer involved in the security fix on 6.0.3 is reading this and knows about the future plans on how to fix that / best practice for avoiding that?

Thanks, Martin

Hi Martin,

the problem is described here: http://forge.typo3.org/issues/46067 - but 
it's missing a working patch.


Am 13.04.13 17:08, schrieb Martin Wagner:
> Hi list,
> I recently struggled with a self-built extension when updating from TYPO3 6.0.2 to 6.0.4.  In the extension, I fetch the data using
>      $this->contentObj = $this->configurationManager->getContentObject();
>      $this->view->assign('data', $this->contentObj->data);
> In the Fluid template, I put the image source using {data.image}.  So far, so good - in 6.0.2, I get back the full image path and everything works fine.  Since 6.0.3, I just get back a '1' instead of the path.
> After some research, I found this behavior filed as a bug at forge.typo3.org/issues/46090.  Since the last activity on that is already a month back, I wonder if anybody out there has found some workaround / other technique to get back the image?
> Thanks folks,
>     Martin

More information about the TYPO3-english mailing list