template parameter does not work correctly

[chiefgeek157]

Using MW 1.25.1, I cannot seem to get the template parameter to work. Here are some examples using "Test Page", "Test Page/Subpage {1|2|3}", and "Template:Subpage list template" with the definition: "There is a subpage named {{{1}}}".

Works

Using parser function with defaults: {{#subpages:}}

• Subpage 1
• Subpage 2
• Subpage 3

Using parser function with pathstyle=full: {{#subpages:pathstyle=full}}

• Test Page/Subpage 1
• Test Page/Subpage 2
• Test Page/Subpage 3

Manually invoking template in a hand-built list:

* {{Subpage list template|Test Page/Subpage 1}}
* {{Subpage list template|Test Page/Subpage 2}}
* {{Subpage list template|Test Page/Subpage 3}}

• There is a subpage named Test Page/Subpage 1
• There is a subpage named Test Page/Subpage 2
• There is a subpage named Test Page/Subpage 3

Fails

Using parser function with the template parameter: {{#subpages:template=Subpage list template}}

• {{Subpage list template|Test Page/Subpage 1}}
• {{Subpage list template|Test Page/Subpage 2}}
• {{Subpage list template|Test Page/Subpage 3}}

It appears that the list is generated correctly, but the resulting output is not passed through the template renderer. This is apparently in part because FunctionRunner has no access to the Parser instance so cannot render the resulting text. Not sure.

Using tag mode with template parameter: <subpages template="My template"/>

<div class="subpagelist">
<ul><li> </li></ul>
<p>There is a subpage named Test Page/Subpage 1
</p>
<ul><li> </li></ul>
<p>There is a subpage named Test Page/Subpage 2
</p>
<ul><li> </li></ul>
<p>There is a subpage named Test Page/Subpage 3
</p>
</div>

HookRunner calls Parser->recursiveTagParse(), but the expansion is messed up. The content doesn't get put into the list item, but outside, and each item becomes a separate list. It appears that each list item is resolved into complete HTML as a separate list rather than waiting until all the items are combined to render into a list.

[JeroenDeDauw]

Thanks for reporting this issue!

[emanspeaks]

I had also seen similar behavior but had not had time to investigate the cause.

[amglez]

Hi
I am trying it with mw 1.31, and does not work either.

[JeroenDeDauw]

Unfortunately I cannot justify spending time on this without funding

[pwinkeler]

Hi Jeroen - I have a great interest in fixing the template rendering option of the Semantic MediaWiki SubPages extension. Do you have a rough idea of what amount of funding you might need to implement this properly?

[JeroenDeDauw]

@pwinkeler my current day rate is several 1000 EUR, which I suspect is on the high side for an open-source fix :) If you wish you can write me with your budget at [email protected] and I'll see if it is sufficient to put one of our devs on it.

[pwinkeler]

That is a bit too much for me to bite off, you’re right. Fortunately I was able to somewhat work around this by setting a property on all the subpages of interest that I can then use to uniquely identify them with a regualr #ask query. I do wish I had the time to understand the subpages code better so I could fix it myself but that will have to wait. Thanks for the response though, PaulW

…

On Aug 9, 2021, at 13:01, Jeroen De Dauw ***@***.***> wrote: @pwinkeler <https://github.com/pwinkeler> my current day rate is several 1000 EUR, which I suspect is on the high side for an open-source fix :) If you wish you can write me with your budget at ***@***.*** ***@***.***> and I'll see if it is sufficient to put one of our devs on it.