View source for Controlling output volume

{{DPL manual|section=Parameters|subsection=Controlling output volume}}
{{tocright}}


By default, DynamicPageList3 shows the name of each article, including its namespace in the result set as a link to the article.
By setting the '''volume control parameters''' of DPL3, it is possible to:

* Specify a header/footer to show when results are found or not found.
* Add metadata (size, author, last edited by, date of last change, etc.) to the output.
* Include contents from articles.
* Show the number of articles in the result set.
* Cut off the articles' content at a certain length.
* Add access date (frequency, date of last access).
* Add the articles' contents or parts of it.


==Defining header and footer for the result==
===resultsheader===
{{DPL Parameter
 |name   = resultsheader
 |purpose= Output a headline, before DPL3 results, if there is at least one article to display.
}}


'''Syntax:'''<br>

<code>resultsheader=''some wiki text''</code>


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: resultsheader (example 1)|Example}}
{{ViewTest|Examples|Parameter: resultsheader (example 1)}}


'''Notes:'''
* <code>{{DPL|%PAGES%}}</code> - {{#lst:Controlling output format|%PAGES%}}
* <code>{{DPL|%TOTALPAGES%}}</code> - {{#lst:Controlling output format|%TOTALPAGES%}}
* <code>{{DPL|%VERSION%}}</code> - {{#lst:Controlling output format|%VERSION%}}
* The symbol <code>¶</code> or <code>\n</code> is converted to a newline symbol. This is useful if you want to use wiki markup that needs to start at the beginning of a line (if the wiki parser requires a linefeed to understand your wikitext).
* If <code>{{DPL|oneresultheader}}</code> is specified as well, the latter is used in case there is exactly one entry in the DPL3 result set. <code>{{DPL|resultsheader}}</code> is only used if there are '''two or more''' entries in the result set.


===resultsfooter===
{{DPL Parameter
 |name   = resultsfooter
 |purpose= Output a 'footline', after DPL3 results, if there is at least one article to display.
}}


'''Syntax:'''<br>

<code>resultsfooter=''some wiki text''</code>


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: resultsfooter (example 1)|Example}}
{{ViewTest|Examples|Parameter: resultsfooter (example 1)}}


'''Notes:'''
* <code>{{DPL|%PAGES%}}</code> - {{#lst:Controlling output format|%PAGES%}}
* <code>{{DPL|%TOTALPAGES%}}</code> - {{#lst:Controlling output format|%TOTALPAGES%}}
* <code>{{DPL|%VERSION%}}</code> - {{#lst:Controlling output format|%VERSION%}}
* The symbol <code>¶</code> or <code>\n</code> is converted to a newline symbol. This is useful if you want to use wiki markup that needs to start at the beginning of a line (if the wiki parser requires a linefeed to understand your wikitext).
* If <code>{{DPL|oneresultfooter}}</code> is specified as well, the latter is used in case there is exactly one entry in the DPL3 result set. <code>{{DPL|resultsfooter}}</code> is only used if there are '''two or more''' entries in the result set.


===oneresultheader===
{{DPL Parameter
 |name   = oneresultheader
 |purpose= Output a headline, before DPL3 results, if there is exactly one article to display.
}}

'''Syntax:'''<br>

<code>oneresultheader=''some wiki text''</code>


'''Notes:''' 
* The symbol <code>¶</code> or <code>\n</code> is converted to a newline symbol. You may need this if the wiki parser requires a linefeed to understand your wikitext.
* <code>{{DPL|%VERSION%}}</code> is replaced by the current DPL3 version. This is useful if you want to use wiki markup, which needs to start at the beginning of a line. 


===oneresultfooter===
{{DPL Parameter
 |name   = oneresultfooter
 |purpose= Output a 'footline', after DPL3 results, if there is exactly one article to display.
}}


'''Syntax:'''<br>

<code>oneresultfooter=''some wiki text''</code>


'''Notes:''' 
* The symbol <code>¶</code> or <code>\n</code> is converted to a newline symbol. You may need this if the wiki parser requires a linefeed to understand your wikitext.
* <code>{{DPL|%VERSION%}}</code> is replaced by the current DPL3 version. This is useful if you want to use wiki markup, which needs to start at the beginning of a line.


===noresultsheader===
{{DPL Parameter
 |name   = noresultsheader
 |purpose= Output a headline if there is no article to display (empty result).
}}


'''Syntax:'''<br>

<code>noresultsheader=''some wiki text''</code>


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: noresultsheader (example 1)|Example}}
{{ViewTest|Examples|Parameter: noresultsheader (example 1)}}


'''Notes:''' 
* Setting a single blank or newline character (<code>{{DPL|noresultsheader}}=&amp;nbsp;</code> or <code>{{DPL|noresultsheader}}=\n</code>) suppresses the warning message from DPL3 that is normally issued if no articles are found.
* The symbol <code>¶</code> or <code>\n</code> is converted to a newline symbol. You may need this if the wiki parser requires a linefeed to understand your wikitext.


===suppresserrors (DEPRECATED)===
This parameter is deprecated and is left in the code as a null parameter to give people time to remove it from their queries.  It will be fully removed in a future release of DPL3.

{{DPL Parameter
 |name   = suppresserrors
 |purpose= Suppress the warning message if no matching article was found.
}}


'''Syntax:'''<br>

<code>suppresserrors=true</code>


'''Notes:''' 
* Setting <code>{{DPL|suppresserrors}}</code> to true has the same effect as setting <code>{{DPL|noresultsheader}}</code> to a single space character. The command is provided for downward compatibility reasons with older DPL versions.
* See also: <code>{{DPL|debug}}</code>.


===noresultsfooter===
{{DPL Parameter
 |name   = noresultsfooter
 |purpose= Output a footline if there is no article to display (empty result).
}}


'''Syntax:'''<br>

<code>noresultsfooter=''some wiki text''</code>


'''Note:''' <code>{{DPL|noresultsfooter}}</code> is essentially the same as <code>{{DPL|noresultsheader}}</code>. If there is no output to display, the difference between header and footer becomes incredibly marginal.


==Adding metadata to the output==
===addcategories===
{{DPL Parameter
 |name   = addcategories
 |purpose= Shows all categories to which an article belongs as a small text line after the article name.
}}


'''Syntax:'''<br>

<code>addcategories  = true</code>


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: addcategories (example 1)|Example}}
{{ViewTest|Examples|Parameter: addcategories (example 1)}}


'''Notes:''' 
* In <code>{{DPL|mode}}=userformat</code> the category list can also be referenced using built-in <code>{{DPL|%CATLIST%}}</code> (pipe separated) <code>{{DPL|%CATBULLETS%}}</code> (bullet separated) <code>{{DPL|%CATNAMES%}}</code> (comma separated).


===addpagecounter===
{{DPL Parameter
 |name   = addpagecounter
 |purpose= Shows number of times the page has been viewed.
{{note|Requires [[mw:Extension:HitCounters|Extension:HitCounters]] to be used. This extension is not yet available on Miraheze.}}
}}


'''Example:'''
<pre>
{{#dpl:
|category       = Dessert examples
|ordermethod    = counter
|order          = descending
|addpagecounter = true
|count          = 3
}}
</pre>

This would show the 3 most popular articles about dessert.


'''Note:''' in <code>{{DPL|mode}}=userformat</code> the access counter can also be referenced as a built-in variable.


===addpagesize===
{{DPL Parameter
 |name   = addpagesize
 |purpose= Shows the size of the page.
}}


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: addpagesize (example 1)|Example}}
{{ViewTest|Examples|Parameter: addpagesize (example 1)}}


'''Note:''' in <code>{{DPL|mode}}=userformat</code> the size can also be referenced as a built-in variable.


===addcontribution===
{{DPL Parameter
 |name   = addcontribution
 |purpose= Shows how much a user contributed to an article.
}}


'''Syntax:'''<br>

<code>addcontribution=true</code> — ('''Default''' is ''false'')


Using this parameter restricts the output to articles that were edited recently (this is usually one week or one month, according to the setup of the wiki).

A link to the contributor is provided and an "asterisk bar" appears indicating how many bytes in the article were changed by that user.

You will also have the built-in {{DPL|variables}} <code>{{DPL|%CONTRIBUTOR%}}</code>, <code>{{DPL|%CONTRIB%}}</code> and <code>{{DPL|%CONTRIBUTION%}}</code> available to be used in your own <code>{{DPL|format}}</code> statement.


===adduser===
{{DPL Parameter
 |name   = adduser
 |purpose= Requires <code>{{DPL|ordermethod}}=''[...,]firstedit''</code> or <code>{{DPL|ordermethod}}=''[...,]lastedit''</code> (where the ''<code><nowiki>[...,]</nowiki></code>'' signifies a complex ordermethod with extra parameters). If {{tt|firstedit}} (or {{tt|lastedit}}), <code>{{DPL|adduser}}=''true''</code> displays the user who made the first (or last) revision of the page. In this way, the parameter is equivalent to the <code>{{DPL|addauthor}}</code> (<code>{{DPL|addlasteditor}}</code>) parameter (see below).
}}


'''Syntax:'''<br>

<code>{{DPL|adduser}}=true</code> — ('''Default''' is ''false'')


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: adduser (example 1)|Example}}
{{ViewTest|Examples|Parameter: adduser (example 1)}}


'''Note:''' If <code>{{DPL|mode}}=userformat</code> the user can be referenced using the built-in variable <code>{{DPL|%USER%}}</code>.


===addauthor===
{{DPL Parameter
 |name   = addauthor
 |purpose= Show the user who created the article, '''cannot''' be used with <code>{{DPL|addlasteditor}}</code>
}}


'''Syntax:'''<br>

<code>addauthor=true</code> — ('''Default''' is ''false'')


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: addauthor (example 1)|Example}}
{{ViewTest|Examples|Parameter: addauthor (example 1)}}


===addlasteditor===
{{DPL Parameter
 |name   = addlasteditor
 |purpose= Show the user who edited the most recent revision of a page, cannot be used with <code>addauthor</code>
}}


'''Syntax:'''<br>

<code>addlasteditor=true</code> — ('''Default''' is ''false'')


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: addlasteditor (example 1)|Example}}
{{ViewTest|Examples|Parameter: addlasteditor (example 1)}}


'''Note:''' The same behavior can be achieved (and formatted) using:
* <code>{{DPL|addlasteditor}} = true</code> and
* <code><nowiki>|format = ,\n* [[%PAGE%|%TITLE%]] . . [[User:%USER%|%USER%]]</nowiki></code>


===addpagetoucheddate===
{{DPL Parameter
 |name   = addpagetoucheddate
 |purpose= Shows date/time of last change to the page according to the definition of the 'page_touched' field on [[mw:Page_table|Page_table]].

Requires <code>{{DPL|ordermethod}}=''[...,]pagetouched''</code> or <code>{{DPL|ordermethod}}=''[...,]title''</code> (<code>[...,]</code> means complex ordermethods with an extra parameter before are allowed.)
}}


'''Syntax:'''<br>

<code>addpagetoucheddate=true</code> — ('''Default''' is ''false'')


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: addpagetoucheddate (example 1)|Example}}
{{ViewTest|Examples|Parameter: addpagetoucheddate (example 1)}}


'''Notes:''' 
* In <code>{{DPL|mode}}=userformat</code> this date can also be referenced as a built-in variable <code>{{DPL|%DATE%}}</code>. 
* The formatting of the date can be influenced using <code>{{DPL|userdateformat}}</code>. 
* The date is translated to your local time zone (if defined in your preferences) or to the server's time zone.


===addeditdate===
{{DPL Parameter
 |name   = addeditdate
 |purpose= If firstedit (resp. lastedit), <code>{{DPL|addeditdate}}{{=}}true</code> shows the date of the first revision/creation (resp. last revision) of the page. Requires <code>{{DPL|ordermethod}}{{=}}''[...,]firstedit''</code> or <code>{{DPL|ordermethod}}=''[...,]lastedit''</code> (<code>[...,]</code> means complex ordermethods with an extra parameter before firstedit/lastedit are allowed.)

Conflicts with other "add*date" (<code>{{DPL|addpagetoucheddate}}</code>, etc.) parameters.
}}


'''Syntax:'''<br>

<code>addeditdate=true</code> — ('''Default''' is ''false'')


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: addeditdate (example 1)|Example}}
{{ViewTest|Examples|Parameter: addeditdate (example 1)}}


'''Notes:'''
* In <code>{{DPL|mode}}=userformat</code> this date can also be referenced as a built-in variable <code>{{DPL|%DATE%}}</code>.
* The formatting of the date can be influenced using <code>{{DPL|userdateformat}}</code>.
* The date is translated to your local time zone (if defined in your preferences) or to the server's time zone.


===addexternallink===
{{DPL Parameter
 |name   = addexternallink
 |purpose= Add the URL of an external link to the output list.
}}

'''Syntax:'''<br>

<code>addexternallink=true</code> — ('''Default''' is ''false'')


'''Note:''' The command makes only sense in combination with <code>{{DPL|linkstoexternal}}</code>.


===addfirstcategorydate===
{{DPL Parameter
 |name   = addfirstcategorydate
 |purpose= Shows the date/time the article was added to one of the listed include categories. If more than one category is listed and an article belongs to more than one of them, the result is ambiguous.

From a logical standpoint, it is recommended to include one category only with the <code>{{DPL|category}}</code> parameter, or to make sure that each of the articles in the result set belongs to only one of the categories listed.
Conflicts with other "add*date" (<code>{{DPL|addeditdate}}</code>, etc.) parameters.
}}


'''Syntax:'''<br>

<code>addfirstcategorydate=true</code> — ('''Default''' is ''false'')


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: addfirstcategorydate (example 1)|Example}}
{{ViewTest|Examples|Parameter: addfirstcategorydate (example 1)}}


'''Notes:''' 
* In <code>{{DPL|mode}}=userformat</code> this date can also be referenced as a built-in variable <code>{{DPL|%DATE%}}</code>.
* The formatting of the date can be influenced using <code>{{DPL|userdateformat}}</code>.  
* The date is translated to your local time zone (if defined in your preferences) or to the server's time zone.


===showcurid===
{{DPL Parameter
 |name   = showcurid
 |purpose= Page links will contain the current page ID, cannot be used together with <code>{{DPL|openreferences}}{{=}}true</code>.
}}


'''Syntax:'''<br>

<code>showcurid=true</code> — ('''Default''' is ''false'')


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: showcurid (example 1)|Example}}
{{ViewTest|Examples|Parameter: showcurid (example 1)}}


'''Notes:'''
* <code>{{DPL|showcurid}}=true</code> cannot be used together with <code>{{DPL|openreferences}}=true</code>.
* Using this type of link may be somewhat faster than using the title only. This kind of link is useful for some web spiders (e.g., some search engine spiders may need a unique ID within the pagelink) and it works even if the title has moved.


'''Alternate Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: showcurid (example 2)|Example}}
{{ViewTest|Examples|Parameter: showcurid (example 2)}}


==Include contents from the articles in the result set==
===include===
{{DPL Parameter
 |name   = include
 |purpose= Include pages (whole content) or include certain sections of articles or template parameters.
''This functionality is based on the ideas and work of Steve Sanbeg and his extension [[mw:Extension:Labeled Section Transclusion|Labeled Section Transclusion]]. DPL3 comes with a modified version of Sanbeg's source, so there is no need for additional installation.''
}}

With <code>{{DPL|include}}</code> you can incorporate one or more of the following
* The whole article as it is
* A certain chapter -- identified by its headline
* A certain chapter -- identified by its position (sequence number, regardless of level)
* Parameter(s) used in template calls
* The output of a surrogate template (phantom template) which is used instead of the original template
* Pieces of text which are marked by special section markers

There is a close correlation between the output of the <code>{{DPL|include}}</code> statement and <code>{{DPL|table}}</code> and <code>{{DPL|tablerow}}</code>. You should understand those statements if you want to create tabular output from included content.

'''The syntax for this parameter is outlined in multiple sections below.''' 


====include whole article====


'''Syntax:'''<br>
:<code>{{DPL|include}} = *</code> — The character <code>*</code> functions as a wildcard.


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: include (example 1)|Example}}
{{ViewTest|Examples|Parameter: include (example 1)}}


'''Note:''' you can use <code>{{DPL|includemaxlength}} = ''n''</code> (where {{tt|n}} is an integer) to restrict the included text to a portion of the article. The text is truncated in a way which does not spoil tag structures or nested brackets. A result is cut at a word boundary if possible.


====include page sections (chapters)====


'''Syntax:'''<br>
:<code>{{DPL|include}} = #heading1,#heading2,...</code> — The character <code>#</code> is used as a prefix to the page section heading (chapter) name.


Specifying <code>''#heading1''</code> includes text from 'heading1' (case-insensitive) until the next heading of the same or lower level.<!-- (refer to [[mw:Extension:Labeled Section Transclusion#Transcluding sections by headings|Transcluding sections by headings]]).-->

* Instead of the prefix <code>#</code>, <code>@</code> can be used (the <code>#</code> may lead to problems in certain cases); <code>@@</code> acts as a regexp comparison just as <code>##</code> does.
* Normally a text pattern is compared ''literally'' and it must match the whole headline of the chapter. If a double hash <code>##</code> is used, however, the text is taken as a (case-insensitive) regular expression. It is automatically enclosed within slashes, and will refer to the headline as a whole (^regexp$). So, if only matching part of the text is desired, <code>.*</code> must be added around the pattern. Correct regexp syntax must be provided; otherwise, runtime errors may be seen, no output received etc.
:<syntaxhighlight lang="wikitext" copy inline>{{DPL|include}} = ##.*omethin.*</syntaxhighlight> — This matches a page section name like "This is something old" or "That Was Something Old".

{{note|Formerly, this example stated that if more than one section exists with the same name, only the first is displayed, similar to how [[mw:Extension:Labeled Section Transclusion#Transcluding sections by headings|Labeled Selection Transclusion]] functions); however, this currently includes '''all''' sections with the same name, and may appear differently in different result formats.}}


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: include (example 2)|Example}}
{{ViewTest|Examples|Parameter: include (example 2)}}


'''Notes:'''
* This functionality is also available as a separate parser function (called <code>{{DPL|#dplchapter}}</code>).
* If there is no chapter with the specified heading, the output will be empty.
* You can also limit the amount of text for each section displayed in the output, which automatically generates a link to view the rest of the content:
:<syntaxhighlight lang="wikitext" copy inline>{{DPL|include}} = #heading1,#heading2[''n'' ''linktext''],...</syntaxhighlight>, where <code>''n''</code> is the number of characters to include, and <code>''linktext''</code> is the characters or text used as the link label.
:* If the remaining text is longer than the limit, it is cut and a link appears pointing directly to the chapter which was included.
:* When truncating included text portions, care is taken not to break words midway through, and ''not to spoil wiki syntax'' (i.e., maintain a symmetry of brackets and braces, make sure that ''nowiki'' and ''pre'' tags are balanced). Therefore, the size of the included text can deviate from what was specified.
:* Note that <code>{{DPL|%SECTION%}}</code> can be used in <code>{{DPL|secseparators}}</code> to fetch the section name, which may be useful to customize the text to include the (otherwise unseen) section name:
::<syntaxhighlight lang="wikitext" copy inline>{{DPL|secseparators}}<nowiki> = ,[[%PAGE%#%SECTION%|more "%SECTION%"...]]</syntaxhighlight>
::* This variable is replaced by "article#heading" if used in <code>{{DPL|secseparators}}</code>. It is up to you to create a link from this text using normal wiki syntax if you wish.

{{note|'''Note:''' Content related to or involving filters may be non-working or incorrect; as such, this section may be removed at a later date.|warn}}
* Add one or more optional filter expressions, a character limit and/or an optional link text in square brackets to shape the included portion of text : {{tt|[filter 1~...~filter n~limit text]}}.
** The filters are applied before calculating the length of the text; they simply throw away the matching part of the contents. 
** If the remaining text is longer than the limit, it is cut and a link appears which points directly to the chapter which was included. Using {{tt|"1"}} as a limit only shows the link (if the corresponding chapter in the article is not empty), {{tt|"0"}} does not show anything, not even the link. When truncating included text portions care is taken ''not to spoil wiki syntax'' (i.e., maintain a symmetry of brackets and braces, make sure that {{tt|nowiki}} and {{tt|pre}} tags are balanced). Therefore, the size of the included text can deviate from what you specified.


====include sections by on-page position reference====


To include sections according to their position on the page, use a simple number with a <code>%</code> as prefix. <code>%0</code> includes the text BEFORE the first chapter, <code>%1</code> includes the first chapter, <code>%6</code> the sixth and so on. Chapters are counted regardless of their level. No nesting logic is applied. <code>%-1</code> is a special value which refers to the '''last''' chapter of an article (<code>%-2</code> does ''not'' work, however). <code>%2[30]</code> includes the first thirty characters of the second chapter. <code>{{DPL|%SECTION%}}</code> contains the heading of the selected chapter.


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: include (example 3)|Example}}
{{ViewTest|Examples|Parameter: include (example 3)}}


====include contents related to templates====
<br>

'''Syntax:'''<br>
:<code>{{tt|include}}={my template}</code> — The character <code>#</code> is used as a prefix to the page section heading name.

The '''the result of a template call''' can be included by specifying the template name within curly braces. So, <code>{{DPL|include}}={my template}</code> displays the result of the template call with the original parameters used on the selected article page.


'''Notes:'''
* A space char or a line break must be specified after this statement before ending the #dpl parser function call or the MW parser may be fooled by three successive closing curly braces.
* MediaWiki treats spaces like underscores. Therefore, ''{my template}'' also matches a template invocation like <nowiki>{{My_template|...}}</nowiki>.
* MediaWiki searches for template calls in the template namespace. Specifying ''{my template}'' also matches a template invocation like <nowiki>{{Template:My_template|...}}</nowiki>.
* Using a different namespace also works: ''{Xyz:my template}'' matches a template invocation in namespace Xyz. ''{:my template}'' matches a template invocation in the main namespace like <nowiki>{{:my template|...}}</nowiki>.
* Include '''one or more template parameter values''' by specifying a list of parapeter names (or position numbers) separated by colons <code>:</code> (and optional white space). Names are used for named parameters, numbers for positional (anonymous) parameters.
:: The following would include the values of the 'age' and 'size' paraneter, and the first unnamed parameter of the template "animal":
:: <syntaxhighlight lang="wikitext" copy inline>{{tt|include}} = {animal}:age:size:1</syntaxhighlight>
* It is even possible to use expressions which contain a <code>%</code> symbol as pseudo parameters:
::<syntaxhighlight lang="wikitext" copy inline>{{tt|include}} = {animal}:age:%PAGE%:size:1</syntaxhighlight>


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: include (example 4)|Example}}
{{ViewTest|Examples|Parameter: include (example 4)}}


;Surrogate tempates
Instead of listing parameter values, '''the output of one or more 'surrogate' templates can be included''' (also called 'phantom templates'). DPL3 calls the template(s) instead of the original, and allows the identical parameter list to be worked with (plus additional DPL3 parameters). The output of the surrogate template sets (and formats) one line of results, which is then applied to each subsequent result in the result set. To make this happen, the name of a template must be specified within single curly braces and a suffix added. Five additional DPL3 parameters are also passed to the template, and can be used within it:

:* <code>{{DPL|%PAGE%}}</code> – {{#lst:Controlling output format|%PAGE%}}
:* <code>{{DPL|%TITLE%}}</code> – {{#lst:Controlling output format|%TITLE%}}
:* <code>{{DPL|%DATE%}}</code> – {{#lst:Controlling output format|%DATE%}}
:* <code>{{DPL|%USER%}}</code> – {{#lst:Controlling output format|%USER%}}
:* <code>{{DPL|%CATLIST%}}</code> – {{#lst:Controlling output format|%CATLIST%}}


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: table (example 3)|Example}}
{{ViewTest|Examples|Parameter: table (example 3)}}


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: title (example 2)|Example}}
{{ViewTest|Examples|Parameter: title (example 2)}}


'''Notes:'''
* There is an alternate syntax to specify a surrogate template that has the advantage that the surrogate template may reside in a different namespace than the original template. Furthermore, the surrogate template's name can be wholly different from the original template name: <code>{template¦surrogate template}</code>. For example, you may specify something like <code>{my template¦Help:Substitution for my template}</code>.
{{note|Formerly it was stated that, if a page listed in the result '''does not use the specified template''', the DPL3 engine calls a template with the additional suffix ".default", with <code>{{DPL|%PAGE%}}</code> and <code>{{DPL|%TITLE%}}</code> as parameters; this is not currently true, ".default" does not appear, the result just won't display.}}<!--
-- currently this does not function as was previously stated
'''Example:'''
{{#lsth:Examples/Parameter: include (example 5)|Example}}
{{ViewTest|Examples|Parameter: include (example 5)}}


Formerly, the DPL3 third-party text said:
 Example: includepage={myTemplate}.dpl
 If a page does not contain a reference to "Template:myTemplate" then "Template:myTemplate.dpl.default" is invoked with <code>{{DPL|%PAGE%}}</code> and <code>{{DPL|%TITLE%}}</code> as parameters.
-->


====include parser function calls====


If a pattern like <code>{#''pfunc''}.''list''</code> is specified, DPL3 looks for calls of the parser function 'pfunc'. DPL3 passes the parameters of this parser function to a template, which must be provided under the name of 'Template:pfunc.list'. Instead of '.list' a desired suffix can be specified. The Template receives the parser function name as <code>%PFUNC%</code> and all parameters under their normal name or number. Instead of specifying a single parser function, a generic pattern can also be used. 


'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: include (example 6)|Example}}
{{ViewTest|Examples|Parameter: include (example 6)}}


'''Note:''' This function is not very robust. It cannot handle nested parser functions properly.

To find all parser functions, <code><nowiki>{#.+}</nowiki></code> can be used:
:<syntaxhighlight lang="wikitext" copy inline>{{DPL|include}}={#.+}.''pfunc''</syntaxhighlight>
* The <code>.+'</code> portion is treated like a regular expression.
* The search itself is based on simple heuristics, so the output may not always be correct.


====include parser extension (tag) calls====


If a patter like <code>{~''func''}.''list''</code> is specified, DPL3 looks for calls of the parser extension (tag) with the tag name <code>&lt;func&gt;</code>. DPL3 passes the body (all contents) of the tag (as-is, including line breaks) to a template, which must be provided under the name of 'Template:func.list'. Instead of '.list' another desired suffix can be used. The Template receives the parser extension (tag) function name as <code>{{DPL|%TAG%}}</code> and the body contentis named <code>{{DPL|%TAGBODY%}}</code>. Note that this function is not very robust, it cannot handle nested tags properly.


====include specially labeled text portions====


To include '''sections which are labeled''' with special tags, you just mention the tag name. Refer to [[mw:Extension:Labeled_Section_Transclusion|Labeled Section Transclusion]] for details on how to label sections in your pages accordingly: 

:<code>include=sec1,sec2,...</code>

If the section name starts with <code>*</code> (asterisk), the asterisk is cut off and the rest of the text is taken as a regular expression. If the section name is <code>**</code> it matches all section names. In both cases, the tag name precedes the output, separated by <code>::</code>.

'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: include (example 7)|Example}}
{{ViewTest|Examples|Parameter: include (example 7)}}


====includematch====
See <code>{{DPL|includematch}}</code> for regexp content selection, using Perl regular expressions.


====include nothing====


To '''include nothing''' from the page (no inclusion), leave blank (this is '''default'''):
:<code>{{DPL|include}}=</code>
* A single <code>-</code> sign has the same effect; such a dummy parameter can be useful if you want to put content into columns of the output table which is not derived from the include statement


====Combinations of the above possibilities====


All of the above can be combined, you can even refer to the same template or heading more than once.

:<syntaxhighlight lang="wikitext" copy inline>include = {template1}suffix1,{template1}:p1:p2:2,#headline,marker,...</syntaxhighlight>


'''Example:'''<br>
<syntaxhighlight lang="wikitext" copy inline>include = foo,#bar[200 ..more..],{boo}.dpl</syntaxhighlight>

This would include:
* A text portion named "foo" which is marked by special tags.
* The contents of a page section named "bar"; only the first 200 characters of wiki text are shown; if the chapter is larger than that, a link with the text "..more.." points to the source.
* The output of template "boo.dpl" being called with the same parameters that were used to call template "boo" in the original page.
* See also <code>{{DPL|includematch}}</code>.


===includepage===
{{DPL Parameter
 |name   = includepage
 |purpose= This can be used as a longer name for <code>{{DPL|include}}</code>.
}}


===includemaxlength===
{{DPL Parameter
 |name   = includemaxlength
 |purpose= Delimit the size of an included article to a maximum of ''n'' number of characters. Only used with <code>{{DPL|includepage}}{{=}}*</code>.
}}


'''Syntax:'''<br>

<code>includemaxlength=''n''</code> - where ''n'' is an integer.

'''Example:'''<br><br><!-- transclude example from subpage-->{{#lsth:Examples/Parameter: includemaxlength (example 1)|Example}}
{{ViewTest|Examples|Parameter: includemaxlength (example 1)}}


===includetrim===
{{DPL Parameter
 |name   = includetrim
 |purpose= Removes all leading and trailing whitespace from transcluded contents.
}}


'''Syntax:'''<br>

<code>includetrim=true</code>   (default is ''false'')


'''Note:''' This parameter is only useful in combination with <code>{{DPL|include}}</code>.
[[Category:Primary Module|04]]