ID: 19902 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Analyzed +Status: Closed Bug Type: Scripting Engine problem Operating System: All Win PHP Version: 4.2.3 New Comment:
This bug has been fixed in CVS. In case this was a PHP problem, snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. In case this was a documentation problem, the fix will show up soon at http://www.php.net/manual/. In case this was a PHP.net website problem, the change will show up on the PHP.net site and on the mirror sites in short time. Thank you for the report, and for helping us make PHP better. The broken browscap.ini is no longer being bundled with Windows distributions of PHP. The documentation now links to a web site where a working browscap.ini, which is frequently updated can be obtained. Previous Comments: ------------------------------------------------------------------------ [2002-10-14 21:42:48] [EMAIL PROTECTED] Hello Iliaa Thank you for acknowledging my initial "Suggestion". I do not recall exactly when I first came across a bundled browscap.ini with "not valid entries", but it must have been quite some time (php releases) ago. Probably browscap.ini is a static item in the bundling process and thus the invalid line 8206 got propagated with every (win) distribution. There does not seem to be a reason, why future releases of PHP should contain an uncorrected version of browscap.ini. Thanks again. Kind regards Juri ------------------------------------------------------------------------ [2002-10-14 19:44:03] [EMAIL PROTECTED] Actually after checking it seems the Windows distribution contains a bundled browscap.ini file. My applogies. I'll look into why we are bundling this file and what can be done to correct it. ------------------------------------------------------------------------ [2002-10-14 19:35:26] [EMAIL PROTECTED] browscap.ini is NOT released by PHP, this file can be obtained from various sources on the net none of which are related to the PHP project. PHP merely has a generic ini parser that amongst other things can parse browscap.ini files. For whatever reason those files are not always completely compatible or properly formatted. Thus they sometimes cannot be parsed completely by the PHP's parser. This means that the incompatible lines should either be removed or altered. ------------------------------------------------------------------------ [2002-10-14 19:24:52] [EMAIL PROTECTED] Hello Iliaa Why do you release a browscap.ini with invalid entries with every new distribution of PHP? Everybody using browscap.ini is forced to edit it, before he may use it. Cumbersom... Kind regards Juri ------------------------------------------------------------------------ [2002-10-14 18:54:22] [EMAIL PROTECTED] Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php The browscap.ini sometimes contains not valid entries not supported by PHP's ini parser. Simply remove those lines, there are usually very few of those. ------------------------------------------------------------------------ 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/19902 -- Edit this bug report at http://bugs.php.net/?id=19902&edit=1
