Nesting a layout field inside a block — is the Panel performance issue still a thing?

The CMS Questions
1

Hi, I’m a beginner just getting started with Kirby CMS.

I wanted to build a block on my site that contains a layout field inside it (so, layouts nested within a block). However, an AI suggested that this approach can seriously slow down the Panel — slower page loading and saving — and pointed me to issue #6734, which was reported against Kirby 4.4.1.

So my question is: does the problem described in that issue still exist, or does this kind of nesting work fine in the current version of Kirby? As a beginner, should I simply avoid putting layouts inside blocks?

Thanks!

2

It will depend a lot on your exact blueprint setup - a blanket “this will be slow” isn’t correct. Especially not after the changes in 5.2 that the discussion in the issue you linked mentions. Kirby 6 should then also get a lot more performant around Panel fields, but that’s currently still in the alpha state.