Last modified: 2013-09-04 11:51:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T31972, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 29972 - "malformed header from script. Bad header=...have pagelinks" errors with the new installer
"malformed header from script. Bad header=...have pagelinks" errors with the ...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.17.x
All All
: Normal normal with 4 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2011-07-20 02:22 UTC by Emufarmers
Modified: 2013-09-04 11:51 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Emufarmers 2011-07-20 02:22:46 UTC 
I've seen two reports of the same problem:

http://www.mwusers.com/forums/showthread.php?17142-Internal-Server-Error-During-Upgrade
http://www.mwusers.com/forums/showthread.php?17187-Upgrade-to-1.17.0-covert-tables-problem-and-inconsistent-page-layout

"malformed header from script. Bad header=...have pagelinks; skipping ol"

Seems goofy.
Comment 1 Brion Vibber 2011-07-20 17:56:54 UTC 
This output line comes from convertLinks, which is a Maintenance subclass...

...it does the output with its $this->output() method, which on Maintenance looks like it tries to output *directly* to stdout, instead of a generic 'print' or 'echo'.

It's possible that this is interfering with output & header buffering, especially if this is a PHP-as-CGI or FastCGI setup.
Comment 2 mickeyf 2011-09-22 18:03:17 UTC 
My hosting co is soon dropping support for php 5.2, so I will be forced to upgrade to mw 1.17. I imagine I'm not alone, and there are now more reports of this on http://www.mwusers.com/forums. I really want the upgrade to be trouble free. Up voted!
Comment 3 Andre Klapper 2013-03-18 01:49:29 UTC 
Is this still an issue? I haven't found any recent reports of this...
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links