I am not sure why, But I cannot see the Bricks content in builder. It appears > I can see it in the structure panel, but I cannot see the elements in preview. What is wrong?
It happens for mine Custom Post Type “Event”. There are two templates for this cpt. The parent one, which contains the Post Content element set to Bricks. And the child one, created directly at the post with Bricks editor.
Then I can edit the post with Bricks again, but I need the parent template assigned for same hero section and contact form for each post… So, what I am doing wrong?
My final Verdict is that when editing single post with Bricks, which have Bricks single template assigned and contains post content module set to bricks, then the Bricks content is not visible for some reason.
I also encountered this (in Firefox) on a simple development site. The site only has a header template and a single page. Header template conditions was set to Entire Website.
I was using Automatic.css + Frames and the site had just been updated after not being used for a while.
I made a new header template and now everything works. Not an ideal solution for a normal site, but at least you’re not alone.
Just repeating what I shared over email for others that may be running into the same bug:
The bug occurs in the builder when the page contains an SVG element with the source set to “Code” and a single template is applied to that page. I have added this to our bug tracker.
In the Single Product template, no content is showing inside the Builder.
Even static elements (e.g., Heading, Button) do not appear in the Builder preview.
On the frontend, everything renders correctly.
This issue did not exist in previous versions, only started after updating to Bricks 2.0.2 for me.
@timmse is currently away, so I’ll check the issue instead. I was unable to replicate it locally, though.
What you could try is to clear all cache and disable all plugins, then you check again.
If it’s still not working, can you check if you see any console errors while in the Bricks editor?
it happened me too and I found out the reason - the hosting provider offered the server Litespeed cache, but didn’t exclude wp-admin, wp-ajax and other important endpoints.
