RE: config_load API

Just a thought :) Maybe an 'exclusive' attribute (or something) is needed for {config_load} if people want to use *only* the config(s) loaded by that template. I like config_load() :) Gerard gerard@interfold.com >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I'm working on adding the config_load API function, and I see that the assigned config array is wiped clean any time fetch() or display() is called. Does anyone see a problem with removing that behavior? For example: $smarty->config_load('foo.conf'); $smarty->fetch('1.tpl'); $smarty->fetch('2.tpl'); $smarty->fetch('3.tpl'); Whatever was loaded from foo.conf should be retained thereafter, not wiped out by calling fetch(). However, {config_load ...} calls from within the templates could affect the loaded variables. Monte