Difference between revisions of "Issue:Extending includepage"
Line 35: | Line 35: | ||
== Reply == | == Reply == | ||
− | |||
{{#dpl: | {{#dpl: | ||
− | | titlematch = City % | + | |resultsheader=«googlemap version="0.9" lat="10.0" lon="11.0" zoom="10"»\n |
− | | include | + | |resultsfooter=\n«/googlemap» |
− | | format | + | |titlematch= City % |
+ | |include = {~googlemap.*}.dpl | ||
+ | |format = ,,\n, | ||
}} | }} | ||
− |
Revision as of 11:43, 10 October 2009
Description: | Includepage support for parser extension calls with parameters |
Extension / Version: | DPL / 1.8.9 on MW 1.15.1 |
Type / Status: | Change Request / open |
Problem
It would be very useful if includepage could be used with parser extension calls with parameters such as the Google Maps extension. Say you have several pages describing cities where each uses the Google map extension. If this new feature was added, DPL could be uses to collect the content of all parser extensions calls and generate a google map with all cities.
Example:
City A:
<googlemap version="0.9" lat="10.00000" lon="11.0000" zoom="10"> 10.00, 11.00, City A </googlemap>
City B:
<googlemap version="0.9" lat="12.00000" lon="13.0000" zoom="10"> 12.00, 13.00, City B </googlemap>
DPL could then generate something like this:
10.00, 11.00, City A 12.00, 13.00, City B
This change request relates to this question in the FAQ.
Reply
<googlemap version="0.9" lat="10.0" lon="11.0" zoom="10"> Template:Googlemap.*.dpl.default 10.2,11.2, halo 10.1,11.0, hala2 (A) 10.00, 11.00, This is City A (X) 10.1, 11.1, A suburb of City A 9.9,11.1, hals2 khj ih iu li 9.9,11.2, hald2 9.9,10.8, half2
</googlemap>