Smarty

[andreas]

Hi!

From a PHP-Script I can assign an array only to one template. But my problem is, I would like to assign an array to a header.tpl which is included into my "main-template" where I assign other variables to.

I've got something like this

file.php:

[messju]

any variables that are visible inside your file.tpl are also visible in your header.tpl .

just use {$something} inside your header.tpl it should be definately visible there.

the only thing with the scope is: you cannot *change* $something inside your header.tpl in the hope, these changes will be accessible in file.tpl afterwards.

but you don't want to change these values anyway. you just want to display.

for the header.tpl at a fixed location and dynamic template_dirs, you can use an absolute path:

$smarty->assign('header_tpl', 'file:'.[path_to_header.tpl]);
and then do {include file=$header_tpl} where needed.
(you can also use a config-var of course, but you may want to build $header_tpl dynamically relative to other vars in your php (SMARTY_DIR or dirname(__FILE__) comes to mind), then a template-var is better than a config-var)

as a side note: if you use different template_dirs, ensure you use a distinct compile_dir for each template_dir, or you may get clashes.

HTH
messju

[andreas]

Thank you for your quick response!

I did not expect it was so easy

But thanl you for your side note! Thats not nice becaus I use plugins that could be added later and I did not want to have changes outside my plugin-directory, I think I should add the compile_dir to my plugin-dir. Not nice.
But why is it done this way? It should not couse problems to see the different template-dirs in smarty-class, does it? Perhaps a "feature-request"?

anyway, thank you very much(Danke Dir )!

Gr??e
Andreas
________
buy silversurfer vaporizer

[messju]

the point is:

it is fully legal to have many subdirectories in your templates_dir and use these as display("$foo/index.tpl"); with changing $foo.
it is also fully legal to use full-paths and one singe compile-dir.

but what causes trouble is:
$smarty->template_dir = $a;
$smarty->display('index.tpl');
[... another page, another user ....]
$smarty->template_dir = $b;
$smarty->display('index.tpl'); // another index.tpl intended
with just one compile_dir

smarty thinks index.tpl is already compiled (since it is in compile_dir), but it is the wrong one. this is where it breaks.

there are loads of workarounds (some of them may even lead to cleaner application design than switching around with $smarty->template_dir,
but that depends on the application, of course):
- using stuff like {include file="$skin_dir/index.tpl"}
- using resources ( http://smarty.php.net/manual/en/templates.from.elsewhere.php )
- using different compile_ids

there may be even more and having to use different template_dirs is not a common problem to me (ymmv) so i don't know if fixing this would be worth the effort.

greetings
messju