How can I get useful error messages in PHP

Question

Quite often I will try and run a PHP script and just get a blank screen back  No error message  just an empty screen  The cause might have been a simple syntax error  wrong bracket  missing semicolon   or a failed function call  or something else entirely   It is very difficult to figure out what went wrong  I end up commenting out code  entering  echo  statements everywhere  etc  trying to narrow down the problem  But there surely must be a better way  right   Is there a way to get PHP to produce a useful error message  like Java does

User · Answer

I have also seen such errors when the fastcgi params or fastcgi conf config file is not properly included in the server configuration  So the fix for me was a silly    include  etc nginx fastcgi params    Took me an hour to find that out

User · Answer

PHP Configuration  2 entries in php ini dictate the output of errors    display errors error reporting   In production  display errors is usually set to Off  Which is a good thing  because error display in production sites is generally not desirable     However  in development  it should be set to On  so that errors get displayed  Check   error reporting  as of PHP 5 3  is set by default to E ALL  amp   E NOTICE  amp   E STRICT  amp   E DEPRECATED  meaning  everything is shown except for notices  strict standards and deprecation notices   When in doubt  set it to E ALL to display all the errors  Check   Whoa whoa  No check  I can t change my php ini   That s a shame  Usually shared hosts do not allow the alteration of their php ini file  and so  that option is sadly unavailable  But fear not  We have other options   Runtime configuration  In the desired script  we can alter the php ini entries in runtime  Meaning  it ll run when the script runs  Sweet   error reporting E ALL   ini set  display errors    On     These two lines will do the same effect as altering the php ini entries as above  Awesome   I still get a blank page 500 error   That means that the script hadn t even run  That usually happens when you have a syntax error   With syntax errors  the script doesn t even get to runtime  It fails at compile time  meaning that it ll use the values in php ini  which if you hadn t changed  may not allow the display of errors   Error logs  In addition  PHP by default logs errors  In shared hosting  it may be in a dedicated folder or on the same folder as the offending script   If you have access to php ini  you can find it under the error log entry

User · Answer

I m always using this syntax at the very top of the php script   ini set  error reporting   E ALL   ini set  display errors    On       On or Off

User · Answer

I recommend Nette Tracy for better visualization of errors and exceptions in PHP

User · Answer

You might also want to try PHPStorm as your code editor   It will find many PHP and other syntax errors right as you are typing in the editor

User · Answer

There is a really useful extension called  xdebug  that will make your reports much nicer as well

User · Answer

On the top of the page choose a parameter   error reporting E ERROR   E WARNING   E PARSE

User · Answer

The following enables all errors   ini set  display startup errors   1   ini set  display errors   1   error reporting -1     Also see the following links   http   php net manual en errorfunc configuration php ini display-errors http   php net manual en errorfunc configuration php ini display-startup-errors http   php net manual en function error-reporting php

User · Answer

If the error is in PHP code  you can use error reporting   function within your code to set to the report all    However  this does not handle the situation when PHP crashes  Information about that is only available in server logs  Maybe you don t have access to those  but many hosting providers I ve worked with have some way to let you access it  For example  the approach I like best is that it creates the error log file in the current directory where  php resides  Try searching there or contact your hosting provider about this

User · Answer

You can enable full error reporting  including notices and strict messages   Some people find this too verbose  but it s worth a try  Set error reporting to E ALL   E STRICT in your php ini   error reporting   E ALL   E STRICT   E STRICT will notify you about deprecated functions and give you recommendations about the best methods to do certain tasks   If you don t want notices  but you find other message types helpful  try excluding notices   error reporting    E ALL   E STRICT   amp   E NOTICE   Also make sure that display errors is enabled in php ini  If your PHP version is older than 5 2 4  set it to On   display errors    On    If your version is 5 2 4 or newer  use   display errors    stderr

User · Answer

I fixed my entire 500 problem like this  A  Check php ini parameters  php ini  gt  gt  error reporting   E ALL   E STRICT php ini  gt  gt  display errors   On php ini  gt  gt  display startup errors   Off  B  Update IIS manager parameters  IIS Manager  gt  gt  Error Pages  gt  gt  500  gt  gt  Edit feature settings  gt  gt  detailed errors  in this step  you get 500 errors like this and with no html loading    IIS Manager  gt  gt  FastCGI Settings  gt  gt  php-cgi exe  gt  gt  standard error mode  gt  gt  IgnoreAndReurn200  in this step  you can see html page including php errors like this   AND DONE

User · Answer

To turn on full error reporting  add this to your script   error reporting E ALL     This causes even minimal warnings to show up  And  just in case   ini set  display errors    1      Will force the display of errors  This should be turned off in production servers  but not when you re developing

User · Answer

using  inexistent function call    in your code will cause the intepreter to quietly die and abort the script parsing  You should check for invalid functions and try not to use the error-supressing operator the   char

User · Answer

Aside from error reporting and the display errors ini setting  you can get SYNTAX errors from your web server s log files  When I m developing PHP I load my development system s web server logs into my editor  Whenever I test a page and get a blank screen  the log file goes stale and my editor asks if I want to reload it  When I do  I jump to the bottom and there is the syntax error  For example    Sun Apr 19 19 09 11 2009   error   client 127 0 0 1  PHP Parse error   syntax error  unexpected T ENCAPSED AND WHITESPACE  expecting T STRING or T VARIABLE or T NUM STRING in D   webroot  test  test php on line 9

User · Answer

You can include the following lines in the file you want to debug   error reporting E ALL   ini set  display errors    1      This overrides the default settings in php ini  which just make PHP report the errors to the log

User · Answer

You can also run the file in the Terminal  command line  like so  php -f filename php   This runs your code and gives you the same output in case of any errors that you d see in the error log  It mentions the error and the line number

User · Answer

FirePHP can be useful as well

User · Answer

For syntax errors  you need to enable error display in the php ini  By default these are turned off because you don t want a  customer  seeing the error messages  Check this page in the PHP documentation for information on the 2 directives  error reporting and display errors  display errors is probably the one you want to change  If you can t modify the php ini  you can also add the following lines to an  htaccess file   php flag  display errors        on php value error reporting       2039   You may want to consider using the value of E ALL  as mentioned by Gumbo  for your version of PHP for error reporting to get all of the errors  more info  3 other items   1  You can check the error log file as it will have all of the errors  unless logging has been disabled    2  Adding the following 2 lines will help you debug errors that are not syntax errors   error reporting -1   ini set  display errors    On       3  Another option is to use an editor that checks for errors when you type  such as PhpEd  PhpEd also comes with a debugger which can provide more detailed information   The PhpEd debugger is very similar to xdebug and integrates directly into the editor so you use 1 program to do everything    Cartman s link is also very good  http   www ibm com developerworks library os-debug

User · Answer

ini set  display errors   1   ini set  display startup errors   1   error reporting E ALL

User · Answer

open your php ini   make sure it s set to   display errors   On   restart your server

User · Answer

In addition to all the wonderful answers here  I d like to throw in a special mention for the MySQLi and PDO libraries   In order to      Always see database related errors  and Avoid checking the return types for methods to see if something went wrong   The best option is to configure the libraries to throw exceptions   MySQLi  Add this near the top of your script  mysqli report MYSQLI REPORT ERROR   MYSQLI REPORT STRICT     This is best placed before you use new mysqli   or mysqli connect     PDO  Set the PDO  ATTR ERRMODE attribute to PDO  ERRMODE EXCEPTION on your connection instance  You can either do this in the constructor   pdo   new PDO  driver host localhost        username    password         PDO  ATTR ERRMODE   gt  PDO  ERRMODE EXCEPTION       or after creation   pdo- gt setAttribute PDO  ATTR ERRMODE  PDO  ERRMODE EXCEPTION

User · Answer

For those who use nginx and have a white screen even for file with  lt  php echo 123   In my case I didn t have this required option for PHP in nginx config file   fastcgi param SCRIPT FILENAME  document root fastcgi script name    This option wasn t in fastcgi params file  so PHP didn t work and there wasn t any errors in logs

User · Answer

For quick  hands-on troubleshooting I normally suggest here on SO   error reporting  0   ini set  display errors   1     to be put at the beginning of the script that is under trouble-shooting  This is not perfect  the perfect variant is that you also enable that in the php ini and that you log the errors in PHP to catch syntax and startup errors   The settings outlined here display all errors  notices and warnings  including strict ones  regardless which PHP version   Next things to consider    Install Xdebug and enable remote-debugging with your IDE    See as well    Error Reporting  PHP The Right Way   Predefined ConstantsDocs error reporting  Docs display errorsDocs

User · Answer

PHP Error Handling  Sometimes your application will not run as it supposed to do  resulting in an error  There are a number of reasons that may cause errors  for example   The Web server might run out of disk space A user might have entered an invalid value in a form field The file or database record that you were trying to access may not exist The application might not have permission to write to a file on the disk A service that the application needs to access might be temporarily unavailable These types of errors are known as run-time errors  because they occur at the time the script runs  They are distinct from syntax errors that need to be fixed before the script will run   A professional application must have the capabilities to handle such run-time error gracefully  Usually this means informing the user about the problem more clearly and precisely   Understanding Error Levels  Usually  when there s a problem that prevents a script from running properly  the PHP engine triggers an error  Each error is represented by an integer value and an associated constant  The following table list some of the common error levels     The PHP engine triggers an error whenever it encounters a problem with your script  but you can also trigger errors yourself to generate more user friendly error messages  This way you can make your application more sofisticated  The following section describes some of common methods used for handling errors in PHP      Basic Error Handling Using the die   Function    lt  php    Try to open a non-existent file       file   fopen  sample txt    r      gt    If the file does not exist you might get an error like this  Warning  fopen sample txt   function fopen   failed to open stream  No such file or directory in C  wamp www project test php on line 2  If we follow some simple steps we can prevent the users from getting such error message    lt  php if file exists  sample txt          file   fopen  sample txt    r      else      die  Error  The file you are trying to access doesn t exist         gt    Now if you run the above script you will get the error message like this  Error  The file you are trying to access doesn t exist   As you can see by implementing a simple check whether the file exist or not before trying to access it  we can generate an error message that is more meaningful to the user   The die   function used above simply display the custom error message and terminate the current script if  sample txt  file is not found      Creating a Custom Error Handler   You can create your own error handler function to deal with the run-time error generated by PHP engine  The custom error handler provides you greater flexibility and better control over the errors  it can inspect the error and decide what to do with the error  it might display a message to the user  log the error in a file or database or send by e-mail  attempt to fix the problem and carry on  exit the execution of the script or ignore the error altogether   The custom error handler function must be able to handle at least two parameters  errno and errstr   however it can optionally accept an additional three parameters  errfile  errline  and errcontext   as described below     Here s an example of a simple custom error handling function  This handler  customError   is triggered whenever an error occurred  no matter how trivial  It then outputs the details of the error to the browser and stops the execution of the script    lt  php    Error handler function function customError  errno   errstr       echo   lt b gt Error  lt  b gt    errno   errstr       gt    You need to tell the PHP to use your custom error handler function     just call the built-in set error handler   function  passing in the name of the function    lt  php    Error handler function function customError  errno   errstr       echo   lt b gt Error  lt  b gt    errno   errstr         Set error handler set error handler  customError        Trigger error echo  test     gt       Error Logging   Log Error Messages in a Text File  You can also logs details of the error to the log file  like this    lt  php function calcDivision  dividend   divisor       if  divisor    0           trigger error  calcDivision    The divisor cannot be zero   E USER WARNING           return false        else          return  dividend    divisor           function customError  errno   errstr   errfile   errline   errcontext        message   date  Y-m-d H i s -          message     Error        errno            errstr in  errfile on line  errline          message     Variables     print r  errcontext  true      r n        error log  message  3   logs app errors log        die  There was a problem  please try again       set error handler  customError    echo calcDivision 10  0   echo  This will never be printed      gt       Trigger an Error   Although the PHP engine triggers an error whenever it encounters a problem with your script  however you can also trigger errors yourself  This can help to make your application more robust  because it can flag potential problems before they turn into serious errors   To trigger an error from within your script  call the trigger error   function  passing in the error message that you want to generate   trigger error  There was a problem       Consider the following function that calculates division of the two numbers    lt  php function calcDivision  dividend   divisor       return  dividend    divisor         Calling the function echo calcDivision 10  0     gt    If a value of zero  0  is passed as the  divisor parameter  the error generated by the PHP engine will look something like this  Warning  Division by zero in C  wamp www project test php on line 3  This message doesn t look very informative  Consider the following example that uses the trigger error   function to generate the error    lt  php function calcDivision  dividend   divisor       if  divisor    0           trigger error  The divisor cannot be zero   E USER WARNING           return false        else          return  dividend    divisor               Calling the function echo calcDivision 10  0     gt    Now the script generates this error message  Warning  The divisor cannot be zero in C  wamp www project error php on line 4  As you can see the error message generated by the second example explains the problem more clearly as compared to the previous one

User · Answer

Try setting your error reporting level in your actual php files  Or  as others have suggested  check your server settings--it could be something in php ini  or some restriction as regards your host  Don t just rely on  htaccess  Also  when troubleshooting  print r any variables you might think fishy

User · Answer

The    ERRORS    are the most useful things for the developers to know their mistakes and resolved them  to make the system working perfect   PHP provides some of better ways to know the developers why and where their piece of code is getting the errors  so by knowing those errors developers can make their code better in many ways   Best ways to write following two lines on the top of script to get all errors messages   error reporting E ALL   ini set  display errors   1     Another way to use debugger tools like xdebug in your IDE

User · Answer

This answer is brought to you by the department of redundancy department         ini set     php ini    htaccess    user ini  The settings display errors and error reporting have been covered sufficiently now  But just to recap when to use which option    ini set   and error reporting   apply for runtime errors only  php ini should primarily be edited for development setups   Webserver and CLI version often have different php ini s   htaccess flags only work for dated setups  Find a new hoster  Well managed servers are cheaper    user ini are partial php ini s for modern setups  FCGI FPM    And as crude alternative for runtime errors you can often use   set error handler  var dump         ignores error reporting and     suppression  error get last    Can be used to retrieve the last runtime notice warning error  when error display is disabled   php errormsg  Is a superlocal variable  which also contains the last PHP runtime message  isset   begone   I know this will displease a lot of folks  but isset and empty should not be used by newcomers  You can add the notice suppression after you verified your code is working  But never before   A lot of the  something doesn t work  questions we get lately are the result of typos like   if isset   POST  sumbit                             You won t get any useful notices if your code is littered with isset empty array keys exists  It s sometimes more sensible to use    so notices and warnings go to the logs at least  assert options ASSERT ACTIVE ASSERT WARNING    To get warnings for assert   sections   Pretty uncommon  but more proficient code might contain some    PHP7 requires zend assertions 1 in the php ini as well  declare strict types 1    Bending PHP into a strictly typed language is not going to fix a whole lot of logic errors  but it s definitely an option for debugging purposes  PDO   MySQLi  And  Phil already mentioned PDO MySQLi error reporting options  Similar options exist for other database APIs of course  json last error     json last error msg  For JSON parsing  preg last error    For regexen  CURLOPT VERBOSE  To debug curl requests  you need CURLOPT VERBOSE at the very least  shell exec    Likewise will shell command execution not yield errors on its own  You always need 2 gt  amp 1 and peek at the  errno

User · Answer

This is a problem of loaded vs  runtime configuration It s important to recognize that a syntax error or parse error happens during the compile or parsing step  which means that PHP will bail before it s even had a chance to execute any of your code  So if you are modifying PHP s display errors configuration during runtime   this includes anything from using ini set in your code to using  htaccess  which is a runtime configuration file  then only the default loaded configuration settings are in play  How to always avoid WSOD in development To avoid a WSOD you want to make sure that your loaded configuration file has display errors on and error reporting set to -1  this is the equivalent E ALL because it ensures all bits are turned on regardless of which version of PHP you re running   Don t hardcode the constant value of E ALL  because that value is subject to change between different versions of PHP  Loaded configuration is either your loaded php ini file or your apache conf or httpd conf or virtualhost file  Those files are only read once during the startup stage  when you first start apache httpd or php-fpm  for example  and only overridden by runtime configuration changes  Making sure that display errors   1 and error reporting   -1 in your loaded configuration file ensures that you will never see a WSOD regardless of syntax or parse error that occur before a runtime change like ini set  display errors   1   or error reporting E ALL   can take place  How to find your  php ini  loaded configuration files To locate your loaded configuration file s  just create a new PHP file with only the following code     lt  php phpinfo     Then point your browser there and look at Loaded Configuration File and Additional  ini files parsed  which are usually at the top of your phpinfo   and will include the absolute path to all your loaded configuration files  If you see  none  instead of the file  that means you don t have a php ini in Configuration File  php ini  Path  So you can download the stock php ini bundled with PHP from here and copy that to your configuration file path as php ini then make sure your php user has sufficient permissions to read from that file  You ll need to restart httpd or php-fpm to load it in  Remember  this is the development php ini file that comes bundled with the PHP source  So please don t use it in production   Just don t do this in production This really is the best way to avoid a WSOD in development  Anyone suggesting that you put ini set  display errors   1   or error reporting E ALL   at the top of your PHP script or using  htaccess like you did here  is not going to help you avoid a WSOD when a syntax or parse error occurs  like in your case here  if your loaded configuration file has display errors turned off  Many people  and stock installations of PHP  will use a production-ini file that has display errors turned off by default  which typically results in this same frustration you ve experienced here  Because PHP already has it turned off when it starts up  then encounters a syntax or parse error  and bails with nothing to output  You expect that your ini set  display errors  1   at the top of your PHP script should have avoided that  but it won t matter if PHP can t parse your code because it will never have reached the runtime

User · Answer

put this code in your code    error reporting -1   ini set  display errors    On

User · Answer

Some applications do handle these instructions themselves  by calling something like this    error reporting E ALL  amp   E DEPRECATED   or error reporting 0     And thus overriding your  htaccess settings

User · Answer

The following code should display all errors    lt  php     ----------------------------------------------------------------------------------------------------    - Display Errors    ---------------------------------------------------------------------------------------------------- ini set  display errors    On    ini set  html errors   0       ----------------------------------------------------------------------------------------------------    - Error Reporting    ---------------------------------------------------------------------------------------------------- error reporting -1       ----------------------------------------------------------------------------------------------------    - Shutdown Handler    ---------------------------------------------------------------------------------------------------- function ShutdownHandler         if  is array  error    error get last                   return  call user func array  ErrorHandler    error                return TRUE       register shutdown function  ShutdownHandler        ----------------------------------------------------------------------------------------------------    - Error Handler    ---------------------------------------------------------------------------------------------------- function ErrorHandler  type   message   file   line          ERRORS   Array          0x0001   gt   E ERROR           0x0002   gt   E WARNING           0x0004   gt   E PARSE           0x0008   gt   E NOTICE           0x0010   gt   E CORE ERROR           0x0020   gt   E CORE WARNING           0x0040   gt   E COMPILE ERROR           0x0080   gt   E COMPILE WARNING           0x0100   gt   E USER ERROR           0x0200   gt   E USER WARNING           0x0400   gt   E USER NOTICE           0x0800   gt   E STRICT           0x1000   gt   E RECOVERABLE ERROR           0x2000   gt   E DEPRECATED           0x4000   gt   E USER DEPRECATED              if   is string  name    array search  type   array flip   ERRORS                    name    E UNKNOWN               return print  sprintf   s Error in file  xBB s xAB at line  d   s n    name   basename  file    line   message          old error handler   set error handler  ErrorHandler        other php code    gt    The only way to generate a blank page with this code is when you have a error in the shutdown handler  I copied and pasted this from my own cms without testing it  but I am sure it works

User · Answer

Turning on error reporting is the correct solution  however it does not seem to take effect in the program that turns it on  but only in subsequently included programs   Thus  I always create a file program  which I usually call  genwrap php   which has essentially the same code as the popular solution here  ie  turn on error reporting  and it also then includes the page I actually want to call   There are 2 steps to implement this debugging   One - create genwrap php and put this code in it    lt  php error reporting -1   ini set  display errors    On     include   REQUEST  page       gt    Two - change the link to the program page you want to debug to go via genwrap php   Eg  change     ajax  dir pgm php param val   done function data                to    ajax  dir genwrap php page pgm php amp param val   done function data

User · Answer

If you are super cool  you might try    test server     SERVER  SERVER NAME       127 0 0 1       SERVER  SERVER NAME       localhost     substr   SERVER  SERVER NAME   0 3      192    ini set  display errors   test server   error reporting E ALL E STRICT     This will only display errors when you are running locally  It also gives you the test server variable to use in other places where appropriate   Any errors that happen before the script runs won t be caught  but for 99  of errors that I make  that s not an issue

User · Answer

To persist this and make it confortale  you can edit your php ini file  It is usually stored in  etc php ini or  etc php php ini  but more local php ini s may overwrite it  depending on your hosting provider s setup guidelines  Check a phpinfo   file for Loaded Configuration File at the top  to be sure which one gets loaded last   Search for display errors in that file  There should be only 3 instances  of which 2 are commented   Change the uncommented line to   display errors   stdout

User · Answer

Are you sure PHP is actually picking up the  display errors  setting from  htaccess  Check the output of the phpinfo   function to make sure   Also  you should check to make sure that you haven t used      it could be silencing your errors if you have used   include      or   some function        somewhere up the stack trace

User · Answer

error reporting E ALL   E STRICT     And turn on display errors in php ini

User · Answer

I don t know if it will help  but here is a piece of my standard config file for php projects   I tend not to depend too much on the apache configs even on my own server  I never have the disappearing error problem  so perhaps something here will give you an idea  Edited to show APPLICATON LIVE    APPLICATION LIVE will be used in process to tell if we are in a development or production environment   It s generally set as early as possible  often the first code to run   before any config  url routing  etc      if   preg match   quot    www   livedomain com   quot     SERVER  quot HTTP HOST quot            define  APPLICATION LIVE   true     elseif   preg match   quot    www   devdomain net   quot     SERVER  quot HTTP HOST quot            define  APPLICATION LIVE   false     else       die  quot INVALID HOST REQUEST   quot    SERVER  quot HTTP HOST quot    quot   quot           Log or take other appropriate action         -------------------------------------------------------------------- DEFAULT ERROR HANDLING -------------------------------------------------------------------- Default error logging   Some of these may be changed later based on APPLICATION LIVE     error reporting E ALL  amp   E STRICT   ini set    quot display errors quot    quot 0 quot    ini set    quot display startup errors quot    quot 0 quot    ini set    quot log errors quot   1   ini set    quot log errors max len quot   0   ini set    quot error log quot   APPLICATION ROOT  quot logs php error log txt quot    ini set    quot display errors quot    quot 0 quot    ini set    quot display startup errors quot    quot 0 quot     if     APPLICATION LIVE            A few changes to error handling for development         We will want errors to be visible during development      ini set    quot display errors quot    quot 1 quot        ini set    quot display startup errors quot    quot 1 quot        ini set    quot html errors quot    quot 1 quot        ini set    quot docref root quot    quot http   www php net  quot        ini set    quot error prepend string quot    quot  lt div style  color red  font-family verdana  border 1px solid red  padding 5px   gt  quot        ini set    quot error append string quot    quot  lt  div gt  quot

User · Answer

Errors and warnings usually appear in      logs php error log or      logs apache error log depending on your php ini settings   Also useful errors are often directed to the browser  but as they are not valid html they are not displayed   So  tail -f  your log files and when you get a blank screen use IEs  view  -   source  menu options to view the raw output

User · Answer

It is possible to register an hook to make the last error or warning visible   function shutdown      var dump error get last        register shutdown function  shutdown      adding this code to the beginning of you index php will help you debug the problems

User · Answer

if you are a ubuntu user then goto your terminal and run this command  sudo tail -50f  var log apache2 error log   where it will display recent 50 errors   There is a error file error log for apache2 which logs all the errors

User · Answer

The two key lines you need to get useful errors out of PHP are   ini set  display errors  1    error reporting E ALL     As pointed out by other contributors  these are switched off by default for security reasons  As a useful tip - when you re setting up your site it s handy to do a switch for your different environments so that these errors are ON by default in your local and development environments  This can be achieved with the following code  ideally in your index php or config file so this is active from the start    switch   SERVER  SERVER NAME             local     case  yourdomain dev          dev     case  dev yourdomain com           ini set  display errors  1           error reporting E ALL       break        live     case  yourdomain com                     break

User · Answer

You can register your own error handler in PHP  Dumping all errors to a file might help you in these obscure cases  for example  Note that your function will get called  no matter what your current error reporting is set to  Very basic example   function dump error to file  errno   errstr        file put contents   tmp php-errors   date  Y-m-d H i s -       errstr  FILE APPEND     set error handler  dump error to file

User · Answer

error reporting E ALL   E STRICT   ini set  display errors   1   ini set  html errors   1     In addition  you can get more detailed information with xdebug

User · Answer

In addition to the very many excellent answers above you could also implement the following two functions in your projects  They will catch every non-syntax error before application script exit  Inside the functions you can do a backtrace and log or render a pleasant  Site is under maintenance  message to the public   Fatal Errors   register shutdown function   http   php net manual en function register-shutdown-function php  Errors   set error handler   http   php net manual en function set-error-handler php  Backtracing   debug backtrace   http   php net manual en function debug-backtrace php

[php] How can I get useful error messages in PHP?

Examples related to php

Examples related to debugging

Examples related to error-handling