I too have used, and find very useful, nested pagelists. If there is a potential risk or problem with a global variable I'd urge that consideration be given to finding a way to remove the global variable.
tia Simon On 10 October 2014 08:39, StefCT <stef...@gmail.com> wrote: > On 10/08/2014 10:22 PM, Randy Brown wrote: > > > > I do find that a pagelist template that invokes another pagelist can be > > a /very/ useful technique. Would it be hard to make that work in some > > future version of PmWiki? > > I think I have repeatedly used nested pagelists but haven't encountered > any problems so far. > > For example, I have a page group in which coworkers can enter their > tasks (one page per task) and another group in which projects can be > created (one page per project). Now tasks can be assigned to projects by > simply mentioning the exact project title somewhere in the task > description (no extra page variables, link or category markup required). > > In order to display all corresponding projects to a task in the task's > group footer, I use two nested pagelist templates: The first one > iterates through all projects in the wiki and invokes the second > template with each project's title as a parameter. The second template > searches for said project title in the current task description and > creates a link to the corresponding project page only if the search is > successful. > > Seems to work fine so far. Is there any downside to be expected from > this solution? > > --StefCT > > > > > > _______________________________________________ > pmwiki-devel mailing list > pmwiki-devel@pmichaud.com > http://www.pmichaud.com/mailman/listinfo/pmwiki-devel > -- ____ http://kiwiwiki.co.nz
_______________________________________________ pmwiki-devel mailing list pmwiki-devel@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-devel