[TYPO3-mvc] Caching Problem

[Xavier Perseguers]

Hi Jochen,

>> Just wanted to add something. We have to use
>> Tx_Extbase_Utility_Plugin::registerPlugin() in ext_localconf.php for the
>> cache to work as expected but we still need to have it in ext_tables.php
>> in order to get the plugin available in BE.
>>
>> @Jochen: can you do something about this? For instance keep the old way
>> of having to use two different method calls in order for a plugin to be
>> registered? One in ext_tables.php for registering it and one in
>> ext_localconf.php to update the tt_content TypoScript.
> 
> Hmm, maybe we have to have two different methods instead of 
> Tx_Extbase_Utility_Plugin::registerPlugin().
> 
> Unfortunately, I am not able to reproduce this issue by now. So it is a 
> little bit difficult for me to handle that. Could you make a patch that 
> works for you, please.

I found exactly where the problem was, it's straightforward where 
reading the phpDoc of t3lib_extMgm:

At the end of your registerPlugin() you basically do two calls, one for 
actually registering in the list of plugin (available from BE) and one 
for telling TYPO3 how to render it with the generated TS.

Call for "registering" is t3lib_extMgm::addPlugin() and phpDoc in 
t3lib_extMgm says: FOR USE IN ext_tables.php FILES

while call for rendering is t3lib_extMgm::addTypoScript() and phpDoc 
this time says: FOR USE IN ext_localconf.php FILES

What about two methods addPlugin() and addTypoScript() or keep the 
registerPlugin() which I quite like for ext_tables.php and add a 
registerTypoScript() or something like that for ext_localconf.php, in 
order to have similar call than when dealing directly with t3lib_extMgm 
but still be a bit different to not call the wrong ones?

Regards

-- 
Xavier Perseguers
http://xavier.perseguers.ch/en

One contribution a day keeps the fork away