@hastxJul 30.2007 — #I usually see them when initializing a variable but there is no value to be passed (ie $x=$_GET['x']; ...but x was never passed), and are usually presented as notices. if you turn off notices you wont see them.
@NogDogJul 30.2007 — #I usually see them when initializing a variable but there is no value to be passed (ie $x=$_GET['x']; ...but x was never passed), and are usually presented as notices. if you turn off notices you wont see them.[/QUOTE]
Don't turn off notices; fix your code, instead. For instance, if your code does...
[code=php] $x = $_GET['x']; [/code]...instead, do... [code=php] $x = ''; if(isset($_GET['x'])) { $x = $_GET['x']; } [/code] Alternatively, you can use a more compact syntax using the ternary ("? :") operator: [code=php] $x = (isset($_GET['x'])) ? $_GET['x'] : ''; [/code] Notices are generated for a reason. All of them can be avoided with properly written code.
@NogDogJul 31.2007 — #I would agree with fixing the code, but it is still a good practice to turn off all error reporting on a production machine.[/QUOTE] Yes, turn off [b]display_errors[/b] for the production system, but you can still leave error_reporting at a high level. Just log the errors to an error log file via the log_errors and error_log configuration settings, instead. (Or, get creative with set_error_handler() and write them to a database. ? )