I am very confused about how the page rendering works in Bricks. Even after I use Bricks almost daily for 3-4 months now. Can someone please clarify the logic for me or point me in the right direction to create a robust workflow?
I am currently transitioning our website to Bricks. I have some “fancy” layout pages (Home, Contact, etc) that I built in the Bricks editor and I have the general pages that I don’t want to bother with building in Bricks (Imprint, Terms, legal stuff).
Now I have figured that I can use a page template in Bricks that can display both the Gutenberg content (previously stored from the old website) and the Bricks content via the building elements. I created this template:
Condition: Post type = Page
This is the structure:
First element is a Post content element, set to Bricks. It has no wrapper because all the page styling is done in page level. It has also a condition:
Dynamic data: {cf__bricks_editor_mode} == bricks
Actually I don’t remember where did I find the custom field that I use here but I have not found in the documentation, but probably in a YT video.
Second element is a wrapper for another Post content element that renders the Gutenberg blocks for the pages I didn’t want to convert. It has the opposite condition:
{cf__bricks_editor_mode} == wordpress
The problem with this approach is that this custom field is not consistent in my experience. Sometimes there is no Bricks content but the _bricks_editor_mode is set to bricks so the page tries to display the Bricks content (nothing) instead of the Gutenberg content.
I suspect that this approach is not the official method for a universal page template. What would be perfect is that there would be a switch (or maybe a custom defined custom field) that I can use to explicitly define which content should be displayed in a page template.
Is there an official method to switch between the content source of a page but using the same template?
Somewhere I have read there is another condition that I should use (echo:has_blocks) but somehow it doesn’t work for me.