What to do if a blank page appears on the PHP page_PHP Tutorial

　Bangkejia (www.Bkjia.com) tutorialIn the process of using PHP programs, we often encounter blank pages. The reason why the pages are blank is because the program is running. If you encounter a problem and cannot execute normally, and the PHP environment configuration information prevents the error message returned by PHP from being output to the page, don't panic when you encounter such a problem. Just open the PHP error message and follow the error message prompts to find the cause of the problem. Then work it out step by step.

The following describes how to set the error reporting level of PHP in the program:

We use the error_reporting() function to set the error reporting level of PHP at the beginning of the program running and return the current level.

The following is the quoted content:

以下为引用的内容：
error_reporting(report_level);

error_reporting(report_level);

The following is the quoted content:

以下为引用的内容：
如果参数 level 未指定，当前报错级别将被返回。下面几项是 level 可能的值：值     常量               描述1     E_ERROR     Fatal run-time errors. Errors that can not be recovered from. Execution of the script is halted2     E_WARNING     Non-fatal run-time errors. Execution of the script is not halted4     E_PARSE     Compile-time parse errors. Parse errors should only be generated by the parser8     E_NOTICE     Run-time notices. The script found something that might be an error, but could also happen when running a script normally16     E_CORE_ERROR     Fatal errors at PHP startup. This is like an E_ERROR in the PHP core32     E_CORE_WARNING     Non-fatal errors at PHP startup. This is like an E_WARNING in the PHP core64     E_COMPILE_ERROR     Fatal compile-time errors. This is like an E_ERROR generated by the Zend Scripting Engine128     E_COMPILE_WARNING     Non-fatal compile-time errors. This is like an E_WARNING generated by the Zend Scripting Engine256     E_USER_ERROR     Fatal user-generated error. This is like an E_ERROR set by the programmer using the PHP function trigger_error()512     E_USER_WARNING     Non-fatal user-generated warning. This is like an E_WARNING set by the programmer using the PHP function trigger_error()1024     E_USER_NOTICE     User-generated notice. This is like an E_NOTICE set by the programmer using the PHP function trigger_error()2048     E_STRICT     Run-time notices. PHP suggest changes to your code to help interoperability and compatibility of the code4096     E_RECOVERABLE_ERROR     Catchable fatal error. This is like an E_ERROR but can be caught by a user defined handle (see also set_error_handler())8191     E_ALL     All errors and warnings, except level E_STRICT (E_STRICT will be part of E_ALL as of PHP 6.0)

If the parameter level is not specified, an error is currently reported Level will be returned. The following are possible values ​​for level: Value Constant Description1 E_ERROR Fatal run-time errors. Errors that can not be recovered from. Execution of the script is halted2 E_WARNING Non-fatal run-time errors. Execution of the script is not halted4 E_PARSE Compile-time parse errors. Parse errors should only be generated by the parser8 E_NOTICE Run-time notices. The script found something that might be an error, but could also happen when running a script normally16 E_CORE_ERROR Fatal errors at PHP startup. This is like an E_ERROR in the PHP core32 E_CORE_WARNING Non-fatal errors at PHP startup. This is like an E_WARNING in the PHP core64 E_COMPILE_ERROR Fatal compile-time errors. errors. This is like an E_WARNING generated by the Zend Scripting Engine256 E_USER_ERROR Fatal user-generated error. This is like an E_ERROR set by the programmer using the PHP function trigger_error()512 E_USER_WARNING Non-fatal user-generated warning. This is like an E_WARNING set by the programmer using the PHP function trigger_error()1024 E_USER_NOTICE User-generated notice. This is like an E_NOTICE set by the programmer using the PHP function trigger_error()2048 E_STRICT Run-time notices. PHP suggest changes to your code to help interoperability and compatibility of the code4096 E_RECOVERABLE_ERROR Catchable fatal error. This is like an E_ERROR but can be caught by a user defined handle (see also set_error_handler())8191 E_ALL All errors and warnings, except level E_STRICT (E_STRICT will be part of E_ALL as of PHP 6.0)

Example:

The following is the quoted content:

以下为引用的内容：
任意数目的以上选项都可以用“或”来连接（用 OR 或 |），这样可以报告所有需要的各级别错误。例如，下面的代码关闭了用户自定义的错误和警告，执行了某些操作，然后恢复到原始的报错级别：//禁用错误报告error_reporting(0);//报告运行时错误error_reporting(E_ERROR | E_WARNING | E_PARSE);//报告所有错误error_reporting(E_ALL);?>

Any number of the above options can be used "OR" connections (using OR or |) report all required error levels. For example, the following code turns off user-defined errors and warnings, performs certain operations, and then returns to the original error level: //Disable error reporting error_reporting(0); //Report runtime errors error_reporting(E_ERROR | E_WARNING | E_PARSE);//Report all errors error_reporting(E_ALL);?>

http://www.bkjia.com/PHPjc/364257.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/364257.htmlTechArticleLieHuo.Net tutorial In the process of using PHP programs, we often encounter blank pages. , the page appears blank because the program encounters a problem during operation and cannot execute normally...