Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72266
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAGa2bXaZwjH2haHkgyf=Y6uQGr+cB-G9ERNh3xP8+-e6OwAJ9Q@mail.gmail.com>
References: <CAGa2bXYHP5D70bDBhbWzE7-B0s2kgk7DmAZdFhXkLqMJQqKV5g@mail.gmail.com>
	<52EF4BF8.60005@sugarcrm.com>
	<CAGa2bXacCxnmcAPZjh-YgTNocMjEpu_Uoc4npfNcKVM2WA2Tow@mail.gmail.com>
	<CAGa2bXZt7n8aqA=VrBKsqBzFiusGZP7aECPO-7xQher4+uVLWg@mail.gmail.com>
	<52F14C66.3030806@gmail.com>
	<CAH-PCH4+ULN2bVh=A2ZNvXmpYDqBPA3JrhhdrKb5zVH_sXucxg@mail.gmail.com>
	<52F15B62.1070006@gmail.com>
	<CAH-PCH4qXWJF_qN2ap0u+ufOMTah3VTR9t-BrV+9qkqD-KdixQ@mail.gmail.com>
	<CAGa2bXaj3Az2yYswgpS1yTFiYR+=j2tM-5y5paMrcjftx=X9pw@mail.gmail.com>
	<52F20C7C.3040803@lsces.co.uk>
	<CAEZPtU5OPzcOmXbY2mgHr7Ckz=k852DXsf3pNg9Ut5qVv07qbA@mail.gmail.com>
	<52F2165E.6040104@lsces.co.uk>
	<CAGa2bXaZwjH2haHkgyf=Y6uQGr+cB-G9ERNh3xP8+-e6OwAJ9Q@mail.gmail.com>
Date: Wed, 5 Feb 2014 12:48:28 +0100
Message-ID: <CAEZPtU52JNHcF2OEVDa5K2zmqiL5kGDqW1bw0BWpk4O8bGBn2A@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: Lester Caine <lester@lsces.co.uk>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Declare minimum PHP version required?
From: pierre.php@gmail.com (Pierre Joye)

hi,

On Wed, Feb 5, 2014 at 12:01 PM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> Hi Lester,
>
> On Wed, Feb 5, 2014 at 7:45 PM, Lester Caine <lester@lsces.co.uk> 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.

ISPs admins (or any admins) can read logs, and will read logs. They do
check customers error logs to prevent flaws, issues, excessive
resource usages, etc. Panels and other user friendly systems provide
log viewers with alerts.

But the key point remains the same, no error should be displayed in
production (whatever hosting is used), this is well documented since
years. I have some hard time to understand why we keep having to
explain why. If the documentation needs improvements, then let try to
fix it. But adding yet another option to finally do something that we
try to prevent since years does not sound very appealing to me.

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org