Pierre Joye wrote:
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.
I get it that all user gets is a white screen because that is what has been documented to returned. In the past we at least got something, but in these modern times IS a blank screen really an acceptable return? If it was just returning messy displays it would at least be something and we can then build on that to get things working properly.
A number of my customers have come to me because they got no help from their ISP's and other ISP's switched back to older versions of PHP because too many sites simply broke. They don't have enough staff to fix PHP code and it's not their job? One of the best ways of getting the PHP5.2 sites updated is providing a default setup that minimizes the occurrence of a blank page. As Yasuo says 'even just a warning page'. With a blank page would a simple user even know that PHP has anything to do with why it's blank?
--
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