Page MenuHomePhabricator

FlaggedRevs should not unavoidably disable core RC patrolling
Closed, ResolvedPublic

Description

Author: happy_melon

Description:
An implementation proposed on en.wiki ([[Wikipedia:Flagged revisions/Trial]]) proposes to use $wgFlaggedRevsOverride = false; $wgFlaggedRevsReviewForDefault = true; to effectively limit the availability of FlaggedRevs features to specific articles. Wanting to only 'enable' FlaggedRevs on a subset of a namespace is an acceptable and probably fairly common desire. However, setting $wgFlaggedRevsNamespaces = array( NS_MAIN ); disables RCPatrolling using the core interface across the entire namespace. I can't see any pressing reason why RCPatrol values necessarily need to be synchronised with reviewed revisions; at the very least it should be possible to 'unlink' the two with a configuration variable.


Version: unspecified
Severity: minor

Details

Reference
bz16495

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:24 PM
bzimport added a project: FlaggedRevs.
bzimport set Reference to bz16495.

happy_melon wrote:

adds a configuration variable to optionally allow normal RC patrolling to continue

Adds a new configuration variable, default true, which when false guts the function FlaggedRevsHooks::stripPatrolRights. UNTESTED

Attached: