How to shield php errors by configuring php.ini
This article introduces how to shield PHP errors by configuring the php.ini file for your reference.
Configure relevant content in the php configuration file php.ini to shield related errors in php. As shown below: ; Error handling and logging ; ; Error control and registration; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; Error reporting is bitwise. Or add the numbers together to get the desired error reporting level. ; E_ALL - all errors and warnings ; E_ERROR - fatal runtime error ; E_WARNING - runtime warning (non-fatal error) ; E_PARSE - compile-time parsing error ; E_NOTICE - runtime reminders (these are often caused by bugs in your code, ;It may also be caused by intentional actions. (For example: based on uninitialized variables automatically initialized to a ; the fact that an empty string is used instead of an uninitialized variable) ; E_CORE_ERROR - Fatal error that occurs during PHP initialization during startup ; E_CORE_WARNING - a warning (non-fatal error) that occurs during the initialization process when PHP starts ; E_COMPILE_ERROR - Fatal compile-time error ; E_COMPILE_WARNING - compile-time warning (non-fatal error) ; E_USER_ERROR - user generated error message ; E_USER_WARNING - user generated warning message ; E_USER_NOTICE - user generated reminder message ; example: ; error_reporting = E_ALL & ~E_NOTICE ; Show all errors except reminders ; error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR ; Show errors only error_reporting = E_ALL & ~E_NOTICE ; Show all errors except reminders display_errors = On ; display error messages (as part of the output) ; On the final published web site, it is strongly recommended that you turn off this feature and use ; error log instead (see below). ; It is possible to continue to enable display_errors in the final published website ; Expose some security-related information, such as file paths on your web service, ; Your database plan or other information. display_startup_errors = Off ; Occurs during PHP startup step even when display_erroes is turned on ; errors will not be displayed. ; It is strongly recommended to keep display_startup_errors turned off, ; Except during error correction. log_errors = Off ; Record errors in the log file (server-specific log, stderr standard error output, or error_log (below)) ; As stated above, it is strongly recommended that you log errors on the final published website ; Replaces direct error output. track_errors = Off ; Save the latest error/warning message in variable $php_errormsg (boolean) ;error_prepend_string = ";" ; The string output before the error message ;error_append_string = ";" ; The string output after the error message ;error_log = filename ; Record error log to the specified file ;error_log = syslog ; Record error log in system log syslog (event log under NT, invalid under Windows 95) warn_plus_overloading = Off ; Warn when using '+' for strings Remove this item ; E_WARNING - runtime warning (non-fatal error) |

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

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

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

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

Hot Topics



Alipay PHP...

JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

Article discusses late static binding (LSB) in PHP, introduced in PHP 5.3, allowing runtime resolution of static method calls for more flexible inheritance.Main issue: LSB vs. traditional polymorphism; LSB's practical applications and potential perfo

The application of SOLID principle in PHP development includes: 1. Single responsibility principle (SRP): Each class is responsible for only one function. 2. Open and close principle (OCP): Changes are achieved through extension rather than modification. 3. Lisch's Substitution Principle (LSP): Subclasses can replace base classes without affecting program accuracy. 4. Interface isolation principle (ISP): Use fine-grained interfaces to avoid dependencies and unused methods. 5. Dependency inversion principle (DIP): High and low-level modules rely on abstraction and are implemented through dependency injection.

How to automatically set the permissions of unixsocket after the system restarts. Every time the system restarts, we need to execute the following command to modify the permissions of unixsocket: sudo...

Session hijacking can be achieved through the following steps: 1. Obtain the session ID, 2. Use the session ID, 3. Keep the session active. The methods to prevent session hijacking in PHP include: 1. Use the session_regenerate_id() function to regenerate the session ID, 2. Store session data through the database, 3. Ensure that all session data is transmitted through HTTPS.

Static binding (static::) implements late static binding (LSB) in PHP, allowing calling classes to be referenced in static contexts rather than defining classes. 1) The parsing process is performed at runtime, 2) Look up the call class in the inheritance relationship, 3) It may bring performance overhead.

How to debug CLI mode in PHPStorm? When developing with PHPStorm, sometimes we need to debug PHP in command line interface (CLI) mode...
