#40333 [Bgs]: DOM Functions page at php.net is down

ID: 40333 User updated by: chuck dot hoffman at t8design dot com Reported By: chuck dot hoffman at t8design dot com Status: Bogus Bug Type: Website problem Operating System: doesn't matter PHP Version: Irrelevant New Comment: LOL... I'm just not going to touch that sequence ;-) Previous Comments: ------------------------------------------------------------------------ [2007-02-02 20:41:03] nlopess@php.net Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Thank you for your interest in PHP. . ------------------------------------------------------------------------ [2007-02-02 20:40:03] nlopess@php.net Thank you for your bug report. This issue has already been fixed in the latest released version of PHP, which you can download at http://www.php.net/downloads.php ------------------------------------------------------------------------ [2007-02-02 20:39:48] bjori@php.net We do appreciate your bug report. This is however is a duplicate report of bug#40312 bug#40316 bug#40320 bug#40322 bug#40314 bug#40323 bug#40328 bug#40329 and bug#40303 which all describe the same problem (which in fact has nothing to do with php at all) and therefor marked as "bogus". I am deeply sorry for any inconvenience this may have caused you all. ------------------------------------------------------------------------ [2007-02-02 20:08:03] chuck dot hoffman at t8design dot com thanks, I think, but the error message in the bug you refer to as being supposedly a duplicate of this one is: * on a different page of the php.net site * gives a different line number. Which may have something to do with why it didn't appear when I searched to see if it had been previously submitted. Here's my original error message, sorry for not including it earlier: Parse error: parse error, unexpected T_STRING in /home/php/phpweb/manual/en/ref.dom.php on line 363 Since the canned response arrived so amazingly quickly, I'd be justified in concluding that you simply didn't read my original posting very carefully. However, if the two different messages, claiming to be on two different lines of code, and on two different pages, are caused by one single error in your own code, and thus both fixed by the same fix in CVS ... well, I can't very well be expected to know that, since I don't look at / work on *your* code all day, I work on mine. ------------------------------------------------------------------------ [2007-02-02 19:58:58] johannes@php.net Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Thank you for your interest in PHP. See bug#40303 ------------------------------------------------------------------------ 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/40333 -- Edit this bug report at http://bugs.php.net/?id=40333&edit=1