In order to keep some control over the "look" of our site, we'd like to restrict creating and editing of "Template:" pages to sysops; users could request new templates, and if we were satisfied they were of general interest, we'd create them, and document then on our template documentation page.
I'm aware that there is no standard mechanism for assigning particular access privileges based on namespace (we don't really want to use one of the custom plugins unless it's pretty sure it will end up in the next version of MW), but is there any "good" (semi-approved) way to write-protect this particular namespace?
Thanks, Ken
I've been protecting my template pages so people can view the source and know what to copy when certain pages need that template, but the only way I've found to do it is individually lock each template, and restrict editing/moving to SysOps. I'm not sure if there's a way to mass-lock anything under the Templates namespace, but if so, I'd like to know too! ~azurite
On 19/06/06, Ken McDonald ken@pixologic.com wrote:
I'm aware that there is no standard mechanism for assigning particular access privileges based on namespace (we don't really want to use one of the custom plugins unless it's pretty sure it will end up in the next version of MW), but is there any "good" (semi-approved) way to write-protect this particular namespace?
Use the hook in Title::userCan(), check against the namespace and $wgUser->isAllowed(); add custom permissions via an extension.
This can probably be done fairly reliably; it's restricting reading that's the bigger problem.
Rob Church
mediawiki-l@lists.wikimedia.org