[TYPO3-dev] plans for 4.2 end of life

[Peter Kuehn [wmdb]]

 > 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 ;)

Martin Kutschker schrieb:
> Peter Kuehn [wmdb] schrieb:
>> no. i will definately not start a discussion if crashing servers by
>> accidently saving a TSTemplate in the wrong module is a bug or not. no.
>> not again ;)
>>
>>> You won't see any new features - no, not even tiny ones.
>> didnt expect features at all - who would. i was asking for guidelines,
>> what will be considered being a bug and what a missing feature.
> 
> Then I didn't understand the question. Data corruption is certainly a
> bug, but I don't understand what saving a TStemplate in the wrong module
> means. You can access a TS template only via alt_doc.php (Web>List or
> "edit full record" link in Web>Template) or via Web>Template. What other
> module can be a "wrong" one.
> 
> Masi