O Guia Definitivo do Yii 1.1

eturn array(
......
'components'=>array(
'errorHandler'=>array(
'errorAction'=>'site/error',
),
),
);
In the above, we configure the CErrorHandler::errorAction property to be the route site/
error which refers to the error action in SiteController. We may use a different route if
needed.
We can write the error action like the following:
public function actionError()
{
if($error=Yii::app()->errorHandler->error)
$this->render('error', $error);
}
In the action, we first retrieve the detailed error information from CErrorHandler::error. If it
is not empty, we render the error view together with the error information. The error
information returned from CErrorHandler::error is an array with the following fields:
• code: the HTTP status code (e.g. 403, 500);
• type: the error type (e.g. CHttpException, PHP Error);
• message: the error message;
• file: the name of the PHP script file where the error occurs;
• line: the line number of the code where the error occurs;
• trace: the call stack of the error;
• source: the context source code where the error occurs.
Tip: The reason we check if CErrorHandler::error is empty or not is because the error
action may be directly requested by an end user, in which case there is no error. Since
we are passing the$error array to the view, it will be automatically expanded to
individual variables. As a result, in the view we can access directly the variables such
as $code, $type.
Message Logging
A message of level error will always be logged when an error occurs. If the error is caused
by a PHP warning or notice, the message will be logged with category php; if the error is
caused by an uncaught exception, the category would be exception.ExceptionClassName
(for CHttpException its statusCode will also be appended to the category). One can thus
exploit the logging feature to monitor errors happened during application execution.