Difference between revisions of "Issue:DPL allows transclusion of non-transcludable namespaces"

From FollowTheScore
Jump to: navigation, search
(New page: {{Issue |Type = Bug |Extension = DPL |Version = 1.6.4 |Description = DPL allows transclusion of non-transcludable namespaces |Status = open }} == Problem == On our ...)
 
(Problem)
Line 19: Line 19:
  
 
to get all the contents of that namespace.  Yikes!
 
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 ==
 
== Reply ==

Revision as of 19:32, 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