Re: [PHP-DEV] set the PHP_INI_ENTRY_* values the same as for php.ini-production

2012-04-01 Thread Daniel Convissor
Hi Folks: On Wed, Mar 14, 2012 at 10:33:59AM -0700, Christopher Jones wrote: In that case, perhaps the STD_PHP_INI_* values should match those in php.ini-development? Many sites have very small ini files and rely on the default ini values for everything else. This means changing the

Re: [PHP-DEV] set the PHP_INI_ENTRY_* values the same as for php.ini-production

2012-04-01 Thread Ferenc Kovacs
On Sun, Apr 1, 2012 at 6:25 PM, Daniel Convissor dani...@analysisandsolutions.com wrote: Hi Folks: On Wed, Mar 14, 2012 at 10:33:59AM -0700, Christopher Jones wrote: In that case, perhaps the STD_PHP_INI_* values should match those in php.ini-development? Many sites have very small

Re: [PHP-DEV] set the PHP_INI_ENTRY_* values the same as for php.ini-production

2012-03-15 Thread Richard Lynch
On Wed, March 14, 2012 12:09 pm, Ferenc Kovacs wrote: On Mon, Jul 25, 2011 at 12:34 PM, Richard Quadling rquadl...@gmail.comwrote: On 23 July 2011 23:29, Ferenc Kovacs tyr...@gmail.com wrote: I would propose that the defaul values(PHP_INI_ENTRY_*) and the php.ini-production should be keep

Re: [PHP-DEV] set the PHP_INI_ENTRY_* values the same as for php.ini-production

2012-03-14 Thread Ferenc Kovacs
On Mon, Jul 25, 2011 at 12:34 PM, Richard Quadling rquadl...@gmail.comwrote: On 23 July 2011 23:29, Ferenc Kovacs tyr...@gmail.com wrote: hi. We had a discussion about the magic_quotes removal that it is weird that even though that mq was deprecated in 5.3, we still have/had that

Re: [PHP-DEV] set the PHP_INI_ENTRY_* values the same as for php.ini-production

2012-03-14 Thread Rasmus Lerdorf
On 03/14/2012 10:09 AM, Ferenc Kovacs wrote: On Mon, Jul 25, 2011 at 12:34 PM, Richard Quadling rquadl...@gmail.comwrote: Maybe, and this is right of the top of my head, if PHP is installed for a production environment with no INI file, or if an ini file doesn't alter any of the core settings

Re: [PHP-DEV] set the PHP_INI_ENTRY_* values the same as for php.ini-production

2012-03-14 Thread Christopher Jones
On 03/14/2012 10:27 AM, Rasmus Lerdorf wrote: The biggest problem with the concept of virgin PHP settings being geared for production is that by definition that isn't very developer friendly. Keeping the learning curve shallow has always been a goal for PHP which is why things like

Re: [PHP-DEV] set the PHP_INI_ENTRY_* values the same as for php.ini-production

2012-03-14 Thread Kris Craig
I'm curious: What would be the implications of having a third option to display a generic catch-all error instead of a blank page? For example, something like, An error has occurred. Please check your server's error log for details. That would significantly reduce the confusion factor for

Re: [PHP-DEV] set the PHP_INI_ENTRY_* values the same as for php.ini-production

2012-03-14 Thread Ferenc Kovacs
On Wed, Mar 14, 2012 at 6:27 PM, Rasmus Lerdorf ras...@lerdorf.com wrote: On 03/14/2012 10:09 AM, Ferenc Kovacs wrote: On Mon, Jul 25, 2011 at 12:34 PM, Richard Quadling rquadl...@gmail.com wrote: Maybe, and this is right of the top of my head, if PHP is installed for a production

Re: [PHP-DEV] set the PHP_INI_ENTRY_* values the same as for php.ini-production

2011-07-25 Thread Richard Quadling
On 23 July 2011 23:29, Ferenc Kovacs tyr...@gmail.com wrote: hi. We had a discussion about the magic_quotes removal that it is weird that even though that mq was deprecated in 5.3, we still have/had that enabled by default (if you didn't set it from the command line or through a php.ini, the

[PHP-DEV] set the PHP_INI_ENTRY_* values the same as for php.ini-production

2011-07-23 Thread Ferenc Kovacs
hi. We had a discussion about the magic_quotes removal that it is weird that even though that mq was deprecated in 5.3, we still have/had that enabled by default (if you didn't set it from the command line or through a php.ini, the default value which is set from the source by the PHP_INI_ENTRY_*