PHP :: Bug #40333 :: DOM Functions page at php.net is down

Bug #40333	DOM Functions page at php.net is down
Submitted:	2007-02-02 19:49 UTC	Modified:	2007-02-02 20:41 UTC
From:	chuck dot hoffman at t8design dot com	Assigned:
Status:	Not a bug	Package:	Website problem
PHP Version:	Irrelevant	OS:	doesn't matter
Private report:	No	CVE-ID:	None

View Developer Edit

Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.

Password:

Status:
Package:
Bug Type:
Summary:
From:	chuck dot hoffman at t8design dot com
New email:
PHP Version:		OS:

New Comment:

[2007-02-02 19:49 UTC] chuck dot hoffman at t8design dot com

Description:
------------
attempted to go to the page about DOM functions using a browser bookmark.  Received a PHP error message about "unexpected T-STRING."

Tried again to reach same page by searching for DOM from the search box at the php.net home page.  Same result.

http://us2.php.net/manual/en/ref.dom.php





Reproduce code:
---------------
http://us2.php.net/manual/en/ref.dom.php

Expected result:
----------------
Expected the page about DOM that I was looking at just yesterday.

Actual result:
--------------
Interruption of my work.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports

[2007-02-02 19:58 UTC] 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

[2007-02-02 20:08 UTC] 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 20:39 UTC] 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:40 UTC] 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:41 UTC] 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:41 UTC] chuck dot hoffman at t8design dot com

LOL... I'm just not going to touch that sequence ;-)

	php.net \| support \| documentation \| report a bug \| advanced search \| search howto \| statistics \| random bug \| login
go to bug id or search bugs for


Copyright © 2001-2026 The PHP Group All rights reserved.	Last updated: Tue Jun 16 11:00:01 2026 UTC