#27438 [Bgs->Opn]: browscap.ini causes error

ID: 27438 User updated by: php_bug_27438 at garykeith dot com Reported By: php_bug_27438 at garykeith dot com -Status: Bogus +Status: Open Bug Type: Documentation problem Operating System: All PHP Version: Irrelevant New Comment: It does crash PHP unless you have modded my file to prevent it. The simple fact is get_browser() does not work the same way browscap.dll does and until it does get_browser() is broken, will continue to crash PHP and cause me nothing but grief. Why do you have to argue with me about this? There is a link in your documentation to my website and I do not want PHP to link to my website anymore. Please remove the link. Previous Comments: ------------------------------------------------------------------------ [2004-02-29 14:41:13] nlopess@php.net It does NOT crash PHP. ------------------------------------------------------------------------ [2004-02-29 14:39:59] php_bug_27438 at garykeith dot com This is not bogus. There is a link in your documentation page to a browscap.ini file that is guaranteed to crash PHP. All I want is my link removed. If you can't help with that then please stay out of this. ------------------------------------------------------------------------ [2004-02-29 12:55:49] nlopess@php.net Duplicate. see #27372 ------------------------------------------------------------------------ [2004-02-29 11:15:31] php_bug_27438 at garykeith dot com All I want is my link removed. If you cannot help me with that then please stay out of this bug report. I will not rehash the problems and slights that led to this here as it's an inappropriate place to do so. ------------------------------------------------------------------------ [2004-02-29 11:00:18] nlopess@php.net When PHP starts give an error on line 693: "browser=Yahoo! Slurp" if you replace it by: "browser=Yahoo Slurp" everything works fine. So, maybe reclassify as something else than documentation problem. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/27438 -- Edit this bug report at http://bugs.php.net/?id=27438&edit=1