4. Error Handling

Eden offers a robust error handling solution which is event driven, offers dynamic messaging and can easily be integrated in your application. To prevent conflicts with other libraries, error handling in Eden by default is turned off. To turn on error handling for both errors and exceptions we follow the example below.

Figure 1. Turn on Custom Error Handling
	->listen('error', 'error')
	->listen('exception', 'error');

In Figure 1, with setReporting(), we first set error reporting to E_ALL because some servers have this PHP setting turned off by default. We next register our event handler using setErrorHandler() and setExceptionHandler() to be called when an error or exception happens. Lastly, we start listening for errors and exceptions with listen and when one is triggered to call error(). Before we can test if this works we need to create an error handler callback called error(). Figure 2 will demonstrate building a quick and easy one.

Figure 2. Make an Error Handler
function error($event, $type, $level, $class, $file, $line, $message) {
	$template = '%s %s from %s in %s on line %s. Eden Says: %s';
	echo sprintf($template, $type, $level, $class, $file, $line, $message);

Now let's purposely invoke a PHP warning as in Figure 3.

Figure 3. Cause an Warning
function warning_in_me() {

PHP WARNING from warning_in_me() in /eden/web/test.php on line 18. Eden Says: Use of undefined constant REDS - assumed 'REDS'

Back Trace

In our last example we made the error output in a user understandable format. Some other things we can do with errors are send emails. create logs, i18n etc., but we will leave that for another tutorial. Sometimes when working with multiple files we'd like to know where the problem started and a history of events leading up to the error. This is where adding a backtrace can help. In Figure 4 we add on history to our error function.

Figure 4. Adding Trace
function error($event, $type, $level, $class, $file, $line, $message, $trace, $offset) {
	$history = array();
	for(; isset($trace[$offset]); $offset++) {
		$row = $trace[$offset];
		//lets formulate the method
		$method = $row['function'].'()';
		if(isset($row['class'])) {
			$method = $row['class'].'->'.$method;
		$rowLine = isset($row['line']) ? $row['line'] : 'N/A';
		$rowFile = isset($row['file']) ? $row['file'] : 'Virtual Call';
		//add to history
		$history[] = array($method, $rowFile, $rowLine);
	echo Eden_Template::i()
		->setData('history', $history)
		->setData('type', $type)
		->setData('level', $level)
		->setData('class', $class)
		->setData('file', $file)
		->setData('line', $line)
		->setData('message', $message)

Eden's error handler actually gives us 10 arguments when an error is triggered. We left $trace and $offset out of Figure 2 because it wasn't important at the time. What we added in our new error() function is a loop that formats each row in our back trace and outputing using Eden_Template instead.

We cover more about Eden_Template in 9. Templating

What we need to know about Eden_Template now is that we are setting PHP variables up using setData() for use in our PHP template file called template.php. Before we can see this in our browser, we first need to create a file called template.php in the same location we are testing error handling (test.php).

Figure 5. Writing the template file (template.php)
	<strong><?php echo $type; ?> <?php echo $level; ?></strong> from 
	<strong><?php echo $class; ?></strong> in 
	<strong><?php echo $file; ?></strong> on line 
	<strong><?php echo $line; ?></strong>
<p><strong>Eden Says:</strong> <?php echo $message; ?></p>
<table width="100%" border="1" cellspacing="0" cellpadding="5">
<?php foreach($history as $row): ?>
	<td><?php echo $row[0]; ?></td>
	<td><?php echo $row[1]; ?>(<?php echo $row[2]; ?>)</td>
<?php endforeach; ?>

Now when we load up test.php up on our browser we get something similar to the following.

PHP WARNING from warning_in_me() in /eden/web/test.php on line 41

Eden Says: Use of undefined constant REDS - assumed 'REDS'



Exception handing in Eden is about the same process as setting up errors shown in Figure 1. We leave the responsibility of explaining custom errors to you. A basic example of triggering errors in an Eden class is shown in Figure 6.

Figure 6. Exceptions
class Exception_In_Me extends Eden_Class {
	public static function i() {
		return self::_getMultiple(__CLASS__);
	public function doSomething() {
		Eden_Error::i('You triggered an Exception.')->trigger();

You shouldn't use throw as in throw new Eden_Error() or throw Eden_Error::i() because the back trace will give you more details than you need and looks like a false positive.

If you load this in your browser you should see something like below.

LOGIC ERROR from Eden_Error in /eden/web/test.php on line 47

Eden Says: You triggered an Exception.

Exception_In_Me->doSomething() /eden/web/test.php(51)

In Eden, we introduce more settings to error handling to help categorize errors and the ability to handle different scenarios. The example below shows different settings depending on the kind of error we want to trigger.

Figure 7. Custom Errors
class Exception_In_Me extends Eden_Class {
	public static function i() {
		return self::_getMultiple(__CLASS__);
	public function doSomething() {
	public function doSomethingElse() {
			->setMessage('%s, you triggered an Exception!')


TESTING EXTREME from Eden_Error in /eden/web/test.php on line 56

Eden Says: Chris, you triggered an Exception!

Exception_In_Me->doSomethingElse() /eden/web/test.php(47)
Exception_In_Me->doSomething() /eden/web/test.php(60)

In the example above we set the message into a string template, added a variable called Chris set the type to TESTING and the error level to EXTREME.

You can set the error level and error type to anything you want.


One final use of Eden_Error is its ability to test method arguments across different data types. This area seems to be lacking in PHP in general, but it's good practice to first validate arguments passed into a method before using them. Figure 8 shows all the data types you can test for.

Figure 8. Arguments Testing
class Exception_In_Me extends Eden_Class {
	public static function i() {
		return self::_getMultiple(__CLASS__);
	public function doSomething($string, $int, $float, $number, $bool, $null, $stringOrNull, $array, $object, $session) {
			->argument(1, 'string')
			->argument(2, 'int')
			->argument(3, 'float')
			->argument(4, 'number', 'numeric')
			->argument(5, 'bool')
			->argument(6, 'null')
			->argument(7, 'string', 'null')
			->argument(8, 'array')
			->argument(9, 'object')
			->argument(10, 'Eden_Session');
		echo 'Passed the argument test!';

eden()->Exception_In_Me()->doSomething('Chris', 29, 186.5, '6', false, NULL, 'CEO', array(), new stdClass(), Eden_Session::i());

If you invalidate any of the passing arguments you will see something like the following.

eden()->Exception_In_Me()->doSomething('Chris', 29, 186.5, '6', false, NULL, 85.5, array(), new stdClass(), Eden_Session::i());

CRITICAL ERROR from Eden_Error in /eden/web/test.php on line 54

Eden Says: Argument 7 in Exception_In_Me->doSomething() was expecting string or null, however 85.5 was given.

Eden_Error->argument() /eden/web/test.php(54)
Exception_In_Me->doSomething() /eden/web/test.php(63)


By now you should understand all the advantages with an error handler like Eden's. With Eden as a whole, not only are we making simplier code but, we can also control how strict our applications can be (in other words "idiot proofing"). We seen how powerful and flexible an event driven design can be with error handling. Let's talk further about events in our next section, 5. Event Driven.

© 2012 Openovate Labs. All rights reserved.