Introduced in r19095; this is a tracking bug // bug for discussion of the new
feature.
Version: 1.10.x
Severity: enhancement
Introduced in r19095; this is a tracking bug // bug for discussion of the new
feature.
Version: 1.10.x
Severity: enhancement
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | None | T10575 Cascading Page Protection (tracking) | |||
Declined | None | T11333 Cascading protection does not affect <includeonly> content | |||
Resolved | None | T11652 String "[cascading]" not shown in edit summary | |||
Resolved | None | T11687 Cascading protection does not affect image pages. | |||
Declined | None | T10658 Allow cascading protections for non-full protection | |||
Resolved | None | T10664 Cascading Page Protection system should pass a parameter with number of trascluding pages | |||
Resolved | None | T10796 Semi-protection should not cascade | |||
Invalid | TheDJ | T24707 Cascading page protection for /Print template subpages | |||
Resolved | Bawolff | T25542 Cascade protection and file redirects | |||
Duplicate | None | T44818 Page-specific protection settings should override cascading protection settings (at least for file description pages) | |||
Resolved | matmarex | T49617 It should be possible to use cascading protection with non-"sysop" protection level |
michael.frey wrote:
When I'm on a page which is proctet by "cascading protection", I see an edit
button and not a "view source" button.
It's no importent bug, but it nice when it's fixed.
That should be in its own bug. In any case, we determined that this query was
too expensive to run every pageview, and explicitly prevented the software from
checking on page-view.
anyfile wrote:
It would be interesting if a parameter is passed to system messages
If a parameter is passed to these system messages with the number of pages
listed below (the number of the page that are rcascading protected and that
include the target page), then these system messages could be written in such a
way, using the {{plural:}} function, to adjust the grammar to be singular or plural.
For instance in English, two different messages could be obtain
... because it is included in the following pages, which are protected ...
... because it is included in the following page, which is protected ...
using the following code
... {{plural:$1|because it is included in the following page, which is
protected|because it is included in the following pages, which are protected}}
(of course other wiki-code could by used and it would also possible to print the
number of the pages)
(for the use of plural see bug # 5005 5006 and
http://meta.wikimedia.org/wiki/Help:Magic_words#Language-dependent_word_conversions
)
robchur wrote:
Please file a *separate* bug for each new request. This is a tracking bug.