cvs: smarty /docs/en/programmers/api-variables variable-compile-check.xml variable-force-compile.xml
"Peter 'Mash' Morgan" <[email protected]>
| Newsgroups | gmane.comp.php.cvs.smarty |
|---|---|
| Message-ID | <cvspete_morgan1126633489@cvsserver> |
pete_morgan Tue Sep 13 13:44:49 2005 EDT
Modified files:
/smarty/docs/en/programmers/api-variables
variable-compile-check.xml
variable-force-compile.xml
Log:
tweaks
http://cvs.php.net/diff.php/smarty/docs/en/programmers/api-variables/variable-compile-check.xml?r1=1.2&r2=1.3&ty=u
Index: smarty/docs/en/programmers/api-variables/variable-compile-check.xml
diff -u smarty/docs/en/programmers/api-variables/variable-compile-check.xml:1.2 smarty/docs/en/programmers/api-variables/variable-compile-check.xml:1.3
--- smarty/docs/en/programmers/api-variables/variable-compile-check.xml:1.2 Mon May 23 11:43:01 2005
+++ smarty/docs/en/programmers/api-variables/variable-compile-check.xml Tue Sep 13 13:44:48 2005
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.2 $ -->
+<!-- $Revision: 1.3 $ -->
<sect1 id="variable.compile.check">
<title>$compile_check</title>
<para>
@@ -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.
+ </para>
+ <para>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
- <link linkend="variable.caching">caching</link>
+ <link linkend="variable.caching">$caching</link>
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 <link
linkend="variable.force.compile">$force_compile</link> or <link
linkend="api.clear.compiled.tpl">clear_compiled_tpl()</link>.
http://cvs.php.net/diff.php/smarty/docs/en/programmers/api-variables/variable-force-compile.xml?r1=1.2&r2=1.3&ty=u
Index: smarty/docs/en/programmers/api-variables/variable-force-compile.xml
diff -u smarty/docs/en/programmers/api-variables/variable-force-compile.xml:1.2 smarty/docs/en/programmers/api-variables/variable-force-compile.xml:1.3
--- smarty/docs/en/programmers/api-variables/variable-force-compile.xml:1.2 Mon May 23 11:43:01 2005
+++ smarty/docs/en/programmers/api-variables/variable-force-compile.xml Tue Sep 13 13:44:48 2005
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.2 $ -->
+<!-- $Revision: 1.3 $ -->
<sect1 id="variable.force.compile">
<title>$force_compile</title>
<para>
@@ -10,7 +10,7 @@
this is disabled. This is handy for development and
<link linkend="chapter.debugging.console">debugging</link>.
It should never be used in a production environment. If
- <link linkend="variable.caching">caching</link>
+ <link linkend="variable.caching">$caching</link>
is enabled, the cache file(s) will be regenerated every time.
</para>
</sect1>
--
Smarty CVS Mailing List (http://cvs.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php