Re: [SMARTY-DEV] Re: config vars are now static

I certainly don't want to cause backward compatability problems, and I think I see what your conundrum is. {config_load file=$lang} This would load a dynamic config file at run-time, chaning the static data. How about this, the config_load function creates a static template that gets included at runtime. This way the data is still compiled statically, but included dynamically at runtime. Sound like it will work? Monte Thomas Seifert wrote:

Hey everyone, ouch that gets nasty. That means I can't upgrade my smarty-installation any longer. I'm using config-files for adding language-abstraction to my apps where the lang-files are loaded dynamically as config-files. Any way to make this new behaviour optional? Thomas On Sat, 14 Jun 2003 04:34:31 -0700 (PDT) jayboots@yahoo.com (Boots) wrote:

Hi Monte. Just started testing the new config var patch. Initial observation is that as a consequence of going compile time, two important issues arise: 1. Literal names in the config_file 'file' parameter are now required: no more dynamically selected configurations. No longer supported: {config_load file=$config_file}

Let alone this:      {config_load file=$Object->config_file}

2. All templates are now required to explicitly do a config_load to have access to the configuration values. I think the previous framework still allowed for a static config_load implementation (well, I did work against 2.5 that achieved a similar outcome.} I like the idea, but I think that those are pretty big changes. xo boots __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com