diff --git a/docs/en/programmers/api-variables/variable-compile-check.xml b/docs/en/programmers/api-variables/variable-compile-check.xml index d269d05a..ea3e3476 100644 --- a/docs/en/programmers/api-variables/variable-compile-check.xml +++ b/docs/en/programmers/api-variables/variable-compile-check.xml @@ -7,15 +7,17 @@ current template has changed (different time stamp) since the last time it was compiled. If it has changed, it recompiles that template. If the template has not been compiled, it will compile regardless of this - setting. By default this variable is set to true. Once an application is + setting. By default this variable is set to true. + + Once an application is put into production (templates won't be changing), the compile_check step is no longer needed. Be sure to set $compile_check to "false" for maximal performance. Note that if you change this to "false" and a template file is changed, you will *not* see the change since the template will not get recompiled. If - caching + $caching is enabled and - compile_check is enabled, then the cache files will get regenerated if + $compile_check is enabled, then the cache files will get regenerated if an involved template file or config file was updated. See $force_compile or clear_compiled_tpl(). diff --git a/docs/en/programmers/api-variables/variable-force-compile.xml b/docs/en/programmers/api-variables/variable-force-compile.xml index 227cbd03..8c93be4c 100644 --- a/docs/en/programmers/api-variables/variable-force-compile.xml +++ b/docs/en/programmers/api-variables/variable-force-compile.xml @@ -10,7 +10,7 @@ this is disabled. This is handy for development and debugging. It should never be used in a production environment. If - caching + $caching is enabled, the cache file(s) will be regenerated every time.