Hi Peter,

Changing a template through the admin UI should not be the case as it should use TemplateService to manually invalidate the cache.

So whatever scenarios are that templates are being changed without manually invalidating corresponding cache are impacted, like changing directly the template system file by an external editor.

This is only about changing default configuration for template caching which will be used if the cache system property setting is omitted. If you don't find any impact, I would like to change this in 3.7 and master branches.

WDTY ?