Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62803 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82883 invoked from network); 4 Sep 2012 16:55:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Sep 2012 16:55:26 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.188 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 213.123.26.188 c2beaomr10.btconnect.com Received: from [213.123.26.188] ([213.123.26.188:14998] helo=mail.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8F/66-46870-C7236405 for ; Tue, 04 Sep 2012 12:55:25 -0400 Received: from host81-138-11-136.in-addr.btopenworld.com (EHLO _10.0.0.5_) ([81.138.11.136]) by c2beaomr10.btconnect.com with ESMTP id IVC50513; Tue, 04 Sep 2012 17:55:21 +0100 (BST) Message-ID: <50463277.8020503@lsces.co.uk> Date: Tue, 04 Sep 2012 17:55:19 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120604 Firefox/13.0 SeaMonkey/2.10 MIME-Version: 1.0 To: PHP internals References: <5042946A.80204@sugarcrm.com> <5042A7D6.7050001@lerdorf.com> <50452713.3020307@sugarcrm.com> <5045CAA3.6000409@lsces.co.uk> <5045E044.9080809@lsces.co.uk> <5045F939.6010806@lsces.co.uk> <5045FD98.8080306@lsces.co.uk> <504605A5.3000600@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0302.50463277.00CB, actions=tag X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.9.4.161815:17:7.944, ip=81.138.11.136, rules=__MOZILLA_MSGID, __HAS_MSGID, __SANE_MSGID, __FW_1LN_BOT_MSGID, __HAS_FROM, __USER_AGENT, __MIME_VERSION, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __CT, __CT_TEXT_PLAIN, __CTE, __ANY_URI, __URI_NO_MAILTO, __URI_NO_WWW, __CP_URI_IN_BODY, BODY_ENDS_IN_URL, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, RDNS_SUSP, BODY_SIZE_7000_LESS X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0205.50463279.0074:SCFSTAT14830815,ss=1,re=-4.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine X-Junkmail-IWF: false Subject: Re: [PHP-DEV] E_STRICT 'errors' - was Are exceptions allowed in php core? From: lester@lsces.co.uk (Lester Caine) Ferenc Kovacs wrote: > Using third party code - joomla - only difference between working and not > working is switching E_STRICT on. With display_errors=off one gets a white > screen. I was not surprised as I've had this all the way through with code > from many sources. Yes a lot of the time you just get the error messages, > but a white screen crash has been the norm most of the time so leaving > display_errors=on helps while fault finding on the development systems. > > usually most people set display_errors=off but log_errors = on and just check > the logfiles for errors. > there is no point bothering your users with messages they won't understand or > could be able to do anything about, plus it is usually a security vulnerability > (Information Leakage). I know all about that side of things ... now I just need to recreate what has been giving me white screens ... having spent a year getting rid of them. GOT IT ... Or at least a white screen, but of cause now that some things have been pointed out then it's obvious what is going on! 12 months on I can see things differently! It is a fatal 'PHP Fatal error: Cannot make static method ... non static' at least on this white screen. The base library has some 'static' references but the descendent classes don't. Having updated some core libraries, the rest of the code is out of sync. But I've managed to pick up a back version that is full of 'deprecated' errors as well. So I need to scroll forward a bit so that I only have E_STRICT differences. I'm fairly sure now that it's the missing 'static' references in PEAR that start some of the confusion on this. I needed a clean strict version of PEAR as the base classes for some areas. And then make sure I don't access that with other websites that have yet to be 'upgraded'. Joomla may be failing over if it's picking up the wrong central libraries? Not having using it before I'll need to check what is picking up centrally. And the error log growing at 40 time the size of the access log is not encouraging from a maintenance viewpoint :( Hiding errors is all very well, but the error log still needs to be usable in production. -- 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