Re: config vars are now static

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