|
From: Christian B. <pos...@cb...> - 2011-02-13 22:07:21
|
Hello, Am Sonntag, 13. Februar 2011 schrieb David Goodwin: > On 13 Feb 2011, at 18:43, Christian Boltz <pos...@cb...> > wrote: > > We could do this easily inside the PFASmarty class (in __construct) > > - no need to make those settings public. > > > > That would also mean we can remove __set, __get and __call. > > > > Objections? > > None. Motion carried :) OK, I moved the smarty setup (template_dir etc.) into __construct() and removed __set, __get and __call. A quick test didn't show any breakage :-) [smarty compile_dir in /tmp] > Sorry. Didnt realise I'd committed or written that. Then you must have a ghost in your keyboard - or your dog is better at typing than you thought ;-) I'll remove the /tmp/ stuff. Commit follows in some minutes. > > That said: Some time ago, I asked if it would be possible to have > > NO compile_dir at all (and recompile the templates every time). > > IIRC the answer was "yes, that's possible", however I have no idea > > how to do that. > > There's a config parameter to do it. Can't remember which ones, but > It is possible to do with smarty. I tried googling this, but didn't find an answer. Would be nice if you can find it out ;-) Regards, Christian Boltz -- wer Windows in irgendeiner Form verwendet (ausser als abschreckendes Beispiel) ist selbst schuld. [Carsten Becher in suse-linux] |
