dewiki has added a link to message wrongpassword which is shown as plain html when input a wrong password on Special:ChangeEmail.
Version: 1.23.0
Severity: normal
dewiki has added a link to message wrongpassword which is shown as plain html when input a wrong password on Special:ChangeEmail.
Version: 1.23.0
Severity: normal
Status | Subtype | Assigned | Task | |
---|---|---|---|---|
· · · | ||||
Invalid | None | T40638 [DO NOT USE] Interface messages needing rewording or documentation and other issues with existing messages [superseded by #Voice_&_Tone] | ||
Invalid | None | T58522 Remove 'wrongpassword' message reuse on Special:ChangeEmail | ||
· · · |
"Das Passwort und/oder das Sicherheitswort (CAPTCHA) ist falsch oder wurde nicht eingegeben. Bitte versuche es erneut oder lass dir das Passwort per E-Mail zusenden. Du kannst auch <a href="//de.wikipedia.org/wiki/Spezial:Userlogin/signup">ein neues Benutzerkonto erstellen</a>"
Inconsistency between wikitext and HTML... what a surprise.
UserloginTemplate expects its messages in HTML:
<?php $this->html( 'message' ); ?>
Whereas SpecialChangeEmail expects wikitext:
$this->getOutput()->wrapWikiMsg( "<p class='error'>\n$1\n</p>", $msg );
I guess we just change ChangeEmail to expect HTML, and officially make wrongpassword a HTML message.
sigh...
Change 95848 had a related patch set uploaded by TTO:
Make Special:ChangeEmail use HTML messages instead of wikitext
Change 95848 abandoned by TTO:
Make Special:ChangeEmail use HTML messages instead of wikitext
Reason:
Per Nikerabbit. Change is not going to be accepted.
Adding many blockers of bug 38638 to the list of "easy" bugs, to mark them as candidates for [[mw:Google Code-in]] tasks (gci2013). If you think this bug is not suitable, remove the keyword.
I don't think that something should be changed here. The wiki markup for external references[1] can be used as an alternative for this message.
[1]: https://meta.wikimedia.org/wiki/Help:HTML_in_wikitext#Permitted_HTML
See comment 2, the message is used at two places in core, at the first place it is rendered as wikitext, at the other place the message is rendered as html, there is no way to create a message which is working in both cases, because the one render does not know about [], the other not about <a></a>.
(In reply to comment #7)
See comment 2, the message is used at two places in core, at the first place
it
is rendered as wikitext, at the other place the message is rendered as html,
there is no way to create a message which is working in both cases, because
the
one render does not know about [], the other not about <a></a>.
Then the message must be split. It wouldn't be bad to also get SpecialChangeEmail to not use an HTML message though.
Change 104797 had a related patch set uploaded by Umherirrender:
Add message wrongpassword as html on Special:ChangeEmail
Change 104797 abandoned by Umherirrender:
Add message wrongpassword as html on Special:ChangeEmail
Reason:
Language team prefers a new message, will rewrite bug summary.
Language team prefers a new message, so rewrite the bug summary to document the fact. Resetting to NEW, because the existing patch is no longer useful.
Similar to bug 53655
Change 121367 had a related patch set uploaded by Ganeshaditya1:
Add message wrongpassword as html and remove its reuse in Special:ChangeEmail
Change 121367 abandoned by Ganeshaditya1:
Add message wrongpassword as html and remove its reuse in Special:ChangeEmail
Reason:
Messed up ..
@TerraCodes: Please avoid contentless pinging.
If you have a specific question, please ask it. If you ask a specific person, please mention their name. Thanks.
Hmm, I wonder if this task is still valid/actual. Special:ChangeEmail seems to doesn't reuse wrongpassword anymore. As far as I know, Special:ChangeEmail should also use AuthManager's reauthentication feature to make sure, that an use is allowed to change his e-mail address. In case of a wrong password, the same message as for login should be used, which sounds correct.
I rather would call it invalid now, as we haven't changed anything to fix it explicitly. As far as I know, the code was superseeded by AuthManager. This was in commit 02b2d8da63f6dc267a23cfba29b8c59330f82d6c, the old implementationw as completely removed in 854a462dc0aef59e1c26c057792b8a9214449af5. So the original task (as I understand it) is invalid :)