Home > Article > Backend Development > How to block error prompts in php
Method: 1. Use the error control operator "@" and place it in front of a PHP expression, and any error messages that may be generated will be ignored. 2. Use the error_reporting() function; 3. In the "php.ini" file, set the value of the "display_errors" item to "Off".
The operating environment of this tutorial: windows7 system, PHP7.1 version, DELL G3 computer
There are 3 types of PHP Methods to mask errors:
Use error control operators: @
Use error_reporting () Function to mask errors
Mask errors through the display_errors parameter
1. Use the error control operator: @
PHP supports using the error control operator @
. Place it before a PHP expression and any error messages the expression may produce will be ignored.
If you set a custom error handling function with set_error_handler(), this error handling function will still be called, and if @
is used before the error statement, the error handling function will return 0.
It should be noted that the @
operator is only valid for expressions. Simply put, if you can get a value from somewhere, you can add the @
operator in front of it. For example, the @
operator can be used before variables, functions, include calls, constants, etc., but it cannot be placed before the definition of a function or class, nor can it be used in conditional structures such as if and foreach statements. forward. The
@
operator is also effective for serious errors that can cause the program to terminate. This means that if @ is used before a function call that does not exist or has the wrong letter, it is suppressed. error message, then the program will die there without any prompt.
[Example] Use the @
error control operator to mask errors in the code.
<?php $link = @mysqli_connect("127.0.0.1", "my_user", "my_password", "my_db") or die('数据库连接失败!'); ?>
The running results are as follows:
数据库连接失败!
2. Use the error_reporting()
function to shield errors
PHP has many error levels , use the error_reporting() function to set what kind of errors PHP will report. The syntax format of the function is as follows:
error_reporting([int $level])
The parameter $level is to set the error level. If $level is set to 0, all PHP errors will be closed. Report; if set to -1, all error reports will be returned.
The error types in PHP are as shown in the following table:
值 | 常量 | 说明 |
---|---|---|
1 | E_ERROR | 致命的运行时错误,一般是不可恢复的情况,例如内存分配导致的问题,后果是导致脚本终止、不再继续运行。 |
2 | E_WARNING | 运行时警告(非致命错误),仅给出提示信息,但是脚本不会终止运行。 |
4 | E_PARSE | 编译时语法解析错误,仅由分析器产生。 |
8 | E_NOTICE | 运行时通知,表示脚本遇到可能会表现为错误的情况,但是在可以正常运行的脚本里面也可能会有类似的通知。 |
16 | E_CORE_ERROR | 在 PHP 初始化启动过程中发生的致命错误,类似 E_ERROR,但是是由 PHP 引擎核心产生的。 |
32 | E_CORE_WARNING | PHP 初始化启动过程中发生的警告(非致命错误),类似 E_WARNING ,但是是由 PHP 引擎核心产生的。 |
64 | E_COMPILE_ERROR | 致命编译时错误,类似 E_ERROR,但是是由 Zend 脚本引擎产生的。 |
128 | E_COMPILE_WARNING | 编译时警告(非致命错误),类似 E_WARNING,但是是由 Zend 脚本引擎产生的。 |
256 | E_USER_ERROR | 用户产生的错误信息,类似 E_ERROR,但是是由用户自己在代码中使用 PHP 函数 trigger_error() 来产生的。 |
512 | E_USER_WARNING | 用户产生的警告信息,类似 E_WARNING,但是是由用户自己在代码中使用 PHP 函数 trigger_error() 来产生的。 |
1024 | E_USER_NOTICE | 用户产生的通知信息,类似 E_NOTICE,但是是由用户自己在代码中使用 PHP 函数 trigger_error() 来产生的。 |
1024 | E_STRICT | 启用 PHP 对代码的修改建议,以确保代码具有最佳的互操作性和向前兼容性。 |
2048 | E_RECOVERABLE_ERROR | 可被捕捉的致命错误,表示发生了一个可能非常危险的错误,但是还没有导致 PHP 引擎处于不稳定的状态。如果该错误没有被用户自定义句柄捕获,将成为一个 E_ERROR,从而使脚本终止运行。 |
8192 | E_DEPRECATED | 运行时通知,启用后将会对在未来版本中可能无法正常工作的代码给出警告。 |
16384 | E_USER_DEPRECATED | 用户产生的警告信息,类似 E_DEPRECATED,但是是由用户自己在代码中使用 PHP 函数 trigger_error() 来产生的。 |
30719 | E_ALL | E_STRICT 除外的所有错误和警告信息。 |
【示例】使用 error_reporting() 函数屏蔽代码中的错误。
<?php error_reporting(0); $link = mysqli_connect("127.0.0.1", "my_user", "my_password", "my_db") or die('数据库连接失败!'); ?>
3、通过 display_errors
参数屏蔽错误
这种方法应该是最彻底的一种解决办法,因为前两种方法只能作用于单行或者单个文件,而这个则是作用于所有的 PHP 文件。
具体的操作方法就是,打开 php.ini 配置文件,在其中搜索 display_errors,然后将 display_errors 的值设置为 Off 即可关闭所有的 PHP 错误报告。如下所示:
; This directive controls whether or not and where PHP will output errors, ; notices and warnings too. Error output is very useful during development, but ; it could be very dangerous in production environments. Depending on the code ; which is triggering the error, sensitive information could potentially leak ; out of your application such as database usernames and passwords or worse. ; For production environments, we recommend logging errors rather than ; sending them to STDOUT. ; Possible Values: ; Off = Do not display any errors ; stderr = Display errors to STDERR (affects only CGI/CLI binaries!) ; On or stdout = Display errors to STDOUT ; Default Value: On ; Development Value: On ; Production Value: Off ; http://php.net/display-errors display_errors = Off
推荐学习:《PHP视频教程》
The above is the detailed content of How to block error prompts in php. For more information, please follow other related articles on the PHP Chinese website!