[TYPO3-mvc] mvc_extjs problem - no javascript-code added

[Thomas Hucke]

Hey Dennis,

thank you for this mega quick reply!
I will give it try switching the dispatcher as you´re suggesting.

Regarding this caching issue:
I did my latest investigations using the "alpha2"-tagged versions of extbase 
and fluid.
So I assume that the latest changes didn´t implement a solution.
Unfortunately I don´t have a clue yet to construct a test case without using 
mvc_extjs.

First I´ll try the dispatcher stuff.
Then I´ll go into the investigation for opening a ticket.
I´m not really sure whether the change i suggested could be implemented 
without any side-effects.

Greets
Thomas


"Dennis Ahrens" <dennis.ahrens at googlemail.com> schrieb im Newsbeitrag 
news:mailman.1.1286209067.3439.typo3-project-typo3v4mvc at lists.typo3.org...
> Hi Thomas,
>
> Thomas Hucke wrote:
>> BTW: It seems to me that the dispatcher class of mvc_extjs isn´t executed 
>> in any case. Does anyone know why?
>
> I've just "linked" the Dispatcher for BE-Modules. You have to change the 
> TypoScript configuration created by 
> Tx_Extbase_Utility_Extension::configurePlugin() - the
>
> userFunc = tx_extbase_dispatcher->dispatch
>
> is specified there. You may change this for your plugin to 
> tx_mvcextjs_dispatcher->dispatch - this might by achieved by adding this 
> TypoScript for your EXT:
>
> tt_content.list.20.yourPluginSignature.userFunc = 
> tx_extbase_dispatcher->dispatch
>
> have not tried this by now. I like to repeat that you should only use this 
> Dispatcher, if you like to use Ext.Direct :)
>
> Related to the caching problem:
> I still haven't digged into the caching issue - have you figured out, if 
> the last changes made by Bastian solve this issue? If they don't, i guess 
> you should file a ticket on forge related to extbase.
>
> regards
> Dennis