[TYPO3-mvc] Concept of dynamic USER_INT switch maybe has to be refactored?

Jochen Rau jochen.rau at typoplanet.de
Tue Mar 2 11:42:40 CET 2010


Hi Franz.

On 28.02.10 17:54, Franz Koch wrote:
> I think the concept for the dynamic USER_INT switching of
> controller/action pairs has to be refactored, because it's not working
> like expected in many cases.

I agree with you.

[...]

> So instead of using TS conditions checking for GETvars to determine
> whether a plugin has to be of type USER or USER_INT, I'd suggest to use
> the new functionality in TYPO3 4.3 and convert those plugins really
> dynamically to USER_INT objects by triggering
> $this->cObj->convertToUserIntObject() and immediately stop further
> processing.
>>
> As I haven't used this function yet, I don't know if it has any side
> effects for caching. Does anybody already have experience with this?

Using the new convertToUserIntObject() will not work as the the 
Dispatcher must be called as USER od USER_INT. If it is already defined 
to be USER the method convertToUserIntObject() inside the Extension will 
never be called.


Jochen


More information about the TYPO3-project-typo3v4mvc mailing list