Smarty

[omarv_r]

Hello, I am new in this forum.

I want to know if is possible to get the path and filename of the template that is being processed at a gave moment.

Thanks

[AnrDaemon]

How would that help you, if template storage is a database?

[omarv_r]

Hello again.

I have a template that includes a subtemplate. In that subtemplate I call a custom Smarty function passing a filename as parameter (something like: {foo filename="../myfile.dat"} ) to be processed by the custom function.

My problem is that the filename could be relative to subtemplate's location. In that case, into the custom function, I can't read the file (ex. using get_file_content) because I only know which is the template's folder (not subtemplate).

Obviously, if I know where the subtemplate is located, then I could locate the file passed as a parameter even if it's path is relative.

Thanks.

[U.Tews]

In the function plugin the template object is passed as 2nd parameter.
$template->parent->source->filepath will give you the filepath of the calling template.

[AnrDaemon]

[omarv_r]

AnrDaemon, thanks for your answer.

You have reason, I should not. But believe me: this data must be in the presentation tier

Thank you again.

[omarv_r]

Hello U.Tews.

The correct answer for my case is: $template->source->filepath

Lets say that we have:

(1) c:\folder1\template.tpl.php

that includes:

(2) c:\folder1\folder2\sub_template.tpl.php (this last one calls the function)

Into the function:

$template->parent->source->filepath

is returning (1), whereas:

$template->source->filepath

returns (2)... what I need!

Thank you because without your answer I had not found the solution.

Thank to AnrDaemon too for his interest.

(And I apologize for my english, but I speak spanish )

[AnrDaemon]

If this data should be in presentation tier, then pass the data (or path to the data) explicitly.
You are solving a nonexistent problem, I'm afraid.

Besides, string binary data in the templates directory does not sound right to me. Or if the data is not binary, may be just {include} it? Or rewrite it as a Smarty config file?