PHP Error Handling
Sometimes your application will not run as it supposed to do, resulting in an error. There are a number of reasons that may cause errors, for example:
The Web server might run out of disk space
A user might have entered an invalid value in a form field
The file or database record that you were trying to access may not exist
The application might not have permission to write to a file on the disk
A service that the application needs to access might be temporarily unavailable
These types of errors are known as run-time errors, because they occur at the time the script runs. They are distinct from syntax errors that need to be fixed before the script will run.
A professional application must have the capabilities to handle such run-time error gracefully. Usually this means informing the user about the problem more clearly and precisely.
Understanding Error Levels
Usually, when there's a problem that prevents a script from running properly, the PHP engine triggers an error. Each error is represented by an integer value and an associated constant. The following table list some of the common error levels:
The PHP engine triggers an error whenever it encounters a problem with your script, but you can also trigger errors yourself to generate more user friendly error messages. This way you can make your application more sofisticated. The following section describes some of common methods used for handling errors in PHP:
Basic Error Handling Using the die() Function
<?php // Try to open a non-existent file
$file = fopen("sample.txt", "r");
?>
If the file does not exist you might get an error like this:
Warning: fopen(sample.txt) [function.fopen]: failed to open stream: No such file or directory in C:\wamp\www\project\test.php on line 2
If we follow some simple steps we can prevent the users from getting such error message:
<?php
if(file_exists("sample.txt")){
$file = fopen("sample.txt", "r");
} else{
die("Error: The file you are trying to access doesn't exist.");
}
?>
Now if you run the above script you will get the error message like this: Error: The file you are trying to access doesn't exist.
As you can see by implementing a simple check whether the file exist or not before trying to access it, we can generate an error message that is more meaningful to the user.
The die() function used above simply display the custom error message and terminate the current script if 'sample.txt' file is not found.
Creating a Custom Error Handler
You can create your own error handler function to deal with the run-time error generated by PHP engine. The custom error handler provides you greater flexibility and better control over the errors, it can inspect the error and decide what to do with the error, it might display a message to the user, log the error in a file or database or send by e-mail, attempt to fix the problem and carry on, exit the execution of the script or ignore the error altogether.
The custom error handler function must be able to handle at least two parameters (errno and errstr), however it can optionally accept an additional three parameters (errfile, errline, and errcontext), as described below:
Here's an example of a simple custom error handling function. This handler, customError() is triggered whenever an error occurred, no matter how trivial. It then outputs the details of the error to the browser and stops the execution of the script.
<?php
// Error handler function
function customError($errno, $errstr){
echo "<b>Error:</b> [$errno] $errstr";
}
?>
You need to tell the PHP to use your custom error handler function — just call the built-in set_error_handler() function, passing in the name of the function.
<?php
// Error handler function
function customError($errno, $errstr){
echo "<b>Error:</b> [$errno] $errstr";
}
// Set error handler
set_error_handler("customError");
// Trigger error
echo($test);
?>
Error Logging
Log Error Messages in a Text File
You can also logs details of the error to the log file, like this:
<?php
function calcDivision($dividend, $divisor){
if($divisor == 0){
trigger_error("calcDivision(): The divisor cannot be zero", E_USER_WARNING);
return false;
} else{
return($dividend / $divisor);
}
}
function customError($errno, $errstr, $errfile, $errline, $errcontext){
$message = date("Y-m-d H:i:s - ");
$message .= "Error: [" . $errno ."], " . "$errstr in $errfile on line $errline, ";
$message .= "Variables:" . print_r($errcontext, true) . "\r\n";
error_log($message, 3, "logs/app_errors.log");
die("There was a problem, please try again.");
}
set_error_handler("customError");
echo calcDivision(10, 0);
echo "This will never be printed.";
?>
Trigger an Error
Although the PHP engine triggers an error whenever it encounters a problem with your script, however you can also trigger errors yourself. This can help to make your application more robust, because it can flag potential problems before they turn into serious errors.
To trigger an error from within your script, call the trigger_error() function, passing in the error message that you want to generate:
trigger_error("There was a problem.");
Consider the following function that calculates division of the two numbers.
<?php
function calcDivision($dividend, $divisor){
return($dividend / $divisor);
}
// Calling the function
echo calcDivision(10, 0);
?>
If a value of zero (0) is passed as the $divisor parameter, the error generated by the PHP engine will look something like this: Warning: Division by zero in C:\wamp\www\project\test.php on line 3
This message doesn't look very informative. Consider the following example that uses the trigger_error() function to generate the error.
<?php
function calcDivision($dividend, $divisor){
if($divisor == 0){
trigger_error("The divisor cannot be zero", E_USER_WARNING);
return false;
} else{
return($dividend / $divisor);
}
}
// Calling the function
echo calcDivision(10, 0);
?>
Now the script generates this error message: Warning: The divisor cannot be zero in C:\wamp\www\project\error.php on line 4
As you can see the error message generated by the second example explains the problem more clearly as compared to the previous one.
