https://ru.wikipedia.org/wiki/u:Basicowes has "autoreview" right (Flagged Revs) in ruwiki. He has used contenttranslation many times, but today he got error: "Only autoreview users could use ContentTranslation in ruwiki".
Description
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Fix autoreview permission check to support FlaggedRevs rights | mediawiki/extensions/ContentTranslation | master | +14 -4 |
Related Objects
Event Timeline
Quoting the exact message rather than (or in addition to) an English translation is always helpful, since it can be searched for. Did he get this error message? If yes, that’s probably a bug in the abuse filter (or AbuseFilter itself).
No. Some time ago ruwiki requested a change in ContentTranslation settings, allowing only "autoreview" users to use this tool (due to many low-quality translations by new users)
Then, again, please quote the original (Russian) message, so that it can be searched for. It would also be helpful if you could mention the task of the requested change – both for cross-reference and to make it easier to find out what went wrong.
https://ru.wikipedia.org/wiki/Project:Форум/Технический#Переводчик
"В русской Википедии использование инструмента перевода доступно только автопатрулируемым"
Change #1227814 had a related patch set uploaded (by Shivaansh Singh; author: Shivaansh Singh):
[mediawiki/extensions/ContentTranslation@master] Fix autoreview permission check to support FlaggedRevs rights
Thanks! It’s https://ru.wikipedia.org/wiki/MediaWiki:Contenttranslation-summary, and I think it appears to everyone, regardless of whether the user has autoreview right or not. (It’s meant by developers to be a generic description of the special page, so ruwiki is sort of abusing it for the error message – and while there is nothing wrong with this abuse from a technical viewpoint, it can lead to confusion, as you can see.)
I tried to understand the village pump discussion using Google Translate, but I’m not sure: is Basicowes really unable to use the tool, or did he just get confused by the message, and didn’t even attempt to use it?
Could you please add this? Or are you unable to find it anymore?
They already identified a problem, but I have major doubts the problem they identified exists to begin with. This is why I ask you to confirm with Basicowes whether he is really unable to use the interface. (Also, the patch in its current state would probably cause more problems than what it solves, so it would require a rewrite almost from scratch. I’d like to save the work of this rewrite if there’s nothing to fix.)
Okay, then I’ll assume there was no error to begin with (there were no deployments yesterday, so if it would have been a software bug, it couldn’t have been fixed yesterday); rather, scared off by the message, he didn’t actually attempt to use the tool earlier this week.
By the way, I suggest you (the ruwiki community) to rephrase https://ru.wikipedia.org/wiki/MediaWiki:Contenttranslation-summary in a way that makes it clearer that its appearance doesn’t imply that the user indeed has no permission to use the tool. Or use some CSS trickery (potentially involving https://ru.wikipedia.org/wiki/MediaWiki:Group-autoreview.css) to hide the message for members of the autoreview group.
Change #1227814 abandoned by Shivaansh Singh:
[mediawiki/extensions/ContentTranslation@master] Fix autoreview permission check to support FlaggedRevs rights
@Tacsipacsi user says the problem was real, a button could not be pressed: https://ru.wikipedia.org/w/index.php?curid=148270&diff=151216329&oldid=151215693
Okay. Then my next question would be whether there are any JavaScript error messages – which of course he cannot answer, since the error is gone. You could ask him, though, to collect them in case the error comes back. (An unpressable button can have many causes: other than a bug in the ContentTranslation code, it can be a conflicting other extension, conflicting gadget or user script, conflicting browser extension etc. An error message can help telling these apart.)
I don’t think so. The error is not currently reproducible, so we couldn’t tell whether the patch (or any other patch) fixes it.