Page MenuHomePhabricator

Allow cascade semi-protection or different protection levels for root page and cascade transclusions
Open, Needs TriagePublic

Description

See [[T10796]]
Hello.
This was I wanted to suggest to the community:

  1. Apply cascade semi-protection on the Main Page.
  2. Apply full protection on the Main Page using abuse filter (here).
  3. Remove links for non-sysops using css in common.css and inherit in group-sysop.css:
.page-עמוד_ראשי #ca-edit, .page-עמוד_ראשי #ca-ve-edit {display: none !important;}

And so avoid a need to semi-protect every day the templates transcluded temporarly to the page, when the main page itself remains fully protected. And also, avoid all the cases when the main page was destroyed via subsubsubtemplate that was not protected. Unfortunately, it isn't possible. Could you, please, reallow cascade semi-protection, or, even better, allow different protection levels for root page and its cascade transclusions? Thank you.

Event Timeline

Restricted Application added subscribers: Scoopfinder, Aklapper. · View Herald TranscriptMay 21 2018, 12:34 PM
Guycn2 added a subscriber: Guycn2.May 22 2018, 10:58 AM

Could you, please, reallow cascade semi-protection,

Allowing cascading for semi-protection is disabled by default because it would effectively allow any autoconfirmed user to semi-protect any page by transcluding it on another cascade semi-protected page. However, it can be enabled with $wgCascadingRestrictionLevels if that is the community consensus.

or, even better, allow different protection levels for root page and its cascade transclusions? Thank you.

Generally it is not possible to have multiple protections with different options on a page (it is also impossible to e.g. make a page permanently semi-protected and add an expiring full protection, see T41038: Full protection expiry should not affect semi-protection).

Note that in this case, you can work around this by fully protecting main page, and then creating another page that transcludes the main page and cascade semi-protecting that. :)

Thank you.

Note that in this case, you can work around this by fully protecting main page, and then creating another page that transcludes the main page and cascade semi-protecting that. :)

I thought about this option, of course, before I filed this task. I do not sure the comunity will agree - it's too complicated, in all sences.

Allowing cascading for semi-protection is disabled by default because it would effectively allow any autoconfirmed user to semi-protect any page by transcluding it on another cascade semi-protected page. However, it can be enabled with $wgCascadingRestrictionLevels if that is the community consensus.

For all pages, not just the main page?

... it is not possible to have multiple protections ...

So can it be implemented for this task?
Thanks again.

Vvjjkkii renamed this task from Allow cascade semi-protection or different protection levels for root page and cascade transclusions to qjcaaaaaaa.Jul 1 2018, 1:08 AM
Vvjjkkii triaged this task as High priority.
Vvjjkkii updated the task description. (Show Details)
Vvjjkkii removed a subscriber: Aklapper.
CommunityTechBot renamed this task from qjcaaaaaaa to Allow cascade semi-protection or different protection levels for root page and cascade transclusions.Jul 1 2018, 4:26 PM
CommunityTechBot raised the priority of this task from High to Needs Triage.
CommunityTechBot updated the task description. (Show Details)
CommunityTechBot added a subscriber: Aklapper.