Closed
Bug 407022
Opened 18 years ago
Closed 18 years ago
developer-test.m.o PHP error
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wenzel, Assigned: oremj)
References
()
Details
developer-test, the recently built dev instance of MDC, is broken:
The front page works, however when you click any link, you get an empty page. The error log on the dev box reads as follows:
PHP Fatal error: Class 'DOMDocument' not found in /data/www/developer.mozilla.org/mediawiki/docs/includes/Parser.php on line 2966, referer: http://developer-test.mozilla.org/
Please look into what's happening here (is a required library missing or something?). Thanks.
| Reporter | ||
Comment 1•18 years ago
|
||
CCing people, sorry for the bugspam.
Comment 2•18 years ago
|
||
DOMDocument is part of the PHP5 core -- does phpinfo() tell us anything interesting?
| Reporter | ||
Comment 3•18 years ago
|
||
Thanks for the hint: phpinfo() mentions a build option '--disable-dom'. This is probably the culprit I assume?
Comment 4•18 years ago
|
||
If I were a betting man, I'd say so. IT Friends: are these the same php5 packages used in live? Do we have a separate package that we install to get the DOM stuff?
| Reporter | ||
Comment 5•18 years ago
|
||
(unchecking group restrictions, I hope others can see the bug now)
CC list accessible: false
Not accessible to reporter
Updated•18 years ago
|
Group: infra
| Assignee | ||
Updated•18 years ago
|
Assignee: server-ops → oremj
| Assignee | ||
Comment 6•18 years ago
|
||
Installed the php-xml package. Also, there was a merge to mediawiki trunk conflict in includes/Linker.php that I fixed. Whenever there is a php error first run `svn status` in /data/www/phase3 to check for conflicts. If there are any either svn revert or fix the conflict then run /data/bin/developer.mozilla.org/bin/update-to-trunk.sh
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•