[TYPO3-dev] plans for 4.2 end of life

[Martin Kutschker]

Steffen Kamper schrieb:
> Hi,
> 
> Martin Kutschker schrieb:
>> Peter Kuehn [wmdb] schrieb:
>>>> I don't understand what saving a TStemplate in the wrong module
>>>> means.
>>> short version: every saving of data in "web > template" does a clear all
>>> cache.
>>>
>>> simply create an +ext template in "Web > Template" on a subpage to
>>> modify a plugin: sysext/tstemplate/index.php line 422 triggers
>>> $tce->clear_cacheCmd("all");
>>> open an existing one the modfunc "Info/Modify", edit and save it from
>>> there: sysext/tstemplate_ceditor/class.tx_tstemplatecseditor.php line
>>> 132 will do the job for you.
>>> see sysext/tstemplate_objbrowser/class.tx_tstemplateobjbrowser.php line
>>> 271 for another example.
>>>
>>> do so cause you dont know on a site with lots of traffic and some GB of
>>> cache_*-pages and watch your phone ;)
>>
>> Ah. I see that this is a problem for *some* sites. Having the cache
>> cleared automatically is usually handy. So I see two options:
>>
>> * make the cache clearing configurable
>>
>> * find out which parts of the tree are affected and clear the cache only
>> for this branch
>>
>>
>> Masi
> 
> there are also other possibilities:
> * set the TCEMAIN .clearCache_disable option

If it can be disabled already then there is nothing to do/fix.

> * xclass typo3_db and rewrite delete
> * xclass tce_main and rewrite clear_cacheCmd

I was thinking of what could be done in the Core to solve the issue for
the public.

Masi