ID: 27438
User updated by: php_bug_27438 at garykeith dot com
Reported By: php_bug_27438 at garykeith dot com
Status: Assigned
Bug Type: Documentation problem
Operating System: All
PHP Version: Irrelevant
Assigned To: kennyt
New Comment:
Apology accepted. Thank you. I'm sorry I misunderstood to whom you were
directing that comment.
IMO, the only realistic option to deal with this situation over the
next several years is for me to provide an alternate browscap.ini file
that takes PHP deficiencies into account.
I've been unwilling to do that because of how I've been treated by
everyone at PHP with three exceptions: you, Jay and Ryan.
Previous Comments:
------------------------------------------------------------------------
[2004-02-29 22:49:47] [EMAIL PROTECTED]
Wow, I'm sorry. That "Happy flaming!" was directed at derick at
php.net, not you. I guess I assumed you watch php.net bug reports. ;-)
I'd like to cooperate with you, while still helping php.net visitors to
find a browscap.ini file. Again, sorry to be offensive. :)
------------------------------------------------------------------------
[2004-02-29 22:41:45] php_bug_27438 at garykeith dot com
I made a typo:
There's also the issue of ampersands and pound signs in browser names
and pound signs in version numbers.
This should have stated:
There's also the issue of ampersands and parenthesis in browser names
and pound signs in version numbers.
------------------------------------------------------------------------
[2004-02-29 22:39:56] php_bug_27438 at garykeith dot com
There are more problems than just replacing an exclamation point.
There's also the issue of ampersands and pound signs in browser names
and pound signs in version numbers. These will all cause get_browser()
to return bogus information and yet according to the MS spec for
browscap.ini these are all valid characters.
How do you expect to get any cooperation from me when you end your
message with "happy flaming!"?
This nlopess character barges in on my attempt to get a link removed
and essentially, once again, tries to blame the whole situation on me.
Then Derick comes along and calls me an ass. My attempts to post a note
in the documentation section urging your users not to use my file keep
getting deleted. These are small examples of what I've gotten in
exchange with my cooperation with PHP. And now I'm the flamer?
We all have our breaking point. I've reached mine.
I will continue to redirect that link back to your own website. Be glad
I am ethical enough not to redirect your users to some gross adult
website.
Make sure you note the new restrictions in my Terms of Service.
Please govern yourselves accordingly.
------------------------------------------------------------------------
[2004-02-29 21:29:00] [EMAIL PROTECTED]
Uh, that is, of course, if you're willing to let us link with this
added information.
------------------------------------------------------------------------
[2004-02-29 21:21:14] [EMAIL PROTECTED]
We could create a new manual page detailing the process of stripping
characters PHP can't handle ('!'). Replace the (2?) links to the site
with links to that page, which would contain the site's URL beneath a
warning. Since that Yahoo! entry is the only bug-provoking one, even
users would find it easy to clean up the file.
Happy flaming!
------------------------------------------------------------------------
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
