Controlling output volume

Manual	Parameters	Controlling output volume

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

resultsheader	Output a headline, before DPL3 results, if there is at least one article to display.

Syntax:

resultsheader=some wiki text

Example:

This selects articles in Category:Dessert examples and uses mode=userformat to get complete control over the output. listseparators= is not set, so nothing will be displayed except the results header. The resultsheader value sets the text for a message about the existing number of articles.

{{#dpl:
|category = Base Dragons
|resultsheader = <i>There are %PAGES% Base Dragons.</i>
}}

Notes:

%PAGES% - Outputs the number of articles in the result set. If the query result is limited (by system settings or by the count parameter) %PAGES% only shows the upper limit.
%TOTALPAGES% - Outputs the number of articles in the result set, regardless of count limits, which may consume extra resources; it is only calculated if used.
%VERSION% - Displays the current DPL3 version (see also Special:Version).
The symbol ¶ or \n 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 oneresultheader is specified as well, the latter is used in case there is exactly one entry in the DPL3 result set. resultsheader is only used if there are two or more entries in the result set.

resultsfooter

resultsfooter	Output a 'footline', after DPL3 results, if there is at least one article to display.

Syntax:

resultsfooter=some wiki text

Example:

This selects articles in Category:Dessert examples and displays them with default unordered list (bullet) formatting. The resultsfooter value sets the text for a message about the number of existing articles.

{{#dpl:
|category = Base Dragons
|resultsfooter = <i>There are %PAGES% Base Dragons.</i>
}}

Notes:

%PAGES% - Outputs the number of articles in the result set. If the query result is limited (by system settings or by the count parameter) %PAGES% only shows the upper limit.
%TOTALPAGES% - Outputs the number of articles in the result set, regardless of count limits, which may consume extra resources; it is only calculated if used.
%VERSION% - Displays the current DPL3 version (see also Special:Version).
The symbol ¶ or \n 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 oneresultfooter is specified as well, the latter is used in case there is exactly one entry in the DPL3 result set. resultsfooter is only used if there are two or more entries in the result set.

oneresultheader

oneresultheader	Output a headline, before DPL3 results, if there is exactly one article to display.

Syntax:

oneresultheader=some wiki text

Notes:

The symbol ¶ or \n is converted to a newline symbol. You may need this if the wiki parser requires a linefeed to understand your wikitext.
%VERSION% 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

oneresultfooter	Output a 'footline', after DPL3 results, if there is exactly one article to display.

Syntax:

oneresultfooter=some wiki text

Notes:

The symbol ¶ or \n is converted to a newline symbol. You may need this if the wiki parser requires a linefeed to understand your wikitext.
%VERSION% 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

noresultsheader	Output a headline if there is no article to display (empty result).

Syntax:

noresultsheader=some wiki text

Example:

The first example selects articles from a nonexistent category, to cause the noresultsheader output to display (for example purposes), the second uses a non-breaking space   to output no result, and the third uses \n to display output no result.

A)
{{#dpl:
|category=notArealCategory
|noresultsheader=<i>No results found</i>
}}

B)
{{#dpl:
|noresultsheader= 
|category=notArealCategory
}}

C)
{{#dpl:
|noresultsheader=\n
|category=notArealCategory
}}

Notes:

Setting a single blank or newline character (noresultsheader=  or noresultsheader=\n) suppresses the warning message from DPL3 that is normally issued if no articles are found.
The symbol ¶ or \n 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.

suppresserrors	Suppress the warning message if no matching article was found.

Syntax:

suppresserrors=true

Notes:

Setting suppresserrors to true has the same effect as setting noresultsheader to a single space character. The command is provided for downward compatibility reasons with older DPL versions.
See also: debug.

noresultsfooter

noresultsfooter	Output a footline if there is no article to display (empty result).

Syntax:

noresultsfooter=some wiki text

Note: noresultsfooter is essentially the same as noresultsheader. If there is no output to display, the difference between header and footer becomes incredibly marginal.

Adding metadata to the output

addcategories

addcategories	Shows all categories to which an article belongs as a small text line after the article name.

Syntax:

addcategories = true

Example:

This selects pages that begin in "Appl" and "Oran", each followed by a list of categories they belong to.

{{#dpl:
|titlematch     = Appl%¦Oran%
|addcategories  = true
}}

Notes:

In mode=userformat the category list can also be referenced using built-in %CATLIST% (pipe separated) %CATBULLETS% (bullet separated) %CATNAMES% (comma separated).

addpagecounter

addpagecounter	Shows number of times the page has been viewed. This function is depreciated.

Example:

This selects the 3 most popular articles about dessert.

{{#dpl:
|category       = Dessert examples
|ordermethod    = counter
|order          = descending
|addpagecounter = true
|count          = 3
}}

Note: in mode=userformat the access counter can also be referenced as a built-in variable.

addpagesize

addpagesize	Shows the size of the page.

Example:

This selects pages from Category:Dessert examples and adds the page size after the page name, using addpagesize. ordermethod=size sets the order to be sorted by page size, and the order parameter set to descending reverses the usual order. count limits the results to 1, so this statement will show only the largest article in the category.

{{#dpl:
|category    = Dessert examples
|addpagesize = true
|ordermethod = size
|order       = descending
|count       = 1
}}

Note: in mode=userformat the size can also be referenced as a built-in variable.

addcontribution

addcontribution	Shows how much a user contributed to an article.

Syntax:

addcontribution=true — (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 variables %CONTRIBUTOR%, %CONTRIB% and %CONTRIBUTION% available to be used in your own format statement.

adduser

adduser	Requires `ordermethod=[...,]firstedit` or `ordermethod=[...,]lastedit` (where the `[...,]` signifies a complex ordermethod with extra parameters). If firstedit (or lastedit), `adduser=true` displays the user who made the first (or last) revision of the page. In this way, the parameter is equivalent to the `addauthor` (`addlasteditor`) parameter (see below).

Syntax:

adduser=true — (Default is false)

Example:

This selects and lists pages in Category:Fruit examples, appending each result with the author of the last revision.

{{#dpl:
|category    = Fruit examples
|adduser     = true
|ordermethod = lastedit
|count       = 3
}}

Note: If mode=userformat the user can be referenced using the built-in variable %USER%.

addauthor

addauthor	Show the user who created the article, cannot be used with `addlasteditor`

Syntax:

addauthor=true — (Default is false)

Example:

This outputs a list of pages belonging to Category:Fruit examples, which shows the user who edited the initial revision of that page.

{{#dpl:
|category  = Fruit examples
|addauthor = true
|count     = 3
}}

addlasteditor

addlasteditor	Show the user who edited the most recent revision of a page, cannot be used with `addauthor`

Syntax:

addlasteditor=true — (Default is false)

Example:

This outputs a list of pages belonging to Category:Fruit examples, followed by the last user who edited the page.

{{#dpl:
|category  = Fruit examples
|addlasteditor = true
|count     = 3
}}

Note: The same behavior can be achieved (and formatted) using:

|addlasteditor = true and
|format = ,\n* [[%PAGE%|%TITLE%]] . . [[User:%USER%|%USER%]]

addpagetoucheddate

addpagetoucheddate	Shows date/time of last change to the page according to the definition of the 'page_touched' field on Page_table. Requires ordermethod=[...,]pagetouched or ordermethod=[...,]title. ([...,] means complex ordermethods with an extra parameter before are allowed.)

Syntax:

addpagetoucheddate=true — (Default is false)

Example:

This outputs a list of pages belonging to Category:Dessert examples, prepending each result with the date of last change.

{{#dpl:
|category           = Dessert examples
|ordermethod        = pagetouched
|addpagetoucheddate = true
|count              = 3
}}

Notes:

In mode=userformat this date can also be referenced as a built-in variable %DATE%.
The formatting of the date can be influenced using userdateformat.
The date is translated to your local time zone (if defined in your preferences) or to the server's time zone.

addeditdate

addeditdate	If firstedit (resp. lastedit), `addeditdate=true` shows the date of the first revision/creation (resp. last revision) of the page. Requires ordermethod=[...,]firstedit or ordermethod=[...,]lastedit. ([...,] means complex ordermethods with an extra parameter before firstedit

Syntax:

addeditdate=true — (Default is false)

Example:

This outputs a list of pages belonging to Category:Fruit examples, prepending each result with the date of last revision.

{{#dpl:
|category    = Fruit examples
|ordermethod = lastedit
|addeditdate = true
|count       = 3
}}

Notes:

In mode=userformat this date can also be referenced as a built-in variable %DATE%.
The formatting of the date can be influenced using userdateformat.
The date is translated to your local time zone (if defined in your preferences) or to the server's time zone.

addexternallink

addexternallink	Add the URL of an external link to the output list.

Syntax:

addexternallink=true — (Default is false)

Note: The command makes only sense in combination with linkstoexternal.

addfirstcategorydate

addfirstcategorydate	Shows the date/time the article was added to one of the listed include categories. If there is more than one category 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 'category' 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" (addeditdate, etc.) parameters.

Syntax:

addfirstcategorydate=true — (Default is false)

Example:

This outputs a list of pages belonging to Category:Fruit examples, prepending each result with the time and date (formatted according to your local mediawiki date display preferences or the user preferences if user logged in).

{{#dpl:
|category             = Fruit examples
|addfirstcategorydate = true
|count                = 3
}}

Notes:

In mode=userformat this date can also be referenced as a built-in variable %DATE%.
The formatting of the date can be influenced using userdateformat.
The date is translated to your local time zone (if defined in your preferences) or to the server's time zone.

showcurid

showcurid	Page links will contain the current page ID, cannot be used together with `openreferences=true`.

Syntax:

showcurid=true — (Default is false)

Example 1:

This outputs a list of pages belonging to Category:Dessert examples; the hyperlinks to these pages would look normal (displaying their page name), but would use an additional MediaWiki parameter named 'curid' at the end of the URL, which contains the numeric ID of the page.

{{#dpl:
|category  = Dessert examples
|showcurid = true
}}

Notes:

A format statement could also be used to achieve (working) output: |format = ,\n* [²{fullurl:%PAGE%¦curid=%PAGEID%}² %PAGE%] (observed in an Parameter: showcurid (example 1)).
showcurid=true cannot be used together with openreferences=true.
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.

This function is currently non-working.

Example 2:

This selects pages in Category:Dessert examples, format provides very similar functionality to showcurid; the \n* creates a new line with bullet, then the MediaWiki magic word {{fullurl:}} is used to create the URL from %PAGE%, and feed the URL the %PAGEID% as a URL parameter external link. %PAGE% is then used as the link text. Using a magic word (or parser function) in the {{#dpl:}} method of using DPL3 requires special syntax, double curly {{ braces }} must be replaced with ²{ and }² respectively, and pipe | characters must be replaced with ¦ or {{!}}. The <span class="plainlinks"></span> wraps each link with a MediaWiki class to prevent the external link icon from displaying.

{{#dpl:
|category  = Dessert examples
|format = ,\n* <span class="plainlinks">[²{fullurl:%PAGE%¦curid=%PAGEID%}² %PAGE%]</span>
}}

Include contents from the articles in the result set

include

include	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 Labeled Section Transclusion. DPL3 comes with a modified version of Sanbeg's source, so there is no need for additional installation.

With include 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 include statement and table and tablerow. 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:

include=* — The character * functions as a wildcard.

Example:

This lists all contents of the article Apple. The format line uses __NOTOC__ to suppress the behavior where the page headings are automatically added to the current page's table of contents. Not specifying the page name other content in format parameter prevents the page name from being output before the result (the default behavior). If the format line is removed, the default behavior can be observed.

{{#dpl:
|titlematch=Apple
|include=*
|format=__NOTOC__,
}}

Note: you can use includemaxlength=n (where 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:

include=#heading1,#heading2,... — The character # is used as a prefix to the page section heading (chapter) name.

Specifying #heading1 includes text from 'heading1' (case-insensitive) until the next heading of the same or lower level.

Instead of the prefix #, @ can be used (the # may lead to problems in certain cases); @@ acts as a regexp comparison just as ## does.
Normally a text pattern is compared literally and it must match the whole headline of the chapter. If a double hash ## 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, .* must be added around the pattern. Correct regexp syntax must be provided; otherwise, runtime errors may be seen, no output received etc.

include = ##.*omethin.* — This matches a page section name like "This is something old" or "That Was Something Old".

Formerly, this example stated that if more than one section exists with the same name, only the first is displayed, similar to how Labeled Selection Transclusion functions); however, this currently includes all sections with the same name, and may appear differently in different result formats.

Example:

This matches (and selects) an article named "Grape" and includes the content of the page section (indicated by #) named "about" or "About" (include is not case-sensitive). The table styles are provided in the first table argument, followed by the remaining table headers. When using table format, if there is more than one section with the same name used on the result page, each section will be listed in a separate table row. If the table statement is removed, the page title will only appear once, followed by each section's contents listed one after the other, as can be seen in Parameter: title (example 1).

{{#dpl:
|titlematch = Grape
|include = #about
|table = class="wikitable sortable", Page, Section content
}}

Notes:

This functionality is also available as a separate parser function (called #dplchapter).
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:

include = #heading1,#heading2[n linktext],..., where n is the number of characters to include, and linktext 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 %SECTION% can be used in secseparators to fetch the section name, which may be useful to customize the text to include the (otherwise unseen) section name:

secseparators = ,[[%PAGE%#%SECTION%|more "%SECTION%"...]]

This variable is replaced by "article#heading" if used in secseparators. It is up to you to create a link from this text using normal wiki syntax if you wish.

Note: Content related to or involving filters may be non-working or incorrect; as such, this section may be removed at a later date.

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 : [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 "1" as a limit only shows the link (if the corresponding chapter in the article is not empty), "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 nowiki and pre tags are balanced). Therefore, the size of the included text can deviate from what you specified.

include sections (chapters) by a reference to their position on-page

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

Example:

This selects articles in Category:Fruit examples, it will include the first thirty characters if the first and third page sections, selecting these sections based only on their position on result pages.

{{#dpl:
|category = Fruit examples
|include = %1[30],%3[30]
|count = 5
}}

include contents related to templates

Syntax:

include={my template} — The character # 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, include={my template} displays the result of the template call with the original parameters used on the selected article page.

You need a space char or a line break after this statement before ending the #dpl parser function call because otherwise 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 {{My_template|...}}.

MediaWiki searches for template calls in the template namespace. Specifying {my template} also matches a template invocation like {{Template:My_template|...}}.
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 {{:my template|...}}.

You can include one or more parameters of a template call by specifying a list of names or position numbers separated by colons (and optional white space). Names are used for named parameters, numbers for positional parameters.

The following would include the values of the two parameters named 'age' and 'size' and the value of the first unnamed parameter in all calls of the template "animal":

include={animal}:age:size:1

It is even possible to use expressions which contain a % symbol as pseudo parameters:

include={animal}:age:%PAGE%:size:1

Example:

This selects articles in Category:Fruit examples and uses include to include the DPL variable for page title, the "image" parameter value, and the "grows" parameter value. The first argument of the table statement adds classes to the table, the second omits the (automatic) linked page name first column (using -, so the page name can be manually inserted without a link and formatted), and the rest of the arguments create the remaining page headers. The tablerow parameter allows the values to be precisely positioned within the formatting applied; the %TITLE% first column is given inside <i></i> (italic) formatting, followed by the "image" value formatted as a rendered image at 30 pixels wide, and then the "grows" parameter value displayed last.

Note: Since the last column value does not have formatting applied, the comma before it and its value ,%% could technically be left off (specifying an empty , suppresses the value from displaying). Without the comma, the column value would still appear because include automatically adds values as-is to the output, tablerow just allows precise positioning of values inside its column's formatting. However, to add more values after that one, that column's value would then have to be specified, simply to hold its position within the comma separated list. For this reason, it is generally good practice with tablerow to put all values from an include statement into the corresponding position of tablerow, it can helps avoid confusion on later edits and/or additions.

{{#dpl:
|category      = Fruit examples
|include       = {Fruit-Infobox}:%TITLE%:image:grows
|table         = class="wikitable sortable",-,Page Name, Image, Grows
|tablerow      = <span style="font-style: italic;">%%</span>,[[File:%%|30px]],%% 
|count         = 5
}}

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:

%PAGE% – Outputs the name of the article (including namespace), corresponds to the Magic Word {{FULLPAGENAME}}.
%TITLE% – Outputs the title of the article (without the namespace), corresponds to the Magic Word {{PAGENAME}}.
%DATE% – Outputs the date selected, e.g., ordermethod=lastedit; requires addeditdate=true or similar; the formatting of the date can be influenced using userdateformat=.
%USER% – Outputs the user who changed the article last; requires adduser=true or addlasteditor=true.
%CATLIST% – Outputs a pipe-separated list of links to all categories to which the article belongs (requires addcategories=true).

Example:

This selects the article Apple and includes the output of a surrogate template, since Apple doesn't use the specified template, instead of displaying the content of DPL3 displays a call to a template with the additional suffix ".default" giving the user a chance to either create the missing template, or correct the include/includepage reference.

{{#dpl:
|titlematch = Apple
|includepage = {Details}.example
|table      = class="wikitable sortable",Page,Surrogate template value 
}}

See Also:

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: {template¦surrogate template}.dpl. For example, you may specify something like {my template¦Help:Substitution for my template}.dpl.

As of DPL3 version 3.5.2, using {template¦surrogate template}.dpl causes the result to be "pre" tag escaped for no reason, preventing this feature's use.

include parser function calls

If a pattern like {#pfunc}.list 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 %PFUNC% and all parameters under their normal name or number. Instead of specifying a single parser function, a generic pattern can also be used.

Example:

This selects the Examples page, and includes all DPL3 parser function calls {{#dpl:}} used on that page. The parameters of each #dpl statement used on Examples are passed to, and can be used in, a surrogate template. The surrogate template specified ends in the chosen ".examples" suffix, resulting in: Template:dpl.examples; that surrogate only makes use of the {{{category|}}} and {{{ordermethod|}}} parameters, to pass those parameter's values to the output. The table statement applies default table formatting in the first argument (left empty, defaults to class="wikitable"), the second, third, and fourth arguments set the table header text. Since {{#dpl:}} was used more than once on the Examples page, one line of output for each instance appears (and table format separates these per line with a repeating title, where other formats may list the title once and the values thereafter).

{{#dpl:
|title = Examples
|include = {#dpl}.examples
|table = ,Page,<code>category</code> parameter value, <code>ordermethod</code> parameter value
}}

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

To find all parser functions, {#.+} can be used:

include={#.+}.pfunc

The .+' 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 {~func}.list is specified, DPL3 looks for calls of the parser extension (tag) with the tag name <func>. 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 %TAG% and the body contentis named %TAGBODY%. 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 Labeled Section Transclusion for details on how to label sections in your pages accordingly:

include=sec1,sec2,...

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

Example:

This selects the Apple Pie article, and includes the content of its <section begin="one" /><section end="one" /> tags (seen using source edit), as well including the values for section tags "two" and "three". The secseparators statement formats places a space, two dashes, and then a space before each result.

{{#dpl:
|title = Apple Pie
|include=one,two,three
|secseparators = &nbsp;--&nbsp;
}}

include nothing

To include nothing from the page (no inclusion), leave blank (this is default):

include=

A single - 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.

include = {template1}suffix1,{template1}:p1:p2:2,#headline,marker,...

Example:

include = foo,#bar[200 ..more..],{boo}.dpl

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 includematch.

includepage

includepage	This can be used as a longer name for include.

includemaxlength

includemaxlength	Delimit the size of an included article to a maximum of n number of characters. Only used with `includepage=*`.

Syntax:

includemaxlength=n - where n is an integer.

Example:

This selects the Some Page article, includes all * content, and then limits the length to 5 characters.

{{#dpl:
|title = Some Page
|include=*
|includemaxlength = 5
}}

includetrim

includetrim	Removes all leading and trailing whitespace from transcluded contents.

Syntax:

includetrim=true (default is false)

Note: This parameter is only useful in combination with include=.

Help

Help:Controlling output volume

From Dragon Mania Legends (DML) Wiki

Contents

Defining header and footer for the result

resultsheader

resultsfooter

oneresultheader

oneresultfooter

noresultsheader

suppresserrors (DEPRECATED)

noresultsfooter

Adding metadata to the output

addcategories

addpagecounter

addpagesize

addcontribution

adduser

addauthor

addlasteditor

addpagetoucheddate

addeditdate

addexternallink

addfirstcategorydate

showcurid

Include contents from the articles in the result set

include

include whole article

include page sections (chapters)

include contents related to templates

include parser function calls

include parser extension (tag) calls

include specially labeled text portions

include nothing

Combinations of the above possibilities

includepage

includemaxlength

includetrim