Last modified: 2011-04-30 01:20:53 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 T25468, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 23468 - Special:AllMessages broken by custom system messages
Special:AllMessages broken by custom system messages
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.15.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-11 05:16 UTC by hai.kataker
Modified: 2011-04-30 01:20 UTC (History)
2 users (show)

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


Attachments

Description hai.kataker 2010-05-11 05:16:04 UTC
Yesterday, after long debugging, I found out that creating custom system messages (that is, new ones, not those lists by Special:AllMessages before) breaks that very special page -- it will then result in a 500 "internal server error". The Apache error log merely states "Permature end of script headers in index.php".
Because I had made more than one change when I actually noticed that the page was not working anymore, I set out to debug what I had done wrong (I had written a skin based on monobook as well as installed some extensions).
I tracked the error down so far that I can say it disappears when I comment out lines 196-200 in file /includes/specials/SpecialAllmessages.php (that is the if-statement creating the appropriate Talk link for each message); to suppress error messages complaining about an empty $talkLink variable you'll have to initialize it to an empty value instead of the if-statement.
My debugging also revealed that in the compound array used to create the messages list, all my custom (new) system messages were not included -- curious that they should still crash the script.
Playing around more with it revealed that the error is either hidden in this file directly, or something more deeper in the language/messages/i18n framework.
If someone could look into this, I'd be really grateful, because even though the rest of the wiki works fine, that error is a thorn in my side (and also, my skin is based on several custom messages).

Regards,
Patrick
Comment 1 OverlordQ 2010-05-11 05:27:14 UTC
It usually helps to include what the actual error message was so we can tell if it's an actual error or a result of your edits.
Comment 2 Roan Kattouw 2010-05-11 11:07:06 UTC
(In reply to comment #0)
> Yesterday, after long debugging, I found out that creating custom system
> messages (that is, new ones, not those lists by Special:AllMessages before)
> breaks that very special page -- it will then result in a 500 "internal server
> error". The Apache error log merely states "Permature end of script headers in
> index.php".
This is a bug in one of your extensions or custom code. One of your .php files (MediaWiki or extensions) has a newline before the opening <?php tag or after the closing ?> tag (the latter is redundant and can be omitted). That newline has to be removed.
Comment 3 hai.kataker 2010-05-11 13:29:23 UTC
@OverlordQ: Yea, sorry about that. Will do next time >.>

@Roan Kattouw: I triple-checked all files that I changed and/or added, and none of these have those superfluous newlines.

But hey, either some of the many caches between me and the server is screwing with me right now, or it works (without me really changing anything) -- what I did do was comment out some parts of the skin, then un-commenting them to localize the source of the error, but twice it appeared, and now it's completely gone without any substantial change to the code.
strange :/

I also have to admit that I didnt do all i could have done to debug it properly, but I was getting frustrated by a seemingly un-founded error with no hint as to where it came from >.>

Thanks anyway,
regards,
Patrick
Comment 4 hai.kataker 2010-05-11 13:57:41 UTC
I just noticed that the bug is caused by the "Configure" extension, though I could not find the reason.
Even with my skin removed, AllMessages still wont work. (The previously seeming connection was probably caused by caching.)
I will check their bug tracker and report this there if necessary.

Sorry again for falsely reporting here.

Regards,
Patrick

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


Navigation
Links