Bug #17627
closed
External TypoScripts files will always be cached
Added by Eckhard M. Jäger almost 17 years ago.
Updated almost 14 years ago.
Description
Scenario:
I'm using SweeTS (typo3.area42.de) developing TYPO3 websites with an external typoscript file. I disable template caching so any changes of the template are visible by reloading the frontend:
page.config.no_cache = 1
<INCLUDE_TYPOSCRIPT: source="FILE: /fileadmin/sweets.ts">
Problem:
When i change my external typoscript files and reload the frontend in the browser nothing happens because the external typoscript file is always being cached. So i have to go to the backend and must clear the FE chache first. The very bad for the workflow working with external typoscript files.
Solution:
May if template cache is disabled include cache should be disable too. Another solution could be a new Command:
page.config.no_cacheInclude = 1
SweeTS: typo3.area42.de
(issue imported from #M6395)
Files
Workaround for this issue is to add the following lines in User TSConfig:
admPanel.override.tsdebug.forceTemplateParsing = 1
Thanx Lucas! A great hint :)
I published this hint (and some more) at the SweeTS website and added you as a contributor.
A possible solution: Extend the rowSum data with the file templates and their mtime, then check for modification (= new mtime) right after checking the rowSum (happens in t3lib_TStemplate).
I attached a patch file "patch_6395.diff" which implements Michaels suggestions to add an information about the file templates to the rowSum array.
But instead of adding the file mtime I simply added the md5 sum of the template string, containing the included templates. so if the templates get changed their md5 sum will change and they get parsed again.
Also available in: Atom
PDF