Smarty

[fbronx]

I'm using template resources and the {include} statement for the themes of my CMS I'm currently developping. My question is: how can I use a compile_id for the templates that come from a resource? At the moment I have only one theme, but when I provide more there will be the danger that other theme templates get overwritten.

An example:

{capture name=content}
...
{/capture}
{include file="theme:main_block.tpl" title=#TITLE# content=$smarty.capture.content}

[messju]

you shouldn't bother if the template comes from a resource or from the filesystem. smarty uses different compiled templates for different compilde_ids in both cases.

[fbronx]

Do you mean that the following code :

function theme_get_template ($tpl_name, &$tpl_source, &$smarty_obj)
{
global $g_settings;
$fname = dirname(__FILE__) . '/themes/' . $g_settings->style . '/templates/' . $tpl_name;
$fh = fopen($fname, 'r') or die("template $fname doesn't exist! ");
$tpl_source = fread($fh, filesize($fname));
fclose($fh);
return true;
}

doesn't create problems when $g_settings->style changes ?

[messju]

you where talking about compile_ids. so if you have distinct compile_ids for each $g_sesstings->style it should work.

[fbronx]

Ok. I just found out that I can set the compile_id after reading the template like this:

function theme_get_template ($tpl_name, &$tpl_source, &$smarty_obj)
{
global $g_settings;
$fname = dirname(__FILE__) . '/themes/' . $g_settings->style . '/templates/' . $tpl_name;
$fh = fopen($fname, 'r') or die("template $fname doesn't exist! ");
$tpl_source = fread($fh, filesize($fname));
$smarty_obj->compile_id = $g_settings->style;
fclose($fh);
return true;
}

I think this is a nice way of creating themes. Or are there better solutions for this?

[messju]

id'd prefer simply assigning $theme and using {include file="$theme/foo.tpl"} everywhere instead of messing with resources and compile_ids