Re: [Astlinux-users] php.ini

2014-07-14 Thread Michael Knill
Ahh I have it now. I will do it in the PHP files itself. ini_set(“display_errors", 0); ini_set(“log_errors”, 1); Thanks for your help. Regards Michael Knill On 15 Jul 2014, at 9:48 am, Lonnie Abelbeck wrote: > Michael, > > The "/etc/php.ini" file is the global file used by our latest PHP

Re: [Astlinux-users] php.ini

2014-07-14 Thread Lonnie Abelbeck
Michael, The "/etc/php.ini" file is the global file used by our latest PHP and lighttpd. This was not always the case and that is why you see other legacy php.ini's in the web interface. If PHP is called via the command line, possibly a php.ini in the same directory may be used, but I'm not c

Re: [Astlinux-users] php.ini

2014-07-14 Thread Michael Knill
Thanks Lonnie. Sorry I thought it was a bit easier than this so I didn’t put it in the dev list. The problem with display level error reporting is that I use PHP for all my phone startup routines and a large number of XML phone features. I hate access codes. As you would imagine, phones don’t r

Re: [Astlinux-users] php.ini

2014-07-14 Thread The Cadillac Kid
I always handled it the other way around for production systems. Generally error reporting defaults to off in the php.ini file and then while you are developing a script, module, etc you turn it on in the runtime for debugging, this way it defaults to the more secure option. (it is also the way

Re: [Astlinux-users] php.ini

2014-07-14 Thread Lonnie Abelbeck
Hi Michael, This question probably belongs on the -devel list, but here goes... To directly answer your question, you could edit "/etc/php.ini" and restart 'lighttpd' to apply the change. Though this is not what I would do. You could "ignore display errors" selectively by using the '@' error c