Last modified: 2008-02-24 20:25:04 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 13128 - Return patrolling data when prop=revisions
Return patrolling data when prop=revisions
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Roan Kattouw
Depends on:
  Show dependency treegraph
Reported: 2008-02-23 14:39 UTC by Hans-Petter Fjeld
Modified: 2008-02-24 20:25 UTC (History)
2 users (show)

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


Description Hans-Petter Fjeld 2008-02-23 14:39:20 UTC
It would be nice to be able get some information about patrolling-status of the revision. Is it patrolled? If so, who and when patrolled?
Comment 1 Bryan Tong Minh 2008-02-23 20:15:14 UTC
As far as I understand from the tables.sql file, whether page is patrolled or not is only recorded in the recentchanges table and not in the revision table. It could be added to list=recentchanges, but certainly not to prop=revisions.
Comment 2 Hans-Petter Fjeld 2008-02-24 17:08:34 UTC
So the fix would be to make the Wiki-software record patrolling-data better?
Comment 3 Roan Kattouw 2008-02-24 19:45:17 UTC
(In reply to comment #2)
> So the fix would be to make the Wiki-software record patrolling-data better?

No, patrolling data won't be added to the revision table, it'll stay in the recentchanges table. I'll implement this today or tomorrow.
Comment 4 Roan Kattouw 2008-02-24 20:25:04 UTC
Fixed in r31233

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