Re: [SMARTY-DEV] DEBUG console feature

There is a property called $debugging_ctrl which determines if URL based debugging is enabled or not. This can be 'NONE' or 'URL' at the moment. Maybe adding a new setting here could add this control. (SESSION, COOKIE, ?) This just seems to be a useful enough feature to add to the core. Our designers run into the problem occasionally. They end up having to place a {debug} statement in the template that they are debugging, which means they have edit a template and remember to remove it later. Monte On Fri, 2003-12-19 at 09:27, Thomas Lutz wrote: > Monte Ohrt wrote: > > > My only reservation about this is that it starts a session, which means > > it may have to output an HTTP header to the browser. I don't know if it > > is smarty's place to be messing with sessions. > > In my opinion that's a feature smarty should not have in it's default > behaviour. > I'd say that if someone wants that his smarty setup to remember it's > debug state, he should implement that in his very own web application. > > That's the way I handle it in my pages, when everything is set up for > action (page startup), a session var sets debugging of my smarty > instance to True or False. And if this session var is changed by a get > or post request, it remembers it's state... > But that's my session handling class, and I am sure, that no one > except this class has something to do with sessions. > > So if this feature is implemented, let us switch it off, or even > better set default to off. > > Really great template engine, thank you ! > > Tom > >