Page MenuHomePhabricator

Non-content pages sometimes do not get autopatrolled
Closed, ResolvedPublic

Description

Author: Wiki.Melancholie

Description:
Non-content pages sometimes do not get autopatrolled, even if user is sysop+sighter.

Sighters normally do auto-sight pages on creation. But this only works for the main feature (ns 0,6,10), but not for talk pages e.g.

Example:
http://als.wikipedia.org/w/index.php?title=Template_talk:Navigationsleiste_Schweizer_Verteidigungsminister&rcid=175363

The page was created by User:Brian67, a sysop and sighter; but others still have to patrol that talk page afterwards (red exclamation mark).


Version: unspecified
Severity: enhancement
URL: http://als.wikipedia.org/w/index.php?title=Vorlage_Diskussion:Navigationsleiste_Schweizer_Verteidigungsminister&rcid=175363

Details

Reference
bz16862

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:28 PM
bzimport set Reference to bz16862.

New pages are not auto-patrolled if new page patrol ($wgNPPatrol) is on. It is on by default on all WMF projects.

Wiki.Melancholie wrote:

Hmm, but this is inconsistent with the normal FlaggedRevs behaviour for content pages.
When creating an article, it automatically gets sighted by the sighter.

What is the reason for $wgNPPatrol being true when this differs from the known auto-sighting behaviour?

I think $wgNPPatrol should only be true when *also* articles/templates/images do not get auto-sighted on creation.

Coupling those two variables might be best, I think. Either both true, or both false.

Wiki.Melancholie wrote:

A description of $wgNPPatrol is missing on MediaWiki.org, but it seems like 'autoconfirmed users' would be affected by $wgNPPatrol too, is that right? Or is there a separation of sighters and autoconfirmed users possible? So that only sighters will *always* auto-patrol (like they do auto-sight)?