Smarty

you can't. maybe pass it as an attribute like template=$smarty.template.

Yes, that's a possible solution, but I don't like it really. The function is called very often within the template and the a ...

I'm gonna push this up again cause I didn't got an answer. Is it possible to find out the template name inside a custom template function? I need to know from where the function has been called to giv ...

I need to know the name of the template within a plugin. Is there any way to find this out via the $smarty variable. Inside a template you can get it by the reserved variable {$smarty.template} but I ...

Thanks, messju, your suggestion works like expected.

When you assign variables in a template they have a local scope to the template itself and all included templates. What I'm looking for is a clean way to assign local variables from PHP. Is there anot ...

Using the file name as alt value doesn't make sense in many cases since the file name is often auto generated (e.g. MD5 hash), especially in typical situations when you need html_image like showing da ...

I think, an empty attribute (alt="") will be better as default. Try to browse a web site with lynx, and you'll see the reason: if the attribute is missing, lynx will display the filename instead, whic ...

You're right, in fact what I use is similar to an include. The params are also mapped. The reason I do it this way is to make it more comprehensive to the web designers I work together with. They are ...

I had a need for this a few days ago. What I wanted to implement was the following:

{$var|wrapper:"box.tpl"}

that should result in building a html wrapper around the value. As $this is not a ...

As I understood the recent HTML recommendations from the W3 consortium, every <img> tag should always contain an "alt" attribute, even if it's empty. The W3 validator throws an error when the al ...

I also like the idea of a $default_resource_type (see poll thread). This will also make the lookup of template files transparent. What I like to avoid is a need for "path:" e.g.

{include fil ...

Multi-language support is an additional thing. I primary use GNU gettext for that via a custom function, e.g.

{locale id="nav_home"}

Maybe I should write another feature ...

Someone else had the same idea. This is from the wiki (Smarty Feature Sugguestions):

* Allow array for template_dir. This is something I've done before, it gives a lot of flexabilty to creat ...

Thanks for the links. I took a look into most of the discussions and my conclusion is, that $template_dir as array optionally will solve the basic problem. I like this concept also, since Smarty is us ...

Yes, of course this can be done via a resource handler. But I think, implementing the array functionality for $template_dir would be simpler than the resource handler - maybe I'm not right. Also to me ...