php Common error levels: 1. E_ERROR; 2. E_WARNING; 3. E_PARSE; 4. E_NOTICE; 5. E_USER_ERROR; 6. E_USER_WARNING; 7. E_USER_NOTICE; 8. E_STRICT; 9. E_ALL.
The operating environment of this tutorial: windows7 system, PHP7.1 version, DELL G3 computer
The error levels in php are:
1 |
E_ERROR (integer)
| Fatal runtime error. This type of error is generally an unrecoverable situation, such as a problem caused by memory allocation. The consequence is that the script terminates and does not continue to run. | |
##2 | ##E_WARNING (integer)Run-time warning (non-fatal error). Only a prompt message is given, but the script does not terminate. |
||
##E_PARSE |
(integer) Compile-time syntax parsing error. Parsing errors are generated only by the parser.
|
##8 |
|
##E_NOTICE | (integer)
Runtime notification. Indicates that the script encounters a situation that may appear as an error, but there may also be similar notifications in scripts that can run normally.
|
||
16 |
E_CORE_ERROR (integer) |
Initialize in PHP A fatal error occurred during startup. This error is similar to E_ERROR , but is generated by the PHP engine core. |
since PHP 4 |
##E_CORE_WARNING( integer) Warning (non-fatal error) that occurred during PHP initialization startup. Similar to |
E_WARNING, but generated by the PHP engine core. since PHP 4 |
##64 | |
##E_COMPILE_ERROR | (integer) Fatal compile-time error. Similar to E_ERROR |
, but generated by the Zend script engine. since PHP 4
| ##128|
( | integer) Compile-time warning (non-fatal error). Similar to E_WARNING, but generated by the Zend script engine. |
since PHP 4 ##256
|
##E_USER_ERROR |
) | Error messages generated by users. Similar to E_ERROR , but it is generated by the user using the PHP function trigger_error() in the code. |
since PHP 4 | |
##E_USER_WARNING( integer) Warning messages generated by users. Similar to |
E_WARNING, but it is generated by the user using the PHP function trigger_error() in the code. since PHP 4 |
##1024 | |
##E_USER_NOTICE | (integer) Notification information generated by users. Similar to E_NOTICE |
, but it is generated by the user using the PHP function trigger_error() in the code. since PHP 4
|
##2048 |
E_STRICT | (integer) Enable PHP's suggestions for code modifications to ensure the best interoperability and forward compatibility of the code. since PHP 5
|
##4096 | ##E_RECOVERABLE_ERROR |
integer | )
Fatal errors that can be caught. It indicates that a potentially dangerous error has occurred, but has not caused the PHP engine to become unstable. If the error is not caught by a user-defined handler, it will become an E_ERROR and the script will terminate.
| since PHP 5.2.0 ##8192 |
##E_DEPRECATED |
(integer) | Runtime notification. When enabled, a warning will be given about code that may not work properly in future versions.since PHP 5.3.0 | ||
E_USER_DEPRECATED (integer)
| User generated warning message. Similar to
E_DEPRECATED , but it is generated by the user using the PHP function trigger_error() in the code.
| since PHP 5.3.0||
30719 | ##E_ALL (integer)
|
E_STRICTAll error and warning messages that go out. 30719 in PHP 5.3.x, 6143 in PHP 5.2.x, 2047 previously |
- E_ERROR
: Fatal runtime error (it prevents the execution of the script)
- E_WARNING
: Runtime warning (non-fatal error)
##E_PARSE - : Parse error
##E_NOTICE : Note (things may or may not be a problem) -
E_USER_ERROR : User generated error message, generated by the trigger_error() function -
E_USER_WARNING : User-generated warning, generated by the trigger_error() function -
E_USER_NOTICE : User-generated note , generated by the trigger_error() function -
E_STRICT : Recommendations on compatibility and interoperability -
E_ALL : All errors, warnings and suggestions -
How to set the error reporting level:
1. Modify the PHP configuration File php.iniAfter setting error_reporting in this way, restart the web server and it will take effect permanently.
Open the configuration file php.ini and check the default value of error reporting level error_reporting, as follows:error_reporting=E_ALL & ~E_DEPRECATED & ~E_STRICT1.It means to report all errors, except E_DEPRECATED and E_STRICT.
Modify it to:
error_reporting=E_ALL & ~E_NOTICE1.It means reporting all errors except E_NOTICE. This is also the most commonly used error reporting level. It will not report errors of the attention class (such as using an undefined variable).
Save and take effect after restarting the web server.
After setting in this way, it can take effect immediately. But only in the area behind the error_reporting() function call in the current script.
int error_reporting ([ int $level ] )1.
The parameter can be an integer or the corresponding constant identifier. It is recommended to use the constant form. The return value is the value (integer value) of the error reporting level in effect at the current location.
Note: The default value of display_errors in the configuration file php.ini is On, which means error prompts are displayed. If set to Off, all error prompts will be turned off.
Use error_reporting(0) or add @ in front of the function to suppress error output to prevent error messages from leaking sensitive information.
Recommended learning: "
PHP Video Tutorial"
The above is the detailed content of What are the common error levels in PHP?. For more information, please follow other related articles on the PHP Chinese website!

The article compares ACID and BASE database models, detailing their characteristics and appropriate use cases. ACID prioritizes data integrity and consistency, suitable for financial and e-commerce applications, while BASE focuses on availability and

The article discusses securing PHP file uploads to prevent vulnerabilities like code injection. It focuses on file type validation, secure storage, and error handling to enhance application security.

Article discusses best practices for PHP input validation to enhance security, focusing on techniques like using built-in functions, whitelist approach, and server-side validation.

The article discusses strategies for implementing API rate limiting in PHP, including algorithms like Token Bucket and Leaky Bucket, and using libraries like symfony/rate-limiter. It also covers monitoring, dynamically adjusting rate limits, and hand

The article discusses the benefits of using password_hash and password_verify in PHP for securing passwords. The main argument is that these functions enhance password protection through automatic salt generation, strong hashing algorithms, and secur

The article discusses OWASP Top 10 vulnerabilities in PHP and mitigation strategies. Key issues include injection, broken authentication, and XSS, with recommended tools for monitoring and securing PHP applications.

The article discusses strategies to prevent XSS attacks in PHP, focusing on input sanitization, output encoding, and using security-enhancing libraries and frameworks.

The article discusses the use of interfaces and abstract classes in PHP, focusing on when to use each. Interfaces define a contract without implementation, suitable for unrelated classes and multiple inheritance. Abstract classes provide common funct


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

VSCode Windows 64-bit Download
A free and powerful IDE editor launched by Microsoft

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.