PHP error handling function, php error function_PHP tutorial
Jul 12, 2016 am 08:55 AMPHP error handling function, php error function
In PHP, the default error handling is very simple. An error message is sent to the browser with the file name, line number, and a message describing the error.
PHP error handling
Error handling is an important part when creating scripts and web applications. If your code lacks error detection coding, the program will look unprofessional and open the door to security risks.
This tutorial covers some of the most important error detection methods in PHP.
We will explain different error handling methods for you:
Simple "die()" statement
Custom errors and error triggers
Bug Report
Basic error handling: use die() function
The first example shows a simple script to open a text file:
<?php $file=fopen("welcome.txt","r"); ?>
If the file does not exist, you will get an error like this:
Warning: fopen(welcome.txt) [function.fopen]: failed to open stream:
No such file or directory in C:webfoldertest.php on line 2
To avoid users getting error messages like the one above, we check whether the file exists before accessing it:
<?php if(!file_exists("welcome.txt")) { die("File not found"); } else { $file=fopen("welcome.txt","r"); } ?>
Now, if the file does not exist, you will get an error message like this:
File not found
The above code is more efficient than the previous code because it uses a simple error handling mechanism to terminate the script after an error.
However, simply terminating the script is not always the appropriate approach. Let's examine alternative PHP functions for handling errors.
Create a custom error handler
Creating a custom error handler is very easy. We simply created a dedicated function that can be called when an error occurs in PHP.
The function must be able to handle at least two parameters (error level and error message), but can accept up to five parameters (optional: file, line-number and error context):
Grammar
error_function(error_level,error_message,error_file,error_line,error_context)
Parameters | Description |
---|---|
error_level | Required. Specifies the error reporting level for user-defined errors. Must be a number. See the table below: Error reporting levels. |
error_message | Required. Specifies error messages for user-defined errors. |
error_file | Optional. Specifies the file name where the error occurred. |
error_line | Optional. Specifies the line number where the error occurred. |
error_context | Optional.Specifies an array containing each variable in use when the error occurred and their values. |
錯誤報告級別
這些錯誤報告級別是用戶自定義的錯誤處理程序處理的不同類型的錯誤:
現(xiàn)在,讓我們創(chuàng)建一個處理錯誤的函數(shù):
function customError($errno, $errstr) { echo "<b>Error:</b> [$errno] $errstr<br>"; echo "Ending Script"; die(); }
上面的代碼是一個簡單的錯誤處理函數(shù)。當(dāng)它被觸發(fā)時,它會取得錯誤級別和錯誤消息。然后它會輸出錯誤級別和消息,并終止腳本。
現(xiàn)在,我們已經(jīng)創(chuàng)建了一個錯誤處理函數(shù),我們需要確定在何時觸發(fā)該函數(shù)。
Value | Constant | Description |
---|---|---|
2 | E_WARNING | Non-fatal run-time error. Do not pause script execution. |
8 | E_NOTICE | run-time notification. Occurs when the script finds a possible error, but can also occur when the script is running normally. |
256 | E_USER_ERROR | Fatal user-generated error. This is similar to E_ERROR set by the programmer using the PHP function trigger_error(). |
512 | E_USER_WARNING | Non-fatal user-generated warning. This is similar to the E_WARNING set by the programmer using the PHP function trigger_error(). |
1024 | E_USER_NOTICE | User generated notifications. This is similar to E_NOTICE set by the programmer using the PHP function trigger_error(). |
4096 | E_RECOVERABLE_ERROR | Catchable fatal errors. Like E_ERROR, but can be caught by a user-defined handler. (see set_error_handler()) |
8191 | E_ALL | All errors and warnings. (E_STRICT becomes part of E_ALL in PHP 5.4) |
設(shè)置錯誤處理程序
PHP 的默認(rèn)錯誤處理程序是內(nèi)建的錯誤處理程序。我們打算把上面的函數(shù)改造為腳本運行期間的默認(rèn)錯誤處理程序。
可以修改錯誤處理程序,使其僅應(yīng)用到某些錯誤,這樣腳本就能以不同的方式來處理不同的錯誤。然而,在本例中,我們打算針對所有錯誤來使用我們自定義的錯誤處理程序:
set_error_handler("customError");
由于我們希望我們的自定義函數(shù)能處理所有錯誤,set_error_handler() 僅需要一個參數(shù),可以添加第二個參數(shù)來規(guī)定錯誤級別。
實例
通過嘗試輸出不存在的變量,來測試這個錯誤處理程序:
<?php //error handler function function customError($errno, $errstr) { echo "Error: [$errno] $errstr"; } //set error handler set_error_handler("customError"); //trigger error echo($test); ?>
以上代碼的輸出如下所示:
Error: [8] Undefined variable: test
觸發(fā)錯誤
在腳本中用戶輸入數(shù)據(jù)的位置,當(dāng)用戶的輸入無效時觸發(fā)錯誤是很有用的。在 PHP 中,這個任務(wù)由 trigger_error() 函數(shù)完成。
實例
在本例中,如果 "test" 變量大于 "1",就會發(fā)生錯誤:
<?php $test=2; if ($test>1) { trigger_error("Value must be 1 or below"); } ?>
以上代碼的輸出如下所示:
Notice: Value must be 1 or below
in C:webfoldertest.php on line 6
您可以在腳本中任何位置觸發(fā)錯誤,通過添加的第二個參數(shù),您能夠規(guī)定所觸發(fā)的錯誤級別。
可能的錯誤類型:
E_USER_ERROR - 致命的用戶生成的 run-time 錯誤。錯誤無法恢復(fù)。腳本執(zhí)行被中斷。
E_USER_WARNING - 非致命的用戶生成的 run-time 警告。腳本執(zhí)行不被中斷。
E_USER_NOTICE - 默認(rèn)。用戶生成的 run-time 通知。在腳本發(fā)現(xiàn)可能有錯誤時發(fā)生,但也可能在腳本正常運行時發(fā)生。
在本例中,如果 "test" 變量大于 "1",則發(fā)生 E_USER_WARNING 錯誤。如果發(fā)生了 E_USER_WARNING,我們將使用我們自定義的錯誤處理程序并結(jié)束腳本:
<?php //error handler function function customError($errno, $errstr) { echo "<b>Error:</b> [$errno] $errstr<br>"; echo "Ending Script"; die(); } //set error handler set_error_handler("customError",E_USER_WARNING); //trigger error $test=2; if ($test>1) { trigger_error("Value must be 1 or below",E_USER_WARNING); } ?>
以上代碼的輸出如下所示:
Error: [512] Value must be 1 or below
Ending Script
現(xiàn)在,我們已經(jīng)學(xué)習(xí)了如何創(chuàng)建自己的 error,以及如何觸發(fā)它們,接下來我們研究一下錯誤記錄。
錯誤記錄
在默認(rèn)的情況下,根據(jù)在 php.ini 中的 error_log 配置,PHP 向服務(wù)器的記錄系統(tǒng)或文件發(fā)送錯誤記錄。通過使用 error_log() 函數(shù),您可以向指定的文件或遠(yuǎn)程目的地發(fā)送錯誤記錄。
通過電子郵件向您自己發(fā)送錯誤消息,是一種獲得指定錯誤的通知的好辦法。
通過 E-Mail 發(fā)送錯誤消息
在下面的例子中,如果特定的錯誤發(fā)生,我們將發(fā)送帶有錯誤消息的電子郵件,并結(jié)束腳本:
<?php //error handler function function customError($errno, $errstr) { echo "<b>Error:</b> [$errno] $errstr<br>"; echo "Webmaster has been notified"; error_log("Error: [$errno] $errstr",1, "someone@example.com","From: webmaster@example.com"); } //set error handler set_error_handler("customError",E_USER_WARNING); //trigger error $test=2; if ($test>1) { trigger_error("Value must be 1 or below",E_USER_WARNING); } ?>
以上代碼的輸出如下所示:
Error: [512] Value must be 1 or below
Webmaster has been notified
接收自以上代碼的郵件如下所示:
Error: [512] Value must be 1 or below
這個方法不適合所有的錯誤。常規(guī)錯誤應(yīng)當(dāng)通過使用默認(rèn)的 PHP 記錄系統(tǒng)在服務(wù)器上進(jìn)行記錄。
以上內(nèi)容是小編給大家介紹的PHP錯誤處理函數(shù),希望對大家以上幫助!
您可能感興趣的文章:
- PHP 自定義錯誤處理函數(shù)的使用詳解
- PHP 自定義錯誤處理函數(shù)trigger_error()
- php一些錯誤處理的方法與技巧總結(jié)
- PHP 的異常處理、錯誤的拋出及回調(diào)函數(shù)等面向?qū)ο蟮腻e誤處理方法
- PHP中的錯誤處理、異常處理機制分析
- php 錯誤處理經(jīng)驗分享
- PHP中PDO的錯誤處理
- 使用PHP的錯誤處理

Hot AI Tools

Undress AI Tool
Undress images for free

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

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

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

TostaycurrentwithPHPdevelopmentsandbestpractices,followkeynewssourceslikePHP.netandPHPWeekly,engagewithcommunitiesonforumsandconferences,keeptoolingupdatedandgraduallyadoptnewfeatures,andreadorcontributetoopensourceprojects.First,followreliablesource

PHPbecamepopularforwebdevelopmentduetoitseaseoflearning,seamlessintegrationwithHTML,widespreadhostingsupport,andalargeecosystemincludingframeworkslikeLaravelandCMSplatformslikeWordPress.Itexcelsinhandlingformsubmissions,managingusersessions,interacti

TosettherighttimezoneinPHP,usedate_default_timezone_set()functionatthestartofyourscriptwithavalididentifiersuchas'America/New_York'.1.Usedate_default_timezone_set()beforeanydate/timefunctions.2.Alternatively,configurethephp.inifilebysettingdate.timez

The key to writing clean and easy-to-maintain PHP code lies in clear naming, following standards, reasonable structure, making good use of comments and testability. 1. Use clear variables, functions and class names, such as $userData and calculateTotalPrice(); 2. Follow the PSR-12 standard unified code style; 3. Split the code structure according to responsibilities, and organize it using MVC or Laravel-style catalogs; 4. Avoid noodles-style code and split the logic into small functions with a single responsibility; 5. Add comments at key points and write interface documents to clarify parameters, return values ??and exceptions; 6. Improve testability, adopt dependency injection, reduce global state and static methods. These practices improve code quality, collaboration efficiency and post-maintenance ease.

Yes,youcanrunSQLqueriesusingPHP,andtheprocessinvolveschoosingadatabaseextension,connectingtothedatabase,executingqueriessafely,andclosingconnectionswhendone.Todothis,firstchoosebetweenMySQLiorPDO,withPDObeingmoreflexibleduetosupportingmultipledatabas

PHP page caching improves website performance by reducing server load and speeding up page loading. 1. Basic file cache avoids repeated generation of dynamic content by generating static HTML files and providing services during the validity period; 2. Enable OPcache to compile PHP scripts into bytecode and store them in memory, improving execution efficiency; 3. For dynamic pages with parameters, they should be cached separately according to URL parameters, and avoid cached user-specific content; 4. Lightweight cache libraries such as PHPFastCache can be used to simplify development and support multiple storage drivers. Combining these methods can effectively optimize the caching strategy of PHP projects.

ToquicklytestaPHPcodesnippet,useanonlinePHPsandboxlike3v4l.orgorPHPize.onlineforinstantexecutionwithoutsetup;runcodelocallywithPHPCLIbycreatinga.phpfileandexecutingitviatheterminal;optionallyusephp-rforone-liners;setupalocaldevelopmentenvironmentwith

In PHP, logical operators are used to combine or evaluate conditions, and the main operators include &&, and, ||, or, !, and xor. 1. The difference between && and is in priority. && is higher than the assignment operator, while and is lower than the assignment operator, so the behavior is different when combining assignment; 2.|| and or also have similar priority differences, || takes precedence over assignment, while or is processed after assignment; 3.! operator is used to invert Boolean values, often used to check whether the condition is false, and it is recommended to wrap complex expressions in brackets to ensure correct application; 4.xor returns true only when exactly one of the two values ??is true, suitable for mutex condition judgment
