[TYPO3-mvc] Extension spread over several pages - best practice?

Franz Koch typo3.RemoveForMessage at elements-net.de
Wed May 26 12:56:02 CEST 2010


Hey,

>>> However, I noticed that now the information of not-to-be-cached
>>> controller/action combinations from ext_localconf.php is lost as well.
>>> That way, my checkout controller was cached :-/
>> That should definitely not happen. Could you debug this even further?
>> For me, it all works...
>
> Could this be caused by the fact that GET and POST variables for a plugin cannot be mixed for Typoscript conditions? Example:
>
> GET:
> tx_myext_pi1[controller]=Foo
> tx_myext_pi1[action]=bar
>
> POST:
> tx_myext_pi1[baz]=1
>
> Now the TS conditions on controller and action fail because t3lib_div::_GP takes the tx_myext_pi1 array from POST and ignores the one from GET. I worked around this by adding hidden fields for controller and action to my form so controller and action are available in the TS conditions. But this is probably not a final solution.

Yes, that's also my guess. I encountered this issue some time ago and 
already started a topic about it - but a better solution for the dynamic 
USER_INT switching wasn't found yet. I'd say to use the new 4.3 features 
that allow switching a USER object to USER_INT - but for that the 
dispatcher might have to be changed in order to switch as early as 
possible in order to save cpu cycles.

-- 
kind regards,
Franz Koch


More information about the TYPO3-project-typo3v4mvc mailing list