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

Stefan Wild sw at sw4.de
Sat May 22 09:30:41 CEST 2010


This is what I did and it works nicely (if you remember to pass 
{settings} to your partials)

> You define a select in the flexform which contains the action you want 
> to call on this page, the first action in the list is the one which 
> will be called. (Important you have to define all actions you want to 
> access on this page too for example: If you index links to a 
> "addAction" you have to say myController->index; myController->add in 
> the values)

Thanks, Alex.

> you're right, hard-coding the target PID in the template would be bad. 
> A common approach in TYPO3 is to create TypoScript settings for the 
> respective PIDs. For the ease of use you might want to add TS constants 
> for those as well:

Thanks, Bastian.

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 :-/

My workaround for now is to disable cache in the page configuration 
where that controller is called. Not the clean way, though.

Best regards,
Stefan



More information about the TYPO3-project-typo3v4mvc mailing list