[SOLVED] behaviour of renderLayout changed?

[gebeer]

Hi @bernhard we just updated RockFrontend on a site from 3.20.0 to 3.23.3 and the site stopped working.

I fixed it by changing  templates/_main.php

<?= $rockfrontend->renderLayout($page); // worked before update ?> 
<?= $rockfrontend->render($page); // works after update ?> 

We use RockPageBuilder and in templates/sections/main.latte

<div sortable x-ref="additional-sections">
 {$page->get('rockpagebuilder_blocks')->render()|noescape}
</div>

Now after the update that threw an error on our home page because template home has no field rockpagebuilder_blocks

I am wondering why this is. Do you have any idea?

I looked at the function signature for render() and the examples in the PHPDoc do not mention that we can pass a Page object as $path argument. So I thought we could not call render($page) at all. But it works. I guess because $page is then overwritten with $this->wire->page.

So renderLayout($page) would be the correct method to use. But something in the inner workings of renderLayout must have changed and stopped the site from working.

I suspect that the way we have setup rendering with RockPageBuilder, RockFrontend and Latte is fundamentally wrong.

 

[gebeer]

Solved. It was indeed a problem with our setup, not with renderLayout().