Page MenuHomePhabricator

Signature containing only a contributions link not recognized by DiscussionTools
Closed, ResolvedPublicBUG REPORT

Description

Steps to reproduce

  1. Open https://hu.wikiquote.org/w/index.php?title=Vita:Magyar_nyelv%C5%B1_palindromok_list%C3%A1ja&oldid=55057&dtenable=1&dtdebug=1.

Actual result

  1. The debug mode highlights only one comment (mine). I had to write that comment using the legacy full-page editor, as there was no reply button.

Expected result

  1. The debug mode highlights two comments (one from the anon, one from me). I could write my comment using the Reply Tool.

Other information

When I modify the wikitext to include a link in the anon’s signature to their talk page, the preview shows that two comments are recognized. When I conversely modify my signature to include only a link to my contribs (and neither to my user page nor to my talk page), the preview shows that there are no comments recognized. So it looks like, contrary to the signature requirements, a contribs page link isn’t enough for DiscussionTools to recognize the comment.

Event Timeline

It does work elsewhere with just the contributions link.

Having not dug into this properly yet, my gut suspicion would be that it's because huwiki's URL for the contributions page contains non-ascii characters and we might be comparing them while they're still URLencoded. (i.e. Szerkesztő_közreműködései compared to Szerkeszt%C5%91_k%C3%B6zrem%C5%B1k%C3%B6d%C3%A9sei)

I would say it some underscore vs. space issue. Aliases are stored with underscores, the compare against parts of Title::getText would be with spaces.

Change 880534 had a related patch set uploaded (by Umherirrender; author: Umherirrender):

[mediawiki/extensions/DiscussionTools@master] LanguageData: Use special page alias with spaces

https://gerrit.wikimedia.org/r/880534

Change 880534 merged by jenkins-bot:

[mediawiki/extensions/DiscussionTools@master] LanguageData: Use special page alias with spaces

https://gerrit.wikimedia.org/r/880534

Thanks for the quick patch, it’s already fixed in production (on the page linked from the description)!

Thanks for the quick patch, it’s already fixed in production (on the page linked from the description)!

Looks good!