cvs: smarty /docs/en/programmers/api-variables variable-compile-id.xml
"Messju Mohr" <[email protected]>
| Newsgroups | gmane.comp.php.cvs.smarty |
|---|---|
| Message-ID | <cvsmessju1112815792@cvsserver> |
messju Wed Apr 6 15:29:52 2005 EDT
Modified files:
/smarty/docs/en/programmers/api-variables variable-compile-id.xml
Log:
added examples to compile_id. thanks to Pete_M.
http://cvs.php.net/diff.php/smarty/docs/en/programmers/api-variables/variable-compile-id.xml?r1=1.1&r2=1.2&ty=u
Index: smarty/docs/en/programmers/api-variables/variable-compile-id.xml
diff -u smarty/docs/en/programmers/api-variables/variable-compile-id.xml:1.1 smarty/docs/en/programmers/api-variables/variable-compile-id.xml:1.2
--- smarty/docs/en/programmers/api-variables/variable-compile-id.xml:1.1 Tue Apr 13 07:39:14 2004
+++ smarty/docs/en/programmers/api-variables/variable-compile-id.xml Wed Apr 6 15:29:49 2005
@@ -1,12 +1,37 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.1 $ -->
- <sect1 id="variable.compile.id">
- <title>$compile_id</title>
- <para>
- Persistant compile identifier. As an alternative to passing the same
- compile_id to each and every function call, you can set this compile_id
- and it will be used implicitly thereafter.
- </para>
+<!-- $Revision: 1.2 $ -->
+<sect1 id="variable.compile.id">
+ <title>$compile_id</title>
+ <para>
+ Persistant compile identifier. As an alternative to passing the same
+ compile_id to each and every function call, you can set this
+ compile_id and it will be used implicitly thereafter.
+ </para>
+ <para>
+ With a compile_id you can work around the limitation that you cannot
+ use the same compile_dir for different template_dirs. If you set a
+ distinct compile_id for each template_dir then smarty can tell the
+ compiled templates apart by their compile_id.
+ </para>
+ <para>
+ If you have for example a prefilter that localizes your templates
+ (that is: translates language dependend parts) at compile time, then
+ you should use the current language as compile_id and you will get a
+ set of compiled templates for each language you use.
+ </para>
+ <para>
+ Another example would be to use the same compile directory across
+ multiple domains / multiple vhosts. eg:
+ </para>
+ <example>
+ <title>compile_id</title>
+ <programlisting role="php">
+<![CDATA[
+ $smarty->compile_id = $_SERVER['SERVER_NAME'];
+ $smarty->compile_dir = 'path/to/shared_compile_dir';
+]]>
+ </programlisting>
+ </example>
</sect1>
<!-- Keep this comment at the end of the file
Local variables:
@@ -27,4 +52,4 @@
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
--->
\ No newline at end of file
+-->
--
Smarty CVS Mailing List (http://cvs.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php