Smarty

[Mike Bradley]

I have been using config_file to implement language versions of my pages (the language files being selected at install time, rather than run-time), but looking at the compiled code I was wondering if these were being implemented in the best way.

It strikes me that .conf files are not intended to be changed that often, in which case could the configuration values not be inserted statically into the compiled page? Any changes to the .conf files would need to result in a recompile.

This would save the script from having to load and parse the .conf files on each page load, at least when the file is loaded with local scope.

Any downside on this? Am I correct in thinking that {# #} values are supposed to be more static than {$ } values?

Mike

[Tom Sommer]

IIRC config files are already pre-compiled?

[Mike Bradley]

Well what do you know - they already thought of that! I never realised that the config files were compiled as well!

Mike

[Tom Sommer]

great isn't it

[Mike Bradley]

One thing - how do I assign the values 'Yes' and 'No' in the config file?

If I do:

lsYes = Yes
lsNo = No

They get evaluated to 1 and 0 respectively

But if I do

lsYes = Ja
lsNo = Nej

They evaluate to Ja and Nej - do Yes and No have special meaning here? If I enclose in quotes, it has no effect.

Mike

[plockaby]

To keep from converting "yes" and "no" to 0 and 1, set the smarty variable $config_booleanize to false or set the config class variable $booleanize to false, depending on which method you're using to access your config files.

[Mike Bradley]

You star - it took a few goes and I had to remember to delete my cache, but it worked just fine.

Mike