Description:
------------
Since I cannot edit or add a comment to bug #23844, I'll 
say it here: I respectfully disagree with goba@php.net that 
that bug is a duplicate of the issue found in #23652.

Having read both of the bug reports a few times, it appears 
that #23844 refers to instances where users attempt to 
access *incorrect* function names as php.net/badfuncname,

...whereas #23652 has more to do with users being 
erroneously 'bounced' between google and php mirror sites, 
primarily as a result of broken links from *within* the PHP 
documentation itself.

* * *

re: [28 May 4:02am CDT] derick@php.net (from #23844)
"Thank you for taking the time to write to us, but this is 
not a bug..."

Maybe things were different at the time of this writing, 
but your 'bug reporting system' now includes a "type of 
bug: php.net website error" entry, so, it  is justified.

* * *

re: [16 May 2:57am CDT] derick@php.net (from #23652)

"website problems can't be critical."

No, but they can surely be annoying as hell to a LOT of 
people who try and use the functionality on a REGULAR 
basis. So multiply that frustration level by the number of   
loyal, albeit forgetful, PHP users that regularly look up 
functions on your site. How long before it reaches a 
'critical' mass? Do you wonder why you seem to be getting a 
lot of reports of this bug, or something just like it?

 I have a lot of respect for you, Derick, but this is one 
of those stupid fixes that will make a lot of people happy. 
I for one do not know exactly how the site works now, as 
opposed to how it worked before the Google integration. But 
I do know that for me, and many others, there is no 
perceived benefit, at least not for php.net/brokenfuncname.

* * *

Original 'bug report' before seeing the bug system match 
about 12 other google-related complaints:

* * *

I fell in love with using php.net/funcname capability as a 
nice shortcut.
However, I did not always remember the function's name 
correctly.

Previous versions of the site would find best matches from 
pages of the site. For example;  

http://us2.php.net/manual-lookup.php?pattern=isstring&lang=
en

Even if I did not find a match I liked, I could still 
change the php.net site URL so I could try to look again.
Now, the site just takes me to google and gives me a 
useless error page. I cannot even hit 'back' because of the 
way in which I am redirected. So I have to go to php.net 
and THEN type the search in the box after waiting for the 
site to load. That kills the usefullness of the shortcut.

It seems like a small thing, but it's something I miss 
quite a bit. I had a nice command line -> web browser 
script set up to perform the lookup.

I am not the only person, either... there are always a few 
others in the efnet #php channel who respond in the same 
way whenever I mention it. So I know I'm not alone in 
saying this.

I love PHP and I love php.net... but this is just a bad 
step for you guys. I hope you put it back the way it was.