Quote:
Originally Posted by stephencarr  If that is true then this is bad for templaters. Since all the stuff in libs is core code the template methodology would mean you don't touch that. I want to be able to dump a template in my templates directory and it just work, I don't want to have to request a user to update his lib folder too. I thought smarty was smarter than having to pre-define includes. |
I would guess then you would have to use the standard names for the tpl files to have a standard template that would work by just putting it in the templates folder. If your gonna change the names to other, non standard names, then I guess an update to the smartyvariables would be needed. Like I said, I'm not 100% sure if they are absolute, I just did a search in the code to find where the tpl files are specified, and it seems that the smartyvariables is where the names of the files are set. Maybe the smartyvariables file should be in the template folder itself, so that it comes with the new template (just a thought). Then the template maker would set the file names in the smartyvariables file to match the names they use. You could run into some problems though, because some people don't use the same common sense naming as others.