Anonymous user
Other parameters: Difference between revisions
replaced: tt> → code> (56)
No edit summary |
(replaced: tt> → code> (56)) |
||
Line 52:
The third group of rules is common to both other groups and controls the update process.
The <
Line 116:
For safety reasons the update statements will only be performed if "exec yes" is specified. So, leaving this away, you can check what would happen if the update were to be executed.
Note that if "exec yes" is present the update will be performed each time the page is rendered which contains the DPL statement with the <
The size of the form fields will dapt to the size of the displayed content.
Line 123:
To make the use of the <
''text'' is plain text; ''replacement'' is text which may contain references (like \1) to the matching ''pattern'' (provided that this pattern contains match groups).
Line 209:
In some cases this may be useful. But in many cases this is not wanted. Especially when you use DPL to create a printable document which contains the full text of other articles you will probably not want to duplicate all links, template uses etc. of those articles.
The <
There are some subtle differences here depending on the mode in which you use DPL. These differences affect the question how links, and categories etc. are treated which are direct part of the document containing the DPL query.
Line 228:
;reset=links: will throw away all references to other pages, i.e. links contained in included contents and links like 'Q Link' will be ignored. This means that all links can be used in the normal "FORWARD" way, but no "BACKLINKS" are available for them.
If you want to avoid the above described effect of <
Line 238:
;reset=links: will throw away all references to other pages
As you see, using <
If you want to avoid the above described effect of <
If you have '''more than one DPL query''' in a document the effects will depend on the exact mode (parser extension or parser function mode), on the sequence of the statements and on the presence of 'reset' or 'eliminate' statements in each of the queries and on their individual arguments. As this is a very rare case we only give a simple rule of thumb here: Once you have used 'reset' in parser function mode or 'reset=links' in parser extension mode the effect of these statements will dominate the rest.
Line 249:
{{DPL Parameter
|name = fixcategory
|purpose= assign the article containing a DPL statement to a category although <
}}
Line 257:
Use multiple commands to assign the article to more than one category.
If you use <
As a side effect of using <
The <
===eliminate===
Line 273:
<code>eliminate=keyword,..</code>
Where <
* <
* <
* <
* <
* <
The output of a DPL statement typically creates links to all pages which are part of the result set. The inclusion of contents from other pages via DPL (using <
* the page containing the DPL query becomes part of the categories of the transcluded page
* shares ('adopts') their use of templates
Line 289:
In some cases this may be useful. But in many cases this is not wanted. Especially when you use DPL to create a printable document which contains the full text of other articles you will probably not want to duplicate all links, template uses etc. of those articles.
The <
For further explanation see <
Please note that the use of <
===debug===
Line 328:
DPL debug messages are translatable in <code>DynamicPageList2.i18n.php</code>. See also [[#Internationalization]].
'debug=1' will suppress warning messages (e.g. if the result set of a DPL query is empty). As an alternative, you can use the <
===execandexit===
Line 367:
See also: [[Template:Extension DPL scroll]] and [[DPL Example 020]] and [[Scrolling]]
Note <
=== cacheperiod ===
|