Last modified: 2010-05-15 15:42:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8258 - Wiki completely crashes, empty page
Wiki completely crashes, empty page
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.8.x
PC Linux
: High critical (vote)
: ---
Assigned To: Nobody - You can work on this!
http://www.gopal-fan.de/wiki
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-12-14 05:49 UTC by Markus
Modified: 2010-05-15 15:42 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Markus 2006-12-14 05:49:11 UTC
Since yesterday everything worked fine. Without changing anything the wiki is no
longer available: trying to access any existing page the webserver gives back
only a completly empty page.
Accessing special pages is possible. Trying to access a not existing page works too:

example: http://www.gopal-fan.de/wiki/index.php/Hauptseite
gives back an empty page

example: http://www.gopal-fan.de/wiki/index.php/xxx
this page doesn't exist and the normal wiki-page for non existing pages is
displayed...

Any ideas? Via special page I can export every existing page in a xml file:
everything looks good there....
Comment 1 Markus 2006-12-14 07:25:00 UTC
Sorry: not "since yesterday everything worked fine", i wanted to say "until
yesterday..."
Comment 2 Rob Church 2006-12-14 08:10:55 UTC
Can you check the PHP error log to see what's actually happening when the empty
page is being returned?
Comment 3 Timo Schefold 2006-12-14 10:02:44 UTC
My Problem is the same, I tried to reinstall Mediawiki but it's still the same.
The error log shows:

Warning: Cannot modify header information - headers already sent by (output
started at c:\Programme\PHP\root.php:8) in
C:\Inetpub\Mainroot\LGHWiki\includes\WebResponse.php on line 9

And this message appears 6 times. What can I do? We're using the latest version
of Mediawiki and we also have the latest PHP version. The Webserver is running
on Windows 2000.
Comment 4 Timo Schefold 2006-12-14 10:03:21 UTC
My Problem is the same, I tried to reinstall Mediawiki but it's still the same.
The error log shows:

Warning: Cannot modify header information - headers already sent by (output
started at c:\Programme\PHP\root.php:8) in
C:\Inetpub\Mainroot\LGHWiki\includes\WebResponse.php on line 9

And this message appears 6 times. What can I do? We're using the latest version
of Mediawiki and we also have the latest PHP version. The Webserver is running
on Windows 2000.
Comment 5 Timo Schefold 2006-12-14 10:03:42 UTC
My Problem is the same, I tried to reinstall Mediawiki but it's still the same.
The error log shows:

Warning: Cannot modify header information - headers already sent by (output
started at c:\Programme\PHP\root.php:8) in
C:\Inetpub\Mainroot\LGHWiki\includes\WebResponse.php on line 9

And this message appears 6 times. What can I do? We're using the latest version
of Mediawiki and we also have the latest PHP version. The Webserver is running
on Windows 2000.
Comment 6 Timo Schefold 2006-12-14 10:05:16 UTC
Whoo sorry I didn't want to send this three times but now i'm not able to delete
it :(
Comment 7 Rob Church 2006-12-14 10:15:16 UTC
Timo, do you have PHP configured to include a particular file at the start of
every script (auto_prepend_file in PHP.ini)? It seems that "root.php", which is
nothing to do with MediaWiki, is being executed, and it's producing some output
which blocks us sending headers.

This may or may not be the same problem that Markus is having.
Comment 8 Markus 2006-12-14 10:28:19 UTC
(In reply to comment #2)
> Can you check the PHP error log to see what's actually happening when the empty
> page is being returned?

I have opened a support ticket at my webhoster to get the information out of the
log files. It's a shared webhosting environment, so I think only the provider
has access to it... Or is it possible for me as a client to look into these
logs?! Where are they normally stored?
Comment 9 Raj Shekhar 2006-12-14 10:52:12 UTC
Yes, you can get the vaule.  In a file (say info.php), put in this line
<?php phpinfo(); ?>
and then access that page from your browser.  Check what value it has for
auto_prepend_file (just seach for that string)
Comment 10 Timo Schefold 2006-12-14 11:10:44 UTC
Thank you very much for your fast help, it works now without a problem!
Comment 11 Markus 2006-12-14 11:26:46 UTC
My provider (all-inkl.com) has fixed the problem: it was a problem with zend
optimizer. They have installed an update and now it works fine again. Thanks for
your help!
Comment 12 Rob Church 2006-12-14 21:44:07 UTC
\o/ on both counts :)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links