[TYPO3-dev] rendering in the not so easy way?

[Steffen Ritter]

Hello,
Afaik the should be a patch removing this behaviour and creating it the 
intuitive way.
RFC: Bug #6885: Nested USER_INT, COA_INT, etc. objects are not rendered 
is covering this topic. In 4.2 this got fixed.

Greetings Steffen

JoH asenau schrieb:
>>> Let me guess: Both, your and the included plugin, are using USER_INT
>>> or something similar to prevent caching?
>> correct.
>>
>>> Since you can not nest XXX_INT objects, this might be a good reason
>>> for the behaviour you described.
>> why this?
>> wouldn't it make sense that only non-cached-objects can include non-
>> cached objects?
> 
> well - due to the current behaviour of XXX_INT objects this is simply not
> possible.
> While rendering the page and putting the result into the cache, all XXX_INT
> objects are replaced with a simple marker.
> 
> While fetching the page from the cache this marker will be recognized and
> replaced with the appropriate TypoScript. (BTW: This is the reason why you
> have to use includeLibs with XXX_INT objects since the orirginal libs will
> be not available here.)
> 
> If your uncached plugin is trying to render another XXX_INT element now,
> this would result in a simple marker that won't be replaced anymore, since
> this would only be done while fetching the page from cache, which has just
> happened a few milliseconds before.
> 
>> I could change the outer extension to USER as it always will work the
>> same, but the inner one couldn't be cached since it has to compute
>> results based on the time (it is timed content, changing every minute)
>> How will the outer cached extension then include the uncached changing
>> content?
>> I thought this can not work, so i decided to have an uncached outer
>> extension.
> 
> Conclusion:
> You can use a USER_INT for the "outer" extension, if it will be rendering
> non XXX_INT objects only.
> You can render XXX_INT objects with it, if you set the "outer" extension to
> USER.
> Every XXX_INT object will remain uncached even if the "outer" extension is
> not, since the behaviour stays the same: A marker is rendered and will be
> replaced while fetching the page from cache.
> 
> HTH
> 
> Joey
>