smarty-php/smarty
1
0
Fork 0
mirror of https://github.com/smarty-php/smarty.git synced 2025-08-05 10:54:27 +02:00
Code Issues Packages Projects Releases Wiki Activity

added examples to compile_id. thanks to Pete_M.

Browse Source
This commit is contained in:
messju
2005-04-06 19:29:49 +00:00
parent 8f0c1f7026
commit b2532a58c3
1 changed files with 33 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
docs/en/programmers/api-variables/variable-compile-id.xml
View File

@@ -1,12 +1,37 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision$ -->
<sect1 id="variable.compile.id">
<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.
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: