Richard Lynch wrote:
On Mon, April 17, 2006 6:19 pm, Jochem Maas wrote:
But they had guys at an old job that did this, after I turned OFF
display_output on their production server... [shudder]
I guess Richard's had another long day ... display_output? maybe
display_errors? or was the stuff those guys produced so bad that a
blank page was preferable? ;-)
Actually, now that I think about it...
Maybe we need a new directive in php.ini :-)
I dare you to ask on php-internals ;-)
;Turns off all output to browser
;Useful when somebody realizes how bad their software really is
;Or when they get sued for same
;display_output = On
:-) :-) :-)
The REALLY scary thing was their application was all about people's
medical records and insurance -- so they were "HIPPA compliant".
Don't even ask me how display_errors on production boxes seemed OK
with "HIPPA compliant" software in ANYBODY's brain, cuz I just don't
get it...
PS
In retrospect, I turned off display_errors on all servers, production
and dev, because they had no way to detect production versus dev in
the first place, in a meaningful way to have them behave differently.
I think I fixed that problem next, and would have turned
display_errors back on, but they already had their "tail.php" script,
and it avoided a lot of questions from programmers too naive to do
"View Source"
the only thing that annoys me is that these numpties probably earn twice
what I do, pay a third the price for their cars and drive from one end
of the american continent to the other for the same price as I pay in petrol
(gas) to sit in traffic for 5 minutes. (teach me to be european I guess ;-)
and boy do I need (read want) a new car :-P
I also turned on E_NOTICE in the same time frame, so they had a LOT of
bugs to fix :-)
thanks for another great story from the trenches Richard :-)
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
