Disabling error docref stuff by default

php.internals

Rasmus Lerdorf

23 years ago
Could we disable these error links by default? As people are slowly migrating to 4.3, it is becoming very clear that all sorts of people are getting confused about these. Especially when a spam web site spews one of these and irate users trying to unspam themselves end up blaming webmaster@php.net for their troubles. Or just people following a link from one of these and emailing us about some error on some website out there that we have nothing to do with. I never really bought into the usefulness of this feature, but I figured it couldn't hurt. Now I see how it does actually hurt. -Rasmus

Jon Parise

23 years ago
On Thu, Mar 13, 2003 at 01:10:10AM -0800, Rasmus Lerdorf wrote:
> Could we disable these error links by default? As people are slowly > migrating to 4.3, it is becoming very clear that all sorts of people are > getting confused about these. Especially when a spam web site spews one > of these and irate users trying to unspam themselves end up blaming > webmaster@php.net for their troubles. Or just people following a link > from one of these and emailing us about some error on some website out > there that we have nothing to do with.
I'm inclined to agree. What if it were made (bu default) on the error_reporting level? E_ALL would use the docrefs but "lower" levels would not (e.g. E_FATAL). Or a new INI option (docref_errors or docref_enable)?
-- Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)

Jani Taskinen

23 years ago
On Thu, 13 Mar 2003, Jon Parise wrote:
>On Thu, Mar 13, 2003 at 01:10:10AM -0800, Rasmus Lerdorf wrote: > >> Could we disable these error links by default? As people are slowly >> migrating to 4.3, it is becoming very clear that all sorts of people are >> getting confused about these. Especially when a spam web site spews one >> of these and irate users trying to unspam themselves end up blaming >> webmaster@php.net for their troubles. Or just people following a link >> from one of these and emailing us about some error on some website out >> there that we have nothing to do with. > >I'm inclined to agree. What if it were made (bu default) on the >error_reporting level? E_ALL would use the docrefs but "lower" levels >would not (e.g. E_FATAL). > >Or a new INI option (docref_errors or docref_enable)?
NO MORE INI OPTIONS!! There are so many options now that it's getting a hell to QA anything anymore..for example those session.bug_compat_42 and session.bug_compat_warn options. And what's wrong with 'display_errors=off' ??? No production website should have that set to 'ON' anyway. --Jani

Rasmus Lerdorf

23 years ago
> No production website should have that set to 'ON' anyway.
That's true, but they obviously do and as a result we are wasting valuable cycles dealing with people who are screaming at us for whatever content they ran across that they link directly to us through one of these links. I have had 3 of these in the past 4 days I had to deal with. One is threatening to sue. I don't need this headache. -Rasmus

Sterling Hughes

23 years ago
On Thu, 2003-03-13 at 04:48, Rasmus Lerdorf wrote:
> > No production website should have that set to 'ON' anyway. > > That's true, but they obviously do and as a result we are wasting valuable > cycles dealing with people who are screaming at us for whatever content > they ran across that they link directly to us through one of these links. > I have had 3 of these in the past 4 days I had to deal with. One is > threatening to sue. I don't need this headache. >
Seriously threatening to sue? Well, I for one vote you put his post on Derick's stupid user requests page. :) I'm with Rasmus here, the doc stuff has no really benefit (except inserting annoying hyperlinks in cli mode), and no it has a signifigant disadvantage. <evil mode="production"> How about we have a is_production php.ini option, that turns on all the necessary production environment ini settings (like turning display_errors = OFF </evil> -sterling
> -Rasmus
-- Good judgement comes from experience, and experience comes from bad judgement. - Fred Brooks

Derick Rethans

23 years ago
On Thu, 13 Mar 2003, Rasmus Lerdorf wrote:
> > No production website should have that set to 'ON' anyway. > > That's true, but they obviously do and as a result we are wasting valuable > cycles dealing with people who are screaming at us for whatever content > they ran across that they link directly to us through one of these links. > I have had 3 of these in the past 4 days I had to deal with. One is > threatening to sue. I don't need this headache.
We can chose to just ignore them too? And I wonder, why does somebody want to sue? Derick
-- "my other box is your windows PC" ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ -------------------------------------------------------------------------

Rasmus Lerdorf

23 years ago
> We can chose to just ignore them too? And I wonder, why does somebody > want to sue?
The guy in question wants to sue somebody and he is flailing randomly looking for whatever tenuous association between his ignorance and an approachable entity. Sueing us for providing PHP to someone who uses it for some nefarious purpose is just like sueing the farmer who grew the food for that same someone. It makes absolutely no sense, and a stern "bugger off" letter from a lawyer would make it go away. But he got to us in the first place through one of these docref links, and since I need to vent my frustration somewhere as well, I have chosen to take it out on that damned docref link that brought me this pain. (Realistically, I'm 99% sure he is all talk) -Rasmus

Derick Rethans

23 years ago
On Thu, 13 Mar 2003, Jon Parise wrote:
> On Thu, Mar 13, 2003 at 01:10:10AM -0800, Rasmus Lerdorf wrote: > > > Could we disable these error links by default? As people are slowly > > migrating to 4.3, it is becoming very clear that all sorts of people are > > getting confused about these. Especially when a spam web site spews one > > of these and irate users trying to unspam themselves end up blaming > > webmaster@php.net for their troubles. Or just people following a link > > from one of these and emailing us about some error on some website out > > there that we have nothing to do with. > > I'm inclined to agree. What if it were made (bu default) on the > error_reporting level? E_ALL would use the docrefs but "lower" levels > would not (e.g. E_FATAL).
I like this magic, but it isn't really our problem I think. People who have error messages on production boxes... yuck.
> Or a new INI option (docref_errors or docref_enable)?
hmm, don't think that's a good idea, it adds another ini-setting... Derick
-- "my other box is your windows PC" ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ -------------------------------------------------------------------------