Re: knowing your template

boots wrote:
> No, unfortuantely there is not. If you are in a compiler function (or a
> prefilter) you can access a private member, $compiler->_current_file --
> which is the fullpath to the actual template file -- but if you want to
> use it after compile time, you will need to insert a corresponding
> assignment into the template code. There shouldn't be a problem with
> nesting as scope is restored after an include is completed.

Is there a plan for this in 3.0 or so?

Iv

-- 
Smarty Development Mailing List (http://smarty.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php