Solved

Using Custom PHP Error Handler, but Parse and Fatal errors are not passed through the handler

Posted on 2007-11-19
6
890 Views
Last Modified: 2008-10-10
Hi.

I'm running a custom PHP error handler on my site which so far detects all errors, except for parse and fatal errors.

I've accidently added a '>' to a PHP file after the '<?' which has generated a parse error.

What do I need to do to force all parse and fatal errors through the error handler?

Any example code would be greatly appreciated. Thanks in advance.
<?php

	ob_start();

	function ErrorHandler($errno, $errstr, $errfile, $errline) {

		ob_clean();

		include("errors/errorhandler.php"); exit();

		ob_get_clean();

	}

	set_error_handler("ErrorHandler", E_ALL^E_NOTICE);

?>

Open in new window

0
Comment
Question by:DReade83
  • 2
6 Comments
 
LVL 20

Expert Comment

by:steelseth12
ID: 20314182
error_reporting(0);
0
 

Author Comment

by:DReade83
ID: 20314209
That doesn't work - all it does is gives me a white screen. The custom error handler still doesn't run.

Could you be a little more specific where that line needs to go please?
0
 
LVL 20

Accepted Solution

by:
steelseth12 earned 250 total points
ID: 20314276
after doing some testing you have to set it in the php.ini to disable error reporting on parse & fatal errors.

error_reporting  = ~E_ALL

And even then according to php.net although errors are not longer display you can not catch them

http://www.php.net/manual/en/function.set-error-handler.php
0
 
LVL 1

Assisted Solution

by:itsbth
itsbth earned 250 total points
ID: 20315399
It is impossible to catch fatal and parse errors, as fatal, as the suggests, is impossible to recover from and parse errors are happens before any of the code actually runs, so the handler is never registered.

From the PHP manual (http://php.net/manual/en/function.set-error-handler.php):  "The following error types cannot be handled with a user defined function: E_ERROR, E_PARSE, E_CORE_ERROR, E_CORE_WARNING, E_COMPILE_ERROR, E_COMPILE_WARNING, and most of E_STRICT raised in the file where set_error_handler() is called.

If errors occur before the script is executed (e.g. on file uploads) the custom error handler cannot be called since it is not registered at that time."
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Deprecated and Headed for the Dustbin By now, you have probably heard that some PHP features, while convenient, can also cause PHP security problems.  This article discusses one of those, called register_globals.  It is a thing you do not want.  …
Nothing in an HTTP request can be trusted, including HTTP headers and form data.  A form token is a tool that can be used to guard against request forgeries (CSRF).  This article shows an improved approach to form tokens, making it more difficult to…
Learn how to match and substitute tagged data using PHP regular expressions. Demonstrated on Windows 7, but also applies to other operating systems. Demonstrated technique applies to PHP (all versions) and Firefox, but very similar techniques will w…
The viewer will learn how to dynamically set the form action using jQuery.

759 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now