Last modified: 2010-05-15 15:41:11 UTC
One sees a raw <p> in this zh-tw message:
$ w3m -dump http://localhost/mediawiki/index.php?title=Current_events\&oldid=9999999999999|
It would be useful if you gave the exact name of the message. <p> in messages
isn't necessarily a problem, since many are included without escaping.
If this is reported against version 1.7.1 for a reason (because it appears on
1.7.1) then it's possible it's been fixed in a later version. In that case, the
fix won't be backported to the 1.7 branch.
If, on the other hand, it's still current in 1.9alpha, please bump the version
number and tell us which message it is.
(reply copied from mailing list)
>> It would be useful if you gave the exact name of the message.
>That brings up another problem, how is the user to figure that out?!
>Here we see in an uselang=en dump, which doesn't have the bug, that
>the page we are looking has all the trappings of the real
>Current_events page, and unless one looks closely, one thinks it is
>the Current_events page.
> $ w3m -dump
> Current events
> From 台掃
> Jump to: navigation, search
> The database did not find the text of a page that it should have found, named
> "Current events,oldid=2147483647".
> This is usually caused by following an outdated diff or history link to a page
> that has been deleted.
> If this is not the case, you may have found a bug in the software. Please
> report this to an administrator, making note of the URL.
> Retrieved from "http://localhost/mediawiki/index.php?title=Current_events"
>And not even in the HTML source can one find the message name you
>want. Any additional bugs I mention please report, if worthy.
>OK, looking through Allmessages I dug it up:
>$ w3m -dump http://localhost/mediawiki/index.php?title=媒體維基:Missingarticle\
>The problem must be they forgot to close the <p>'s, so the 2nd one
>ends up rendered. Ah ha! So do validate all your HTML before making
>releases. You could probably cat(1) together all the items on
>Allmessages, and send it all to the validate(1) program.
Are you running Tidy? WMF sites do, so presumably it validates for us. It is
indeed invalid XHTML, fixed in r18219.
>By the way, in
>one can click on a link offered,
>but that won't get us anywhere, nor will
>Indeed, the /en is not working.
That's intended behavior, although it's pretty odd. Messages that don't exist
in the database are retrieved from the message files, but the page doesn't
Seems this issue has been fixed in r18219 by Simetrical.