[TYPO3-mvc] Extbase / ViewHelper disable caching?

[Claus Due]

Hi Gabriel,

You're thinking about this all wrong.

A cached output does not render the ViewHelpers every time, it stores HTML already built. This is why you must use USER_INT to make the template render every time. You can make chunks of cached output inside an uncached extension but not the other way around. If the parent is cached then the child is not asked to render.

The solution is to use USER_INT and manually cache the parts you want cached. The other way is backwards ;)

Cheers,
Claus

On Sep 13, 2012, at 6:19 PM, Gabriel Kaufmann | Typoworx <info at typoworx.de> wrote:

> Hello Philipp,
> 
>> Include the extbase plugin as USER_INT.
> Umm... well that would be a solution. But it's not very handy to force the whole plugin to be uncached then? For the "usual" piBase programming every programmer would say that's an absolute "no go". I don't think it's a good way to do it now.
> 
> I hoped for one of these cases to "cleanly" solve this issue:
> 
> 1. Have a property or method inside my viewHelper-Class to avoid caching
> 2. Have a viewHelper-Block that will enforce non-cached processing for
>   every fluid-tag/viewHelpers inside the block.
> 
>   f.e: <f:nonCached> .... some viewhelpers .... </f:nonCached>
> 
> 
> Best regards
> Gabriel