In wikis using FlaggedRevs, the mobile apps don’t check whether the article’s latest version or an earlier one should appear according to the user settings, they always show the latest (unapproved) version.
| iOS | Android | MobileFrontend |
|---|---|---|
 |  |  |
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Duplicate | None | T153595 Unapproved article version shown in mobile apps | |||
| Invalid | None | T163276 Show only approved article version for FlaggedRev Wikipedias | |||
| Duplicate | None | T163462 FlaggedRevs for Mobile Content Service | |||
| Open | None | T169116 Support flagged revisions in RESTBase | |||
| Open | None | T209936 Content of unaccepted pending revisions show up in RESTBase APIs |
Event Timeline
Comment Actions
It looks like this is an optional MW extension used by some editors on some wikis as part of their article editing workflow.
We'd probably want to add this to our general "apps editing features" triage - timing/resourcing/priority etc of more heavily used editing workflow items like notifications, talk pages, etc...
Another consideration - apps don't presently handle "the user settings" mentioned in the description, which would need to be tackled first.
Comment Actions
I believe there are actually two issues here:
- Logged in editors of flagged-rev wikis need a setting to determine whether to show the latest version or the flagged version should be shown to them
- Non-logged in readers of flagged rev wikis should only see the approved version of an article
The former is complicated and maybe out of scope for the Reading team. The latter should be a priority fix, if technically feasible.
I'm not terribly familiar with flagged revs wikis and their workings, so I will need some help determining if I understand the issues correctly and if they are fixable.
Comment Actions
Yes, you’re correct. However, I think that an even larger percentage of the mobile app users is logged out, “just” a user, so the first point is not a big problem. You can configure the app at first to show the latest version or to show the approved version if it’s easier, I don’t think it would be such a big issue.
Comment Actions
@JMinor FYI this was brought up during the Reading / Services Sync. Services is aware… and planning it into their new persistance infrastructure. But that is still some time off.
Tagging to make sure its on their radar.
Comment Actions
Note that users should be able to navigate to both versions of the article, it's just that anons vs. logged-in users should get a different version by default.
Comment Actions
Clients should also be prepared to handle thumbnail URLs which refer to some non-current version of the image (see also T66214#3256693). Presumably that's not happening right now due to this bug.