Drupal 7 Error Reporting

all over the world. Join today Community Documentation Community Docs Home Develop for Drupal Theming Guide Glossary Contribute to Docs Blank pages or "white screen

Drupal 7 Error Sending Email

of death" (WSOD) Last updated August 22, 2016. Created on July 10, windows 7 error reporting 2007.Edited by rhuffstedtler, Ayesh, Sutharsan, lolandese. Log in to edit this page.Occasionally a site user or developer will windows 7 error reporting tool navigate to a page and suddenly the page content disappears, and it becomes blank. No content. No errors. Nothing. This happens sometimes, It could happen after updating a module, theme, https://www.drupal.org/node/1036982 or Drupal core. This is what is referred to by most members of the Drupal community as the White Screen of Death or WSOD. There are several reasons why this might occur, and therefore several possible solutions to the issue. (Note: The suggestions on this page might solve the problem even when you do not get the WSOD as it relates https://www.drupal.org/node/158043 to an Internal Server Error.) "Invisible" Errors If error reporting is turned off, you could be getting a fatal error but not seeing it. On a production site, it is common to have error reporting turned off. If that is the case and PHP has hit an unrecoverable error, neither an error nor content will be displayed, therefore you end up with a completely blank page. What you can do about this is either turn on PHP error reporting so it displays a message on the page itself, or check your log files (from the server) to look for the error. How to do both of these are explained below. Enable Error Reporting Although it may be turned off on commercial hosts and production sites (for good reason, so that users do not see the errors), these errors are one of your best tools for troubleshooting. To enable error reporting, temporarily edit your index.php file (normally located in your root directory) directly after the first opening PHP tag (do not edit the actual file info!) to add the following:

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring http://drupal.stackexchange.com/questions/15415/how-do-i-silence-php-errors developers or posting ads with us Drupal Answers Questions Tags Users Badges Unanswered Ask Question http://definitivedrupal.org/err _ Drupal Answers is a question and answer site for Drupal developers and administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How do I silence PHP errors? up vote 23 down vote favorite 6 Is there a way 7 error to silence all PHP errors, warnings and notices in Drupal? They are usefull on the devel site but they are a big security risk, and make the site look bad on live. I know on Drupal 6 the page at admin/settings/error-reporting can stop Drupal from writing errors to the screen, but where can I find this in Drupal 7? It seems it is missing. 7 share|improve this question edited Sep 27 '13 at 20:05 kiamlaluno♦ 66.5k897192 asked Nov 14 drupal 7 error '11 at 9:14 drupal_stuff_alter 1,78911743 2 Do note, though, that errors have a very important role: they indicate that something is wrong. Surpressing that, does not solve the underlying problem. This is also called the "Russian Method": When the alarm-light in a nuclear plant starts blinking, just remove the lightbulb. Alarm-light no longer blinks; no problems. –berkes Nov 14 '11 at 10:00 Funny :). But I only suppress error on the production site. –drupal_stuff_alter Nov 14 '11 at 12:13 Drupal has the option to decide which errors should be displayed; not displayed errors are still recorded in the database, and shown in admin/reports/dblog. –kiamlaluno♦ Nov 14 '11 at 17:03 @kiamlaluno, in production that is somewhat fine (yet presenting an error that a payment failed is always better then leaving your client in uncertainty). But in development and testing my experience is that errors pushed into dblog are neglegted. Drupalsites with hundreds of notices and warnings per hour logged there, is no exception. And real exceptions and errors are lost in the noise. Best is to push each and every notice hard into the face of the developer. –berkes Nov 14 '11 at 21:17 Right, but the OP seems to be interested to hide those errors in a production site. (See, "They are usefull on the devel site but they are a big security risk,

developing- so you know when something isn't right even when everything seems to be working fine, and even more when things go wrong. The below code goes in settings.php (minus the opening and closing php tags; settings.php will already have opened PHP at the top of the file and you should not close PHP at the end of a document. error_reporting(-1);  // Have PHP complain about absolutely everything.
$conf['error_level'] = 2;  // Show all messages on your screen
ini_set('display_errors', TRUE);  // These lines give you content on WSOD pages.
ini_set('display_startup_errors', TRUE);
?> Note that for the error_level configuration setting above 2 = ERROR_REPORTING_DISPLAY_ALL but that constant is not loaded yet, so we have to use the number 2. Originally inspired by and posted to Randy Fay's blog post, If you edit PHP code, please work with E_NOTICE turned on!!!. Note As noted, the configuration 'error_level' sets what level of warning and error messages are sent to the screen. As a general principle, though, how do you know what configuration variables are available for overriding in settings.php? You can see what values are presently in the variable table with debug($conf); in your code. However, variables which have never had their settings form saved – which are still at their default value – will not show up in the table or the $conf array. Instead, the fastest way to determine the names of