Smarty

$smarty->assign('test', '123');
echo $smarty->fetch('foo.tpl');
$smarty->clearAssign('test');
$smarty->assign('test', '456');
echo $smarty->fetch&# ...

/root/sub/bar.tpl
{include file="../foo.tpl"} {*try to load template in root*}
{include file="foo.tpl"} {*try to load template in sub*}
...

I understand you.
But you are not banned using the relative path starting with ../ in the tempaltes.
Maybe better way to use something like open_basedir in php.ini?

/templates/bar.tpl
/templates/alpha/bar.tpl

and

$smarty->setTemplateDir(array(
'/templates/alpha',
'/templates/',
));

If you'd call $smarty->fetch('bar.tpl'); ...

$smarty->template_dir is an array.
include_path in php.ini also contents several paths and it works well. So it's strange argument about an array.

have to be relative to the current working directory (usually a bad idea) or relative to SMARTY_DIR (yet another bad idea).
In previous versions relative path starts from $smarty->template_dir. Ho ...

$template_dir = /some/path
template /some/path/sub/test.tpl

test.tpl
{include file="../main.tpl"}
{include file="main.tpl"}

In the case {include fil ...

Woks strange:

include 'smarty/Smarty.class.php';
$smarty=new Smarty();

//set absolute path for template dir
$smarty->setTemplateDir(dirname(__FILE__).'/ ...

I made function canonicalPath (see code of globe at first page) and made some changes in sysplugins/smarty_internal_template.php
In method buildTemplateFilepath I changed all "return $some_file; ...

This is not possible as template_dir can be an array which is scanned if you call display('my.tpl');
We need to get the path of the matching array element.
For that reasion we can't skip the test ...

Another idea: it may be possible to cache the path of existing templates in the file?
Something like that:

public function buildTemplateFilepath ($file = null)
{
if ($this-& ...

Thank you! I will wait.

Anyway there will be some changes in filepath handling in the upcomming version 3.1.
Can I expect these changes soon in svn?

Why not simply use a unique way of specifying the template_dir filepathes in your project.....

In the code, I prefer to use absolute paths, so there's no problem - I can bring them to the required ...

In the method buildTemplateFilepath already present verification that the path relative. So that verification can be simplified.