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

[JoH asenau]

> 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.

Don't know what the patch does exactly but IMHO it would have been enough to
patch the TS parser itself so that it would switch XXX_INT objects to XXX
objects when rendered within another XXX_INT object before rendering the
whole stuff.

Since the surrounding XXX_INT object already makes sure that none of the
containing elements will be taken from cache, nesting of XXX_INT objects
will just slow down the rendering process without any additional advantage.

The bug report you mentioned contains a notice about problems commerce and
newloginbox using the following TS:

plugin.tx_commerce_pi3 = USER_INT
plugin.tx_commerce_pi3 {
        loginBoxUID = USER_INT
        loginBoxUID.userFunc = plugin.tx_newloginbox_pi1->main
}

switching it internally to

plugin.tx_commerce_pi3 = USER_INT
plugin.tx_commerce_pi3 {
        loginBoxUID = USER
        loginBoxUID.userFunc = plugin.tx_newloginbox_pi1->main
}

would have been enough to solve the problem and still have no cached output
for the newloginbox.

I will ad this as a notice to the bug report.

HTH

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your gob sometimes!)
Dieter Nuhr, German comedian
openBC/Xing: http://www.cybercraft.de
T3 cookbook: http://www.typo3experts.com
Jobs: http://www.professionals-only.com