Last modified: 2014-10-01 23:52:52 UTC
In bug 8796 cascade semi-protection has been disabled. Several other bugs were WONTFIXed 'cause in all of them there still was a breach that non authorized user could abuse cascade protected pages for making non authorized protections by transcluding things in them. What I propose is to make it possible to made cascade semi-protection while the page protection is being performed under being fully protected or being made fully protected. This way the only possible "abusers" of the cascading would be users who can make a normal semi-protection. Are authorized in other words. (Unless a wiki uses some fancy custom sets of userrights, sure). This way it would be possible to have e.g. Main page fully protected itself but all templates (and other transcluded pages) and local images it uses semi-protected without performing manual per-page protection for e.g. hundreds of picture of the day templates be semi-protected. Now it is usually possible to find in a large wiki like Russian Wikipedia a template transluded to the Main page which is not protected (e.g. a part of a GA/FA shown and so on). Using cascade full-protection is inadmissible because this way e.g. DYK blocks contributors wont be able to work except few with a sysop flag.
This has the same issue as all of the other requests. If [[Foo]] gets this form of protection set on it, and [[Foo]] transcludes [[Template:Bar]], then any autoconfirmed user can semi-protect any page they want by transcluding it from [[Template:Bar]].
