[TYPO3-ect] lib/div multiple extension with same key on one page - action dispatcher

Michael Knoll mimi at kaktusteam.de
Wed Sep 26 13:07:08 CEST 2007


Franz Koch wrote:
> Hi Elmar,
> 
>> I think there are solutions.
>> Using the ext_key as designator is only the fallback solution, if you do
>> nothing else!!!
>>
>> I.e. you can set "var $defaultDesignator" to any value you like or 
>> provide a
>> key in the moment of link generation.
>>
>> It's that flexible, because the requirements are very different for
>> different extensions. Sometimes different plugins work synchronized. They
>> need to share the same designator. Sometimes the same extension needs
>> different designators within the same page, like in your case.
>>
>> The designator should be "unique enough" (TM), so best start with the
>> extension key and end with a string of your choice.
>> Often the controllers class name is a good designator (like in
>> tslib_pibase): tx_myext_aController
> 
> well, I guess this solution is not a propper solution for the problem. 
> What if you have two instances of the same plugin that have to listen to 
> the same piVars, but one should allow for actionA (e.g. category view) 
> and actionB (e.g. listing of category items) and the second should 
> always show actionC (detailView).
> 
> This problem also existed in cal and it's solved like this:
> There is a configuration option (TS which can be overridden with FF) 
> where you can define allowed actions for a controller. If the action 
> request is within the list of allowed actions, it's executed (if it 
> exists) - if not, it falls back to the first allowed action/view.
> 
> I think this is also needed for lib/div as a basic feature if it's not 
> already there somewhere (didn't follow the last changes).
> 
> -- 
> Kind regards,
> Franz Koch

Hm... only an idea - what about taking the UID of the controller object 
from the page it is inserted - so you will know, which plugin insertion 
handles which form. This only works, if the is inserted as tt_content 
and not created via another plugin or things like that. But this would 
handle different plugin inserted on the same page.

Regards

Mimi


More information about the TYPO3-team-extension-coordination mailing list