Search results

* the output of a surrogate template (phantom template) which is used instead of the original template ...you can '''include the output of a 'surrogate' template''' (also called a 'phantom template'). DPL calls this template instead of the original template with t

...you use <tt><nowiki>[[{{{%PAGE%}}}|{{{%TITLE%}}}]]</nowiki></tt> within a phantom template. ...the include statement, you will have to provide as many headlines as the ''phantom template'' produces columns.

...de</tt> statement. So, if you call a dummy parameter only or if you call a phantom template that does not produce any output, you will see no matches. It is,

If you want to do it automatically, you could use a DPL phantom template to create csv syntax. The csv text produced would then appear on t ::The phantom template is always called with the original parameters plus some general pa

; %CATLIST% : is now available as a local variable in phantom templates ;phantom templates: now support additional variables: %DATE% and %USER%

...le statement and use a phantom template which produces table rows. In this phantom template you can put a [[{{{%PAGE%}}}]] parameter in whatever column you li ...tt>include</tt> statement. So you would have to use a surrogate template ('phantom template') which could use the %variables%. But this works only if there ex

...about the first (i.e. the ''article cell'') one? Probably do I must use a phantom template? --[[User:Briotti|GB]] 20:46, 28 July 2008 (CEST) ...a different way you must take over control completely by writing your own phantom template. The ''table'' statement tries to keep syntax simple ... [[User:Ge

:Hello Kay,<br />I suggest you do the following: Create a phantom {{Source/dpl}} with the following code <code><nowiki>{{{Source}}}</nowiki><

== D: invoke a ''phantom'' template == == D1: use template parameters without ''phantom'' template ==

== includematch with phantom templates == ...new problem! :-P It is about the includematch criteria in reference with a phantom template.

Second, after some experimenting I found a work around (using a phantom template). You can urge DPL to use double pipes and you can add a trailing ...xplicit "format" specification and the include statement must refer to the phantom template. So we get:

* change the sequence of fields and apply a nested DPL within a phantom template [[DPL Example 004]]

...mple|Create a sortable table of articles based on template parameters, use phantom template with subquery}} As we want full control over the fields and formats of each row we use a phantom template (surrogate template).

...venience we output the columns in different sequence. Therefore we need an phantom template [[Template:Country.listByCapital]] to format the output of each li ...tandard column arrangement from Example 001 we could have done without the phantom template. In this case we would have had to sort table #1 by column #2.

:Use a phantom template and a #replace statement to throw away everything except the text