Last modified: 2013-04-29 07:10:58 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 T49811, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47811 - Local account creation of Translation Notification Bot on wikidatawiki needed
Local account creation of Translation Notification Bot on wikidatawiki needed
Product: MediaWiki extensions
Classification: Unclassified
TranslationNotifications (Other open bugs)
All All
: Normal major (vote)
: ---
Assigned To: Niklas Laxström
Depends on: 44210
  Show dependency treegraph
Reported: 2013-04-29 00:19 UTC by Vogone
Modified: 2013-04-29 07:10 UTC (History)
7 users (show)

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


Description Vogone 2013-04-29 00:19:57 UTC
Please unify the SUL account "Translation Notification Bot" to wikidatawiki. Otherwise local bot flagging is impossible as Special:UserRightManagement cannot recognize the bot.

Thanks in advance,

Comment 1 Kunal Mehta (Legoktm) 2013-04-29 00:22:42 UTC
Confirmed. The account doesn't exist on Wikidata and does not show up on [[m:Special:CentralAuth/Translation_Notification_Bot]].
Comment 2 Siebrand Mazeland 2013-04-29 00:45:17 UTC
Niklas, can you please pick this up?
Comment 3 Nemo 2013-04-29 06:56:53 UTC (Special:Contributions finds one edit by unregistered user, as you can see from the missing user page link)!&uselang=en (no account on wikidata)
Comment 4 Nemo 2013-04-29 07:05:58 UTC
Fixed by sending myself a notification from Meta: I've reopened bug 44210 for the underlying problem on wikis with local translation notifications; or should we repurpose this bug?
Comment 5 Vogone 2013-04-29 07:10:58 UTC
Thank you, Nemo. I think this bug can be closed as RESOLVED now.

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