Display handler - part 6.

Introduction

This example requires :

• PEAR::HTML_Progress 1.2.0 or better.
• PEAR.

This example will show you how to customize display errors renderers.

An error was volontary made on call of setAnimSpeed method (lines 41 and 56). We have decided to ignore API exception (lines 4 thru 10 and 30), and use our own error handler rather than PEAR_Error (lines 11 thru 29 and 31). Display handler renderer was changed on lines 33 thru 37. So only lines 62 to 65 will be executed to catch HTML_Progress error.

display_errors

Print out errors (as a part of the output). For production web sites, you're strongly encouraged to turn this feature off, and use error logging instead. Keeping display_errors enabled on a production web site may reveal security information to end users, such as file paths on your Web server, your database schema or other information.

log_errors

Log errors into a log file (server-specific log, stderr, syslog ...) As stated above, you're strongly advised to use error logging in place of error displaying on production web sites.

 Render options

Default options below are used :

• message_callback : callback HTML_Progress::_msgCallback()
• context_callback : callback HTML_Progress::_getBacktrace()

Only option changed is :

• push_callback : callback _pushCallback() [ignore if error is an exception]
• error_handler : callback _errorHandler() [do not use PEAR_Error]
• handler/display/conf/lineFormat : '<b>%1$s</b>: %2$s <hr>%3$s'
• handler/display/conf/contextFormat : '<b>Function</b>: %3$s<br/><b>File</b>: %1$s<br/><b>Line</b>: %2$s<br/>'

• 1$ = error level
• 2$ = message body
• 3$ = error context (class/method/file/line)

• 1$ = filename
• 2$ = line number
• 3$ = class and method names

 Output

Error: invalid input, parameter #1 "$delay" was expecting "less or equal 1000", instead got "10000"

 PHP source syntax highlight