Page MenuHomePhabricator

Add Special:Protectedpages
Closed, ResolvedPublic

Description

Please add Special:Protectedpages on the same principle as Special:Ipblocklist -
it should display all active locks of all types.

Table structure such as following would be great as well as sorting by any
column but "reason" and "by" such as Special:Imagelist for quicker orientation.

+-------+-------+---------------------------------------------------+------------+

editmove

+---+---+---+---+ pagename | since | reason | by |

ASAS

+===+===+===+===+===================================================+============+

**Foo2006-10-15 12:34Only for registeredUser:Admin

+---+---+---+---+----------+------------------+---------------------+------------+

****Bar2006-11-22 23:45Only for sysopsUser:Admin

+---+---+---+---+----------+------------------+---------------------+------------+

Thanks


Version: unspecified
Severity: normal

Details

Reference
bz7575

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 9:26 PM
bzimport set Reference to bz7575.
bzimport added a subscriber: Unknown Object (MLST).

rotemliss wrote:

About the proposal: it's not possible. The best we can do is the following:

  • Page Name (restrictions e.g. edit=autoconfirmed:move=sysop)

The one who protected the page, the reason for the protection, and the time of
protection are not stored in a table like "ipblocks" - only in "logging", since
23 December 2004, and before that in text pages, not in the database. The
protections are only stored in the table "page", as the column
"page_restrictions", without any other information. Therefore this proposal is
impossible to implement.

*** This bug has been marked as a duplicate of 2171 ***

rotemliss wrote:

(In reply to comment #1)

and before that in text pages, not in the database.

Of course, the text itself was stored in the database, but the structured data
about the protection was not stored there.