Last modified: 2014-02-12 23:38:23 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 T44162, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 42162 - Option to patrol changes to translated pages is offered but gives error
Option to patrol changes to translated pages is offered but gives error
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
https://meta.wikimedia.org/w/index.ph...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-15 20:39 UTC by Wiki13
Modified: 2014-02-12 23:38 UTC (History)
11 users (show)

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


Attachments

Description Wiki13 2012-11-15 20:39:09 UTC
Hi,

I seem to get error when patrolling pages on Wikidata (don't know sure if this also applies to Meta), which are using the Translate extension. If I click on "mark as patrolled" for example on https://www.wikidata.org/w/index.php?diff=463241&oldid=463230&rcid=460677 I get the following error:

You do not have permission to mark others' edit as patrolled, for the following reason:

This page cannot be updated manually. This page is a translation of page Wikidata:Introduction and the translation can be updated using the translation tool.

--Wiki13
Comment 1 Niklas Laxström 2012-11-15 20:42:49 UTC
I could add patrol to whitelist but it would be redundant with translation review feature.
Comment 2 Nemo 2012-11-15 21:05:50 UTC
I think it's completely meaningless to patrol changes to translation pages: one can and should patrol only (at most) changes to translation units; see discussion on Meta.
The simplest solution would be to disable new page/RC patrol for translation pages in the least intrusive way possible. A more complex (impossible?) solution would be to connect the translation pages revisions to their translation units equivalents so that patrolling one makes the other patrolled as well (in one or both directions): I doubt this is worth it.
The interaction with translation review is up to the wiki, I think, just as with patrolling vs. flagged revisions.
Comment 3 Kunal Mehta (Legoktm) 2013-04-12 07:23:58 UTC
(In reply to comment #1)
> I could add patrol to whitelist but it would be redundant with translation
> review feature.

IMO the main issue isn't that people want a way to review the translations, it's that these edits will still show up when you hit "hide patrolled", and there is no way to get rid of them.
Comment 4 Rainer Rillke @commons.wikimedia 2013-06-28 09:25:19 UTC
No matter how you decide, there should be no link that does not work.
Comment 5 Nemo 2013-06-28 09:46:42 UTC
(In reply to comment #4)
> No matter how you decide, there should be no link that does not work.

True. That should be filed as core bug I think; before it was removed completely, the revision patrolling button at the bottom of pages showed up also when patrolling was not possible, so probably the logic in core has some faults.
Comment 6 Rainer Rillke @commons.wikimedia 2013-06-29 13:03:02 UTC
Just for the record:
When clicking  [Mark as patrolled]

Request:
POST https://commons.wikimedia.org/w/api.php
action	patrol
format	json
rcid	100039614
token	---

Response:
{"servedby":"mw1144","error":{"code":"unknownerror","info":"Unknown error: \"tpt-target-page\""}}


The bubble-notification only says "Marking as patrolled failed." and the change is marked with a red "!" in the watchlist.
Comment 7 Marius Hoch 2013-06-29 14:26:54 UTC
Solution would probably be to use the TitleQuickPermissions hook and disallow patrolling for translate titles with.

Alternative would be to introduce a new hook in the article class to only hide the links.

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


Navigation
Links