Difference between revisions of "Issue:DPL allows transclusion of non-transcludable namespaces"
From FollowTheScore
(→Problem) |
|||
| Line 23: | Line 23: | ||
== Reply == | == Reply == | ||
| + | Yes, the current version of DPL does not care about the $wgNonincludableNamespaces array. If you or someone else came up with a patch for the DPL source code which does the job I would certainly make that part of the next release. | ||
| + | :[[User:Gero|Gero]] 21:06, 27 March 2008 (CET) | ||
Revision as of 22:06, 27 March 2008
| Description: | DPL allows transclusion of non-transcludable namespaces |
| Extension / Version: | DPL / 1.6.4 |
| Type / Status: | Bug / open |
Problem
On our wiki, we have some non-transcludable namespaces (which are also locked down by user). However, when using DPL, I can do something like:
<DPL> namespace=SecuredNamespace include=* format=,<H3>[[%PAGE%|%TITLE%]]</H3>,<BR>, </DPL>
to get all the contents of that namespace. Yikes!
As a note, these are namespaces that have been placed into the standard $wgNonincludableNamespaces array, and as such, should be available to DPL.
Reply
Yes, the current version of DPL does not care about the $wgNonincludableNamespaces array. If you or someone else came up with a patch for the DPL source code which does the job I would certainly make that part of the next release.
- Gero 21:06, 27 March 2008 (CET)
