Jump to content
This wiki has been automatically closed because there have been no edits or log actions made within the last 60 days. If you are a user (who is not the bureaucrat) that wishes for this wiki to be reopened, please request that at Requests for reopening wikis. If this wiki is not reopened within 6 months it may be deleted. Note: If you are a bureaucrat on this wiki, you can go to Special:ManageWiki and uncheck the "Closed" box to reopen it.

General usage and invocation syntax: Difference between revisions

fixed
m (→‎Scrolling: clean up, replaced: [[zh:Extension::{{subst:BASEPAGENAME}}]] → [[zh:扩展:{{subst:BASEPAGENAME}}]])
(fixed)
Line 24:
;Parsing procedure
Wiki markup expansion ''does not take place'' before the commands are handed over to the extension module.
* This may be useful if you want to pass wiki syntax elements to DPL3 as arguments (see the <code>[[{{dpl3|format]]</code>}} option, for example).
* [[mw:Magic words|Magic words]] like <code><nowiki>{{PAGENAME}}</nowiki></code> or <code><nowiki>{{CURRENTDAY}}</nowiki></code> '''cannot''' be used.
* Template calls like <code><nowiki>{{{some template}}}</nowiki></code>, cannot be used as parameters.
Line 97:
 
==Built-in variables==
Within a DPL statement you can use some [[DPL format variables|variables]] which are implicitly set by DPL.
Example: %TITLE%, %PAGE%
 
Some [[DPL format variables|variables]] can only be used in the header or footer, like e.g. %PAGES%, %TOTALPAGES%
 
==URL parameters==
DPL understands a couple of parameters which can be passed via an URL specification. These URL-parameters all start with DPL_:
* DPL_count: influences the [[{{dpl3|count]]}} parameter (in fact it overwrites the value specified within the DPL statement)
* DPL_offset: influences the [[{{dpl3|offset]]}} parameter (in fact it overwrites the value specified within the DPL statement)
* DPL_refresh: if used with a value of 'yes' this will clear the DPL cache
* DPL_fromTitle: restrict the selection to articles with a page title greater or equal to the specified value
Line 166:
<center style="border:1px black solid"><big>'''''Normally DPL does not return its own page in the result.'''''</big></center>
 
* The parameter <code>[[{{dpl3|skipthispage]]</code>}} gives you control over this behavior. By setting it to ''no'' you can allow self references in DPL result sets.
* You can suppress back references to a page containing a DPL query by using [[{{dpl3|reset]]}} and/or [[{{dpl3|eliminate]]}}.
 
==Symbol replacement in ''mode=userformat''==
Line 197:
resultsfooter=«/nowiki»«/pre»
 
The same effect can be achieved with <code>[[{{dpl3|debug]]}}=5</code>.
 
==Table output==
We'd also like to point out that there are two special commands named [[{{dpl3|table]]}} and [[{{dpl3|tablerow]]}} which make it quite easy to produce output in table form.
 
==Scrolling==
Line 207:
The command <code>scroll=yes</code> must be given to enable scrolling.
 
DPL can take certain URL parameters from the command line, like &DPL_fromTitle and &DPL_toTitle. If these arguments are given the commands <code>title&gt;</code> and <code>title&lt;</code> will implicitly be set. Within the [[{{dpl3|resultsheader]]}} and/or [[{{dpl3|resultsfooter]]}} you can call a template which generates links to fetch the next / previous page.
 
See [[DPL Example 027]] for details.
 
Basically the idea of backward scrolling is that the SQL statement produces a DESCENDING order (with titles below the threshold). Internally DPL buffers the SQl result set and reverses its order. So the user will see a page of entries directly below the threshold, but in ascending order.
Anonymous user
Cookies help us deliver our services. By using our services, you agree to our use of cookies.