Include +content block from another page in a +content block

Everyone

I have a page template with a +content variable, which holds multiple sections (created in the block editor). In some sections I'd like to include content from another page. I'm trying to do this through a pagelist or filelist block. However the mentioned page also has a +content variable holding all kinds of blocks, including pagelist or filelist blocks. What happens is that included content from all blocks does show up correctly except pagelist or filelist blocks, for which only the markup without any elements inside gets created. Is this a bug or an intended behavior?

mad

Everyone Yeah it is kind of intended in order to prevent infinite loops. I hope I understand you correctly. Or maybe it would be enough to change just the page context in the template using the with statement in order to display content from another page.

Everyone

I think you understand me correctly. The thing is I don't want to hardcode an include directly in a template, because the project features a common group of sections, from which some or all will be repeated across many pages.

It could be worked around either by creating multiple templates with each combination (super-ugly) or by giving each section an option to toggle it on or off, which is less ugly, but still not very flexible or future-proof.

Is there a way to somehow cheat the system so that content generated by using the editor's pagelist/filelist blocks also shows, when the page is included by another pagelist/filelist block?

mad

Everyone You can try to solve that using the snippet block. That allows for rendering basically anything.

Everyone

Actually it doesn't work this way either. When a block type variable has content that pulls another block type variable containing pagelist or filelist, only the markup for those blocks will be generated with content completely omitted.

I think I'd have to write my own parser to make it work, but it's currently way above my knowledge and time constraints.

mad

Everyone The problem is that if that would be possible, it would be very likely that the webserver would get stuck in an infinite loop — a pagelist rendering pages that include a pagelist that is rendering pages that include a …

Everyone

Yes, I totally understand why this was implemented like that, I just wish there was some way to make it work. Do you think it would be feasible to implement a programmable recurrency limiter in the block rendering routines? So that one could instruct the pagelist block to quit going deeper after, say, 5 levels?

mad

Everyone I think it is somehow possible. However it would require heavy modifications of the engine in order to be aware at what level the current rendering is happening. I guess a simple one-dimensional counter won’t work here.