On Tue, Jul 02, 2002 at 10:17:10AM -0400, Erik Price wrote:
> Except in a production environment, where you really never want your 
> users to see PHP error messages that you haven't coded yourself for the 
> user's benefit.  It could reveal just a bit too much about your setup... 
> even filenames are valuable to maleficants.

Very true.

> I recommend setting your php.ini to E_NONE and then putting 
> error_reporting(E_ALL) at the top of each of your scripts, and then when 
> the file is migrated to production, comment or remove the line.

Dude, that's nuts.  It creates way more work.  Having to put it on each
page in the first place, then having to change it before you put it up.  
Then, there's the possibility that you forget to change it before
uploading.  OUCH!

Set error_reporting to E_ALL in php.ini on the development machine and to
0 in php.ini or .htaccess on the live server.  Set it once on each machine
and you're good.


               PHP classes that make web design easier
        SQL Solution  |   Layout Solution   |  Form Solution
    sqlsolution.info  | layoutsolution.info |  formsolution.info
 T H E   A N A L Y S I S   A N D   S O L U T I O N S   C O M P A N Y
 4015 7 Av #4AJ, Brooklyn NY     v: 718-854-0335     f: 718-854-0409

PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to