[TYPO3] any idea why COA_INT doesn't render USER_INT properly?

[Amiran Chyb]

On Thu, 23 Nov 2006 03:45:24 +0100, JoH asenau <info at cybercraft.de> wrote:

>> I've noticed that USER_INT content element (eg.
>> plugin.tx_newloginbox_t1) isn't rendered properly (in this case isn't
>> rendered at all) when put into COA_INT array. Surprisingly changing
>> it to normal cacheable COA array solves the problem.
>>
>> It doesn't look like designed behaviour, since it should be perfectly
>> normal to nest two non-cacheable objects, shouldn't it?
>
> No, it shouldn't, since the non cached COA_INT will be enough.
> Simply nest COA_INT and USER and everything will be working as expected.
>
> Since the COA_INT will be triggered each time the page is loaded by the
> client, the USER element will always be non cached even without being an
> _INT element itself.
>
> The reason why both of them can't work is, that _INT elements are  
> rendered
> as a marker that is put into the cached page. While rendering the page  
> from
> cache, the marker gets replaced with the desired content. In this case  
> the
> "content" would again be a marker to be put into the cache, but caching
> doesn't happen for the COA_INT element, so the marker for the USER_INT  
> would
> never be replaced.
>
> HTH
>
> Joey


Hey Joey, thanks for the great answer and the background info especially -  
it does make sense indeed. I'll just change plugins' TS to USER, than.


greets
Amiran