Re: [SMARTY-DEV] RE: config_load API

From: Date: Mon, 09 Dec 2002 20:36:00 +0000
Subject: Re: [SMARTY-DEV] RE: config_load API
References: 1  Groups: php.smarty.dev 
Request: Send a blank email to php-smarty-dev+get-392@lists.php.net to get a copy of this message
When you use config_load() from the API, there is no template. You're just loading vars into global space. Is that what you meant? On Mon, 2002-12-09 at 14:31, Gerard wrote: > 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 -- Monte Ohrt <monte@ispi.net>

« previous php.smarty.dev (#392) next »