error-reporting | 易学教程

How to display errors on laravel 4?

阅读更多关于 How to display errors on laravel 4?

I'm trying to create an app on Laravel 4 beta but I can't debug it because it doesn't show any error, display_errors is on, error_reporting is E_ALL and debug => true ( config/app.php ). When I try to do an error on public/index.php it shows a parse error, but when I do it on the router it just shows a blank page (White screen of death). How can I fix this? Thank you @Matanya - have you looked at your server logs to see WHAT the error 500 actually is? It could be any number of things @Aladin - white screen of death (WSOD) can be diagnosed in three ways with Laravel 4. Option 1: Go to your

What are the reasons why PHP would echo errors, even with error_reporting(0)?

阅读更多关于 What are the reasons why PHP would echo errors, even with error_reporting(0)?

问题 What are some reasons why PHP would force errors to show, no matter what you tell it to disable? I have tried error_reporting(0); ini_set('display_errors', 0); with no luck. 回答1: Note the caveat in the manual at http://uk.php.net/error_reporting: Most of E_STRICT errors are evaluated at the compile time thus such errors are not reported in the file where error_reporting is enhanced to include E_STRICT errors (and vice versa). If your underlying system is configured to report E_STRICT errors,

Php Error Reporting even when display error is on

阅读更多关于 Php Error Reporting even when display error is on

I'm getting a problem with my php scripts. No error reporting is being made in spite that in my php.ini that i've set display error everywhere ; display_errors ; Default Value: On ; Development Value: On ; Production Value: On ; display_startup_errors ; Default Value: Off ; Development Value: On ; Production Value: Off ; error_reporting ; Default Value: E_ALL ; Development Value: E_ALL ; Production Value: E_ALL Salman You have to use these: display_errors = On display_startup_errors = On error_reporting = E_ALL With no ; at the start of the line. That is a comment and just disables the

PHP Error Reporting Production vs Development

阅读更多关于 PHP Error Reporting Production vs Development

What is best practice when setting error reporting on development and production applications? At the moment I have the following: // development error_reporting(E_ALL); // production ini_set('display_errors', 0); ini_set('log_errors', 1); error_reporting(E_ERROR | E_WARNING | E_PARSE); I see people have downvoted the question. Perhaps explain why the question is bad instead of just downvoting. Quoting the php-production.ini that should have come bundled with your PHP: ; PHP comes packaged with two INI files. One that is recommended to be used ; in production environments and one that is

Can the ASP.NET Yellow Screen of Death (YSOD) be generated on demand or captured?

阅读更多关于 Can the ASP.NET Yellow Screen of Death (YSOD) be generated on demand or captured?

问题 We'd like to just capture the YSOD output to use in an erorr reporting email, from a Global.asax error handler, for instance. Is there any way of leveraging the built-in ysod generator? 回答1: Yes there is a way that you can do this. In the Application_Error event in the global.asax file, get the last exception as an System.HttpUnhandledException. Your code will look like this: var lastException = Server.GetLastError() as HttpUnhandledException; string Ysod = lastException.GetHtmlErrorMessage()

Parse errors are not displayed

阅读更多关于 Parse errors are not displayed

I want PHP to display parse errors on screen. What I get instead is a blank page. Nothing gets written to server's error log file. My setup: PHP5.2.9/ IIS 6 (not Apache!). My PHP.INI: error_reporting=E_STRICT display_errors = On display_startup_errors = On log_errors = On error_log = "C:\Program Files\Zend\ZendServer\logs\php_error.log" How do I get parse or fatal errors to be either logged or shown on screen? Thanks, Temuri UPDATE : After playing with different switches it looks to be an IIS specific problem. ANY IDEAS FOLKS? Setting error level in php file itself does not resolve the problem

How can I capture all exceptions from a wxPython application?

阅读更多关于 How can I capture all exceptions from a wxPython application?

问题 I'm writing a little debug app for a bit of kit we're developing and I'd like to roll it out to a few users to see if they can provoke any crashes. Does anyone know a way of effectively wrapping a wxPython app to catch any and all unhandled exceptions that would cause the app to crash? Ideally I'd want to capture all output (not just errors) and log it to a file. Any unhandled exceptions ought to log to the current file and then allow the exception to pass on as per usual (i.e. the logging

How to display errors on laravel 4?

阅读更多关于 How to display errors on laravel 4?

问题 I'm trying to create an app on Laravel 4 beta but I can't debug it because it doesn't show any error, display_errors is on, error_reporting is E_ALL and debug => true ( config/app.php ). When I try to do an error on public/index.php it shows a parse error, but when I do it on the router it just shows a blank page (White screen of death). How can I fix this? Thank you 回答1: @Matanya - have you looked at your server logs to see WHAT the error 500 actually is? It could be any number of things

PHP not displaying errors even though display_errors = On

阅读更多关于 PHP not displaying errors even though display_errors = On

I have a Ubuntu server running Apache2 with PHP 5. In the php.ini I set error_reporting = E_ALL | E_STRICT and error_reporting = E_ALL | E_STRICT , but PHP is still not displaying error messages. I'm also using Apache virtual hosts. Also, what is the most strict error reporting PHP5.3 has to offer? I want my code to as up-to-date and future-proof as possible. Ray You also need to make sure you have your php.ini file include the following set or errors will go only to the log that is set by default or specified in the virtual host's configuration. display_errors = On The php.ini file is where

How to get users to read error messages?

阅读更多关于 How to get users to read error messages?

问题 If you program for a nontechnical audience, you find yourself at a high risk that users will not read your carefully worded and enlightening error messages, but just click on the first button available with a shrug of frustration. So, I'm wondering what good practices you can recommend to help users actually read your error message, instead of simply waiving it aside. Ideas I can think of would fall along the lines of: Formatting of course help; maybe a simple, short message, with a "learn