Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72273 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24212 invoked from network); 5 Feb 2014 14:02:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Feb 2014 14:02:43 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.204 mail4.serversure.net Linux 2.6 Received: from [217.147.176.204] ([217.147.176.204:42503] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D3/E7-09402-18442F25 for ; Wed, 05 Feb 2014 09:02:42 -0500 Received: (qmail 22961 invoked by uid 89); 5 Feb 2014 14:02:38 -0000 Received: by simscan 1.3.1 ppid: 22952, pid: 22958, t: 0.0636s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO linux-dev4.lsces.org.uk) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 5 Feb 2014 14:02:38 -0000 Message-ID: <52F2452D.1090102@lsces.co.uk> Date: Wed, 05 Feb 2014 14:05:33 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23 MIME-Version: 1.0 To: PHP internals References: <52EF4BF8.60005@sugarcrm.com> <52F14C66.3030806@gmail.com> <52F15B62.1070006@gmail.com> <52F20C7C.3040803@lsces.co.uk> <52F2165E.6040104@lsces.co.uk> <52F23078.4040206@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Declare minimum PHP version required? From: lester@lsces.co.uk (Lester Caine) Pierre Joye wrote: > With a blank page would a simple user even know that PHP has anything to do with > why it's blank? > > It is not a php problem per se. Php cannot do anything after a fatal error or a > crash. So how do we protect PHP from crashing in such a way that it can actually display an alternate page to the 'white screen of death'? > It takes 5 mins to any admin (7 for non Admin) to setup a default error page, in > any webserver. And it does exactly what you suggest. So why are there so many reports of 'white screen of death' if it is easy to provide something more useful? Even the big frameworks seem to have a problem with this. I do think this is an important area in order to bring forward the majority of the current user base ... -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk