Hi Diana
Thanks again for your patience.
Well, after talking to our Layouts developer it seems we will be getting a feature request for children layouts, so you can decide to wrap them on a container or not. So congrats and thanks for the feedback.
On the meantime, while this gets evaluated ane eventualy done, I am not that familiar with Bootstrap myself, but I believe that when rendering children layouts inside the parent, we were avoiding the extra wrappers to have a clearer output. It seems that when dealing with children layouts taking a full row, we avoid the natural cell wrapper and leave the whole strucuture to the children layout.
So I also have grey news for you. We have a couple of PHP actions running ehwn the cell starts and ends rendering, where you can modify the cell content, so this might be a matter of checking the cell type and doing it. The bad news is that you need to code the clution, and that we do not have public documentation for those ations yet. As you know, we are not supposed to provide code snippets on the support forum, so I am just going to add some info here so you can follow the dots 🙂
The action you should be hooking at is
ddl_before_frontend_render_cell
, and it takes two arguments: $cell and $renderer. The one you need to care about is the first one, which is the cell object. You can check its type by calling its cell method
, and then act when the cell type is the one matching a child layout.
Once you have targeted the righ cell type, you can get the cell content with the cell method
get_content_field_value('content')
, modify it and then save it back with the cell method
$cell->set_content_field_value('content', 'Your modified content goes here );
.
We will be documenting that action in the near future, adn as I said we are adding the option to wrap child layouts in the future. I know it might not solve your problem now, but thanks for your understanding.
Hope it helps.
Regards.