Last modified: 2013-09-18 11:35:31 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 28894 - Proofread Page extension needs an API module to set or change page status
Proofread Page extension needs an API module to set or change page status
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
ProofreadPage (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on: 46578
Blocks: noncoreapi Wikisource
  Show dependency treegraph
Reported: 2011-05-09 15:20 UTC by MZMcBride
Modified: 2013-09-18 11:35 UTC (History)
6 users (show)

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


Description MZMcBride 2011-05-09 15:20:56 UTC
The Proofread Page extension (<>) needs an API module to allow users to set or change page status (without text, problematic, etc.).

This is related to bug 28893.
Comment 1 Beau 2011-08-21 12:12:20 UTC
I wonder if it is really needed. You can always change page status using action=edit. Proofreading does not only involve changing status, but also correcting mistakes. In such cases you will have to edit page anyway.

The only pitfall here is that earlier versions of the extension used PageQuality template. You can replace them by extension tag just by nullediting all pages.
Comment 2 billinghurst 2011-10-29 15:16:13 UTC
With the addition of the API, it means we can more easily process files based on API data rather than having to do extra processing on the actual of the file.  With regard to the tag vs the template is a typical example of why, with the API, we can quickly get files of a certain time/period/whatever and process them using a bot rather than having to jump on every file to check its needs.
Comment 3 Beau 2011-10-29 19:15:48 UTC
Andrew, I don't how your comment is related to this feature request. You can obtain the proofread status of a page via api.
Comment 4 John Mark Vandenberg 2012-03-21 07:32:34 UTC
I would like the proofread status of a page to be a Flagged Rev Tag.

This allows the existing API to be used

It also provides some other benefits
* separation of the proofreading UI (textbox + image side by side) from the proofreading quality system.
* multiple quality indicators (often the text is perfect but the style is poor quality)
* customisation of the quality workflows, including customisation of access control to the quality levels (some projects may want three phase verification, one project demanded that anons be allowed to change quality levels - see bug 20812 comment 28)
Comment 5 Tpt 2012-09-12 12:59:30 UTC
"I would like the proofread status of a page to be a Flagged Rev Tag": a lot of wikis doesn't use (and doesn't want to use) FlaggedRevs. So we can't make ProofreadPage dependant of FlaggedRevs.

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