EN.WP.ST47 wrote:

We could probably do this with a category, and create a separate CSS class for pages in a specific category. That would require a query against categorylinks for each page in Special:Newpages and a new CSS class like li.not-patrolled.

EN.WP.ST47 wrote:

A patch to allow a pages that are members of a specified category to be highlighted differently on Special:Newpages.

attachment bug30134.patch ignored as obsolete

EN.WP.ST47 wrote:

Updated: A patch to allow a pages that are members of a specified category to be highlighted differently on Special:Newpages.

This corrects some inappropriate quoting syntax in the query, and moves the addition of the categorylinks table to the conditional where it belongs.

Attached:

I don't think this is something we should put into core. It seems
like this could easily be done with some JS if the information is
exposed via the API, though.

pocoapocowiki wrote:

I really think that this features could be used by everybody, but anyhow, who can help us to get this in JS implemented? Thanks.

Anyone familiar with JavaScript and jQuery should be able to do this:

• Fetch the page names from the page
• Make a request to the API for those titles with the categorymembers querymodule
• If the returned object contains a certain category store it in an array
• Create a CSS selector fed to jQuery for all these page names and call addClass()

how about fixing the actual issue, namely, that patrolling only allows for "unpatrolled" and "patrolled" states. What you want is a third state, basically "found to be bad". So, how hard would it be to add support for more than two states to the patrolling feature?

(In reply to comment #7)

how about fixing the actual issue, namely, that patrolling only allows for
"unpatrolled" and "patrolled" states. What you want is a third state, basically
"found to be bad". So, how hard would it be to add support for more than two
states to the patrolling feature?

It wouldn't be too complicated, but it seems to be out of scope for the patrolling feature. Mainly because patrolling is for revisions, not pages. Assuming the latest revision for the entire page may be okay for the FlaggedRevs extension but not for core patrolling.

This sounds like a great feature request for FlaggedRevs, or perhaps FlaggedPages.

Another long-time proposal that seems to overlap with this a little bit is the "Special rights requests queue" extension. An extension where users can make request for certain actions to be taken that they do not want or are unauthorized to perform (page moves, user blocks, user right changes, deletions etc.)

Such an extension could then hook into patrolling of core, FlaggedRevs or both to filter out ones that have pending requests for a certain action (eg. delete).

The obvious conclusion is though that neither templates, categories or long pure-wikitext pages are a long-term solution to deletion requests, page moves and the like (as also concluded by Jimmy Wales' talk at Wikimania 2011).

The latter part was mentioned from time to time, but never on bugzilla afaik. Logged under bug 30373.