Hi Lester,
On Wed, Feb 5, 2014 at 7:45 PM, Lester Caine <[email protected]> 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
[email protected]