This is more a follow up of this bug, which was previously fixed. But there’s a situation where it still fails.. when the nestable element itself is set as a component.
Steps to reproduce..
Similarly to the previous report, as none of the Bricks native elements use this exact combination of both using render_builder AND being nestable, to reproduce you need to add a custom element that does. Here’s a plugin for a reduced test case, adding one test nestable element which does - GitHub - wplit/nestable-element-bricks · GitHub
-
Add the nestable element with a text element inside.
-
Turn that nestable element into a component, and add a prop to populate the text element.
-
Inside the builder you’ll notice the text element never shows the prop value.
-
The known workaround is to wrap in a block, and then make the block the component instead. The issue only happens when a nestable element using the ‘bricks-element-children’ is set to be a component itself.
Screen recording showing how it typically works with other elements being components, and then showing it not working with the test element - Prop on text element is populated in builder, accept for when the component is a nestable element.