HTML_CSS : The Definitive Guide
HTML_CSS : The Definitive Guide
|
There are many scenarios in which fine-grained control over error raising is absolutely necessary.
The first level to control error generation is the
php.ini directives display_errors and
log_errors. When these directives are set to
TRUE, then browser and file outputs are effective.
![[Tip]](img/admons/tip.png) |
Tip |
|---|---|
If you want to ignore all errors raised (no display, no logs) and avoid to include PEAR core class, then you should have something like :
<?php
require_once 'HTML/CSS.php';
function myErrorHandler()
{
return null;
}
$errorConf = array('error_handler' => 'myErrorHandler');
$css = new HTML_CSS(null, $errorConf);
// ...
?>
|
With push_callback option, you can decides to stop script execution (as done with exceptions by default: returns
PEAR_ERROR_DIE constant), or continue without filtering (returns
NULL).
If you want to write your own callback function for the push_callback option, this one should have two arguments: first one will get the error code, and second will get error level. These are all the necessary informations to do a filtering. Example that follow show how to be aware that a script use wrong argument data type.
<?php
require_once 'HTML/CSS.php';
function myErrorFilter($code, $level)
{
if ($code === HTML_CSS_ERROR_INVALID_INPUT) {
error_log('script: '.__FILE__.' used wrong argument data type', 1, 'admin@yoursite.com');
}
return null;
}
$errorConf = array('push_callback' => 'myErrorFilter');
$css = new HTML_CSS(null, $errorConf);
// ...
?>
| HTML_CSS : The Definitive Guide | v 1.0.0 : June 24, 2006 |