Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72264 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 142 invoked from network); 5 Feb 2014 11:02:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Feb 2014 11:02:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.51 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.51 mail-la0-f51.google.com Received: from [209.85.215.51] ([209.85.215.51:38113] helo=mail-la0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 74/44-09402-B4A12F25 for ; Wed, 05 Feb 2014 06:02:36 -0500 Received: by mail-la0-f51.google.com with SMTP id c6so175311lan.38 for ; Wed, 05 Feb 2014 03:02:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=P2r/76fnclNqKECylqhZTRzlF4Bwpfw0YEKFyoXZ19A=; b=W8yWvovpTVfoNkINjwSVFpWdLQZnUtdWO2s/6jmvs8dweF/LUZQ3O/iZMUSfLgrrMK JJny18uqhgKCc7t5Vc7iaS/b8j1PIBfheVz/nN9sgr578MGlL9eRNapZdEWDdUj5x69A P+O67QIeqKZkxbuLP3di9RkJ9ALkU8y/JUGfKxWmLjb10bnAdgQnh/mJLBcPn7IvlGTj byV6I0lodu3vpB7oJl0j2ZNDQc/TGZBBoEGSKJIS21Zz8VFazpVmwWaSWndljDrkVv/d 7I9I07ws7UXbTItqAT3OqLTB9cDCZ1AfOESMza4X2/ejQ0edPHW2BJwBnXAvrhQvgL9X bF7Q== X-Received: by 10.112.131.100 with SMTP id ol4mr620647lbb.38.1391598151560; Wed, 05 Feb 2014 03:02:31 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.199.37 with HTTP; Wed, 5 Feb 2014 03:01:51 -0800 (PST) In-Reply-To: <52F2165E.6040104@lsces.co.uk> References: <52EF4BF8.60005@sugarcrm.com> <52F14C66.3030806@gmail.com> <52F15B62.1070006@gmail.com> <52F20C7C.3040803@lsces.co.uk> <52F2165E.6040104@lsces.co.uk> Date: Wed, 5 Feb 2014 20:01:51 +0900 X-Google-Sender-Auth: MUZNu1g7aHVvY2gCAAQO4C0sWMA Message-ID: To: Lester Caine Cc: PHP internals Content-Type: multipart/alternative; boundary=047d7b3441b47e732204f1a6b119 Subject: Re: [PHP-DEV] Declare minimum PHP version required? From: yohgaki@ohgaki.net (Yasuo Ohgaki) --047d7b3441b47e732204f1a6b119 Content-Type: text/plain; charset=UTF-8 Hi Lester, On Wed, Feb 5, 2014 at 7:45 PM, Lester Caine wrote: > If you look at the bulk of PHP users, they are using PHP via a hosting > service, who set up the 'production server' for them. When they install an > 'application', it's install section takes care of configuration. Then the > ISP changes PHP version and they get a white screen ... help ... > > At this point what PHP needs to supply as a minimum is just a 'php has > crashed please check log', but ideally we should be able to direct these > 'simple' users back to their installation section if that can handle the > problem. 95% of users would probably not understand what the difference > between a production and develop server is? Telling them they have no place > using PHP is not acceptable? > I think your comment is valuable. Under production environment, web apps should not display any internal data including PHP errors. However, it may be a good idea to have option for administrators to display some messages. Perhaps, INI like fatal_error_message = "Program had fatal error. Please consult XXXXXX" might be useful for ISPs admins and users. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --047d7b3441b47e732204f1a6b119--