Manual:Patrolling

Patrolling log events mark revisions as patrolled.

Database

• recentchanges.rc_patrolled
• logging

Configuration settings

Every user with the patrol permission is able to review article changes. By default, only the sysop (admin) group has this permission. You can optionally add patrol to an additional group:

$wgGroupPermissions['team']['patrol'] = true;

Users with the autopatrol permission have their changes automatically marked as patrolled. The below configuration means that changes made by users in the sysop, bot, team groups are automatically reviewed:

$wgGroupPermissions['bot']['autopatrol'] = true;
$wgGroupPermissions['sysop']['autopatrol'] = true;
$wgGroupPermissions['team']['autopatrol'] = true;

You can also let a certain group of users only see the unpatrolled edit marks, by giving them the patrolmarks permission. Configuration in the example below means that everyone (even unregistered users) will be able to see the unpatrolled edit marks.

$wgGroupPermissions['*']['patrolmarks'] = true;

If you change your configuration or permissions, and you don't see what you expect in RecentChanges, you probably need to run the 'Rebuildrecentchanges.php ' maintenance script.

See also

• Manual:$wgUseNPPatrol
• Manual:$wgUseRCPatrol
• Help:Patrolling
• Help:Patrolled edits

API

Patrol log events have a patrol child element, e.g. <patrol cur="12" prev="0" auto="1" />