How to define error reporting level in php configuration file
How to define the error reporting level in the php configuration file: 1. Open the PHP installation directory, find and open the "php.ini" configuration file; 2. In the configuration file, find the "error_reporting" item, and change the Just set the value to the required error type.
The operating environment of this tutorial: windows7 system, PHP7.1 version, DELL G3 computer
php configuration file definition Methods for reporting error levels
1. Open the PHP installation directory, find and open the php.ini configuration file
2. In the configuration file, find the "error_reporting" item, Just set the value of this item to the required error type.
Error types in PHP are shown in the following table:
Value | Constant | Description |
---|---|---|
1 | E_ERROR | Fatal runtime errors are generally unrecoverable situations, such as problems caused by memory allocation. The consequence is that the script terminates and no longer Keep running. |
2 | E_WARNING | Run-time warning (non-fatal error), only prompt information is given, but the script will not terminate the operation. |
4 | E_PARSE | Compile-time syntax parsing error, generated only by the parser. |
8 | E_NOTICE | Runtime notification, indicating that the script encounters a situation that may appear as an error, but in the script it can run normally There may also be similar notifications. |
16 | E_CORE_ERROR | A fatal error that occurs during PHP initialization startup, similar to E_ERROR, but generated by the PHP engine core. |
32 | E_CORE_WARNING | Warning (non-fatal error) that occurs during PHP initialization startup, similar to E_WARNING, but generated by the PHP engine core of. |
64 | E_COMPILE_ERROR | Fatal compile-time error, similar to E_ERROR, but generated by the Zend scripting engine. |
128 | E_COMPILE_WARNING | Compile-time warning (non-fatal error), similar to E_WARNING, but generated by the Zend scripting engine. |
256 | E_USER_ERROR | The error message generated by the user is similar to E_ERROR, but it is generated by the user using the PHP function trigger_error() in the code. produced. |
512 | E_USER_WARNING | The warning message generated by the user is similar to E_WARNING, but it is generated by the user himself using the PHP function trigger_error() in the code produced. |
1024 | E_USER_NOTICE | The notification information generated by the user is similar to E_NOTICE, but it is generated by the user using the PHP function trigger_error() in the code. produced. |
1024 | E_STRICT | Enable PHP's suggestions for code modifications to ensure the best interoperability and forward compatibility of the code. |
2048 | E_RECOVERABLE_ERROR | A fatal error that can be caught, indicating that a potentially very dangerous error has occurred, but has not caused the PHP engine to be in Unstable state. If the error is not caught by a user-defined handler, it will become an E_ERROR, causing the script to terminate. |
8192 | E_DEPRECATED | Runtime notification, when enabled, will give warnings about code that may not work properly in future versions. |
16384 | E_USER_DEPRECATED | The warning message generated by the user is similar to E_DEPRECATED, but it is generated by the user himself using the PHP function trigger_error() in the code produced. All error and warning messages except |
30719 | E_ALL | E_STRICT. |
You can also use the error_reporting() function in the PHP file to define the error level.
Recommended learning: "PHP Video Tutorial"
The above is the detailed content of How to define error reporting level in php configuration file. 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

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

SublimeText3 Linux new version
SublimeText3 Linux latest version

Dreamweaver Mac version
Visual web development tools

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

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.

SublimeText3 Mac version
God-level code editing software (SublimeText3)