Manual talk:$wgNonincludableNamespaces


Transclusion from within the same namespace[edit]

I think that this would be more useful (for my purposes, at least) if it did not block transclusion from within the same namespace...or possibly from within the same namespace+talk pair. -- 04:08, 16 May 2007 (UTC)Reply[reply]

I'm not sure how this is useful if you want to allow transclusion/inclusion but prevent access to the data via those mechanisms. If I understand this concept correctly, the transclusion act should determine if the page is protected and then not transclude it or not. If all the pages must be in the same namespace, then I cannot use tranclusion at all on those pages, which seems like an incomplete solution. -- 17:04, 26 October 2007 (UTC)Reply[reply]

We are using a lot of extra namespaces and it would be very useful to allow inclusion/transclusion within a namespace but disallow inclusion/transclusion from one namespace to the other. So, if someone has an idea how to implement such a feature... I would be more than glad to know how to do this... -- 12:48, 10 March 2008 (UTC)Reply[reply]

What file[edit]

What file is this set it? LocalSettings.php? It would be nice if the help said were it is to be set. --Vaccano 22:47, 21 August 2008 (UTC)Reply[reply]

As for all configuration settings, it is LocalSettings.php. iAlex 07:26, 22 August 2008 (UTC)Reply[reply]
Thanks. I was not sure because it does not work for me on my 1.9.2 MW install. I am using the extension and it seems to be doing nothing. Ah well. Maybe I can talk my boss into upgrading to the latest version. --Vaccano 19:16, 22 August 2008 (UTC)Reply[reply]

Well, it does say "Introduced in version: 1.10.0", so I'm not surprised it does nothing in 1.9.2. Tell your boss that 1.9 has reached EOL and is no longer supported at all. No security patches, nothing. See Version lifecycle -- Duesentrieb 19:58, 22 August 2008 (UTC)Reply[reply]