Hi,
Thanks for your response. That is a solution that might work, but the design I’ve been using relies on a single Container, and then loads template defintions based on a list defined in settings. The code that does that is here: https://pastebin.com/7HYhQ84b My plan was to use filters to modify the content of blocks, and which blocks were loaded, through filters, which does works (I can filter livy_block_load
to manually add or remove block types successfully)–but I’m not able to access conditionals that relate to the page being edited. I think this is because the hook that loads Carbon Fields happens to ‘early’, so that information isn’t available when this code is running.
I was hoping you might be able to shed some light on how the containers are made aware of what page they’re on, so that I might be able to adapt that to my workflow here. I’ve taken a look at the your code, but I haven’t been able to determine how it’s done.