Home  >  Article  >  Backend Development  >  Introduction to custom exception handling methods in CodeIgniter3.0+ framework

Introduction to custom exception handling methods in CodeIgniter3.0+ framework

不言
不言forward
2019-03-29 10:33:123393browse

This article brings you an introduction to the custom exception handling method of the CodeIgniter3.0 framework. It has certain reference value. Friends in need can refer to it. I hope it will be helpful to you.

Background: The core code of the ci3.0 framework automatically implements exceptions and implements the corresponding pages and methods thrown. This may not be suitable for some personalized needs, especially interface type applications. Therefore, it is necessary to change the handling of exceptions and 404 and other related exceptions without revising the core code (files in the system directory).

Method Description

CI framework 3.0 has major changes compared to 2.0, one of which is the handling of exceptions. The following is part of the code for exception handling in CodeIgniter-3.1.8\system\core\CodeIgniter.php

/*
 * ------------------------------------------------------
 *  Define a custom error handler so we can log PHP errors
 * ------------------------------------------------------
 */
    set_error_handler('_error_handler');
    set_exception_handler('_exception_handler');
    register_shutdown_function('_shutdown_handler');
...

The methods in the above brackets are all in common.php with function_exists is a prerequisite statement.

...
if ( ! function_exists('_exception_handler'))
{
...

Code implementation

We simply and crudely rewrite the following method in the project entry file index.php

/**
 * 推送到redis 异常队列
 * @time 2019/3/21 15:29
 * @author 
 * @param $msg
 * @return bool|int|string
 */
function redis_list_add($msg)
{
    ini_set('default_socket_timeout', -1);
    $v = explode(':', $_SERVER['SITE_REDIS_SERVER']);
    if (is_array($v) && !empty($v)) {
        try {
            $redis = new redis();
            $redis->pconnect($v[0], $v[1]);
            $trace = $_SERVER['SERVER_NAME'] . " exception\n";
            $trace .= "clint ip is  {$_SERVER['REMOTE_ADDR']} " . ",server is " . $_SERVER['SERVER_NAME'] . "(" . $_SERVER['SERVER_ADDR'] . ")"."\n";
            $trace.= "path is ".(isset($_SERVER['REQUEST_URI'])?$_SERVER['REQUEST_URI']:"empty")."\n";
            $trace .= "request params is =" . print_r($_POST, true);
            return $redis->LPUSH('PHP_ERROR_WARNING', $trace . $msg);
        } catch (Exception $e) {
            return $e->getMessage();
        }
    }
}

/**
 * 优先重写common.php中对应方法
 * @time 2019/3/21 16:19
 * @author 
 * @param $severity
 * @param $message
 * @param $filepath
 * @param $line
 */
function _error_handler($severity, $message, $filepath, $line)
{
    $is_error = (((E_ERROR | E_PARSE | E_COMPILE_ERROR | E_CORE_ERROR | E_USER_ERROR | E_STRICT) & $severity) === $severity);

    if ($is_error) {
        $error_msg = ($message . "\n" . $filepath . "\n" . $line);
        redis_list_add($error_msg);
        exit(json_encode(['success' => '-1', 'code' => 501, 'msg' => 'error']));
    }
}

/**
 * 捕获php本身语法,对象调用,参数类型传递等错误
 * 优先重写common.php中对应方法
 * ParseError,object(Error),TypeError,Error
 * @time 2019/3/20 18:33
 * @author 
 * @param $exception
 */
function _exception_handler($exception)
{
    $_tmp =& load_class('Exceptions', 'core');
    if (!empty($exception)) {
        $error_msg = ($exception->getMessage() . "\n" . $exception->getTraceAsString());
        redis_list_add($error_msg);
        exit(json_encode(['success' => '-1', 'code' => 501, 'msg' => 'exception']));
    }
}

/**
 * 优先重写common.php中对应方法
 * require_once('no_exists.php')
 * @time 2019/3/21 9:49
 * @author 
 */
function _shutdown_handler()
{
    $last_error = error_get_last();
    if (isset($last_error) &&
        ($last_error['type'] & (E_ERROR | E_PARSE | E_CORE_ERROR | E_CORE_WARNING | E_COMPILE_ERROR | E_COMPILE_WARNING))) {
        redis_list_add($msg = $last_error['message'] . "\n" . $last_error['file'] . "\n" . $last_error['line'] . "\n");
        exit(json_encode(['success' => '-1', 'code' => 501, 'msg' => 'shutdown']));
    }
}

/**
 * 优先重写common.php中对应方法
 * ci 框架内部的load异常、config异常、loader异常等会自动抛出,
 * 但common.php中的函数定义之类错误无法捕捉
 * @time 2019/3/20 18:46
 * @author 
 * @param $message
 * @param int $status_code
 */
function show_error($message)
{
    redis_list_add($message);
    exit(json_encode(['success' => '-1', 'code' => '503', 'msg' => 'ci_exception_1']));
}

/**
 * 优先重写common.php中对应方法
 * @time 2019/3/21 15:34
 * @author 
 * @param string $page
 */
function show_404($page = '')
{
    redis_list_add("url: " . $page . " not found");
    exit(json_encode(['success' => '-1', 'code' => '404', 'msg' => 'Not Found']));
}

This article ends here It’s all over. For more other exciting content, you can pay attention to the PHP Video Tutorial column on the PHP Chinese website!

The above is the detailed content of Introduction to custom exception handling methods in CodeIgniter3.0+ framework. For more information, please follow other related articles on the PHP Chinese website!

Statement:
This article is reproduced at:segmentfault.com. If there is any infringement, please contact admin@php.cn delete