Page MenuHomePhabricator

Option to protect all subpages and talk pages when protecting the page
Open, LowPublic

Description

Author: mohamed.m.k

Description:
Hello

When you protect a page, Its sub-pages should be protected too, If they exist.

Example problem:
We have that template on arwiki which have many sub-pages, that template is displayed on the main page, it should be semi-protected. It is possible to do so manually, but it would be a tedious job.

http://tinyurl.com/22uoxh


Version: unspecified
Severity: normal

Details

Reference
bz12908

Related Objects

StatusSubtypeAssignedTask
OpenNone
OpenFeatureNone
DeclinedNone
ResolvedNone
ResolvedNone
ResolvedNone
DeclinedNone
DeclinedNone
ResolvedLegoktm
ResolvedNone
ResolvedNone
ResolvedNone
DeclinedNone
DeclinedNone
ResolvedNone
DeclinedNone
ResolvedLegoktm
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
DeclinedNone
DeclinedNone
DeclinedNone
ResolvedNone
InvalidNone
DeclinedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
DeclinedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
DeclinedNone
DeclinedNone
DeclinedNone
DeclinedNone
ResolvedNone
ResolvedNone
ResolvedNone

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 10:05 PM
bzimport set Reference to bz12908.
bzimport added a subscriber: Unknown Object (MLST).

This should be optionally not automatically -> changing the summary to describe this issue more properly.

I am unconvinced that this is at all necessary or desirable. I can think of
many examples of pages on wikis which should be protected, but their subpages
should not (think user-pages and user subpages).

It is my opinion that this would be a nuisance, more so than it would be useful
for your particular situation.

Marking as WONTFIX.

Reopening, since the comment #2 was apparently based on original request. However I changed it to _optional_ protecting.

mohamed.m.k wrote:

exactly, i didn't think it would be understood to be obligatory but rather like a check box to protect the sub-pages. thanks danny for correcting it.

This reminds me of a similar bug which requested moving all subpages of a moved page. As discussed there, this can put the server on a high load if a page has many subpages. Perhaps both requests can be fullfilled if a solution could be proposed which is based on a background process (much like RenameUser).

(In reply to comment #5)

This reminds me of a similar bug which requested moving all subpages of a moved
page.

That's bug 9626.

webmaster wrote:

(In reply to comment #6)

(In reply to comment #5)

This reminds me of a similar bug which requested moving all subpages of a moved
page.

That's bug 9626.

See also:

Bug 9626 - Moving pages should optionally move their subpages as well
Bug 13491 - Option to delete all subpages when deleting a page

mike.lifeguard+bugs wrote:

talk pages too - just like the shiny new move-subpages

mike.lifeguard+bugs wrote:

(In reply to comment #2)
[...]

It is my opinion that this would be a nuisance, more so than it would be useful
for your particular situation.

Certainly not the case for Wikibooks projects. Please think outside the <s>box</s> Wikipedia.

Perhaps as a extension that hooks into 15071 to get the groups/chain of pages that should be protected if its ever completed and have it offer a "cascading" protection over them.

mike.lifeguard+bugs wrote:

(In reply to comment #11)

What's 15071 ... bug 15071 ?

Yes.

Came here to ask for the same thing. It would be a very useful feature at some cases. At the Albanian Wikiquote we want to be able to protect automatically every quote of the week page (but not its talkpage) as soon as it is created. If this feature was possible, we would just protect the main page (Wikiquote:Quote of the Week) and cascade the protection to all its subpages for them to be autoprotected as soon as they were created.