-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Simetrical wrote: I believe I've looked at that before, but I just re-read over it. It doesn't, however, address what I needed with this. In particular, this extension was written for 1.9.x for a user who was struggling with doing exactly what this extension does (restricting read and every other kind of access to a namespace). Additionally, Lockdown is a bit too customizable--this extension's meant to address a single issue in as simple a way as possible. That was introduced in 1.10 and thus not useful here. I noted that the parser cache can cause problems with this; however, the only way that this could happen would be if a user who is allowed to access restricted content saves a page transcluding a page in that restricted namespace. If you know of a better way to prevent the transclusion of a non-readable page in a readable page without the aid of $wgNonincludableNamespaces, please do let me know. - -- Daniel Cannon (AmiDaniel) http://amidaniel.com cannon.danielc(a)gmail.com