I am able to edit my homepage with bricks 1.5.2 however when I update to 1.5.3 the loader crashes and I get a kill page popup from chrome. No changes made to the page between the updates. Other pages are editable.
If I downgrade back to 1.5.2 the page becomes ediable again.
Whilst the page is not editable on 1.5.3, it still displays the frontend fine.
I’ve made a video showing the issue - Afraid I can’t write a better bug report.
(Note that i’m not part of the Bricks team), but I’m pretty sure for a bug report they’ll need more info to get to the bottom of this. The video isn’t enough information.
ie steps to reproduce, or they’ll ask for access to the site to troubleshoot.
i can see from the URL you gave, that you have a few plugins active. AutomaticCSS, Max Addons, Motion Page… The first thing to test would be upgrading with these deactivated - to remove all external influences and narrow down the issue. Once you know it’s not being caused by another plugin, then it’s easier to solve (and hopefully easier to reproduce if it is a Bricks issue)
I’ve got this too! Same thing - all other pages work, but not the home page. I get the exact same eternal loading of the builder - but it never finally loads.
Since we both had this problem on the homepage, just for fun, I tried to change the home page to another page and gave it a go again. Still didn’t work on that page, even though it was NOT set to the homepage.
I tested with Site Health Troubleshooting mode, enabling Bricks but disabling all plugins. Still didn’t work.
I’d be happy to provide access to the site, but it’s not actually on a public IP, so you’ll have to change your hosts file to get access to it. Not hard for those who know how to do it.
There wasn’t much coming up in my console, though there was an uncaught promise relating to recaptcha__en.js
Regarding steps to reproduce, think it’s pretty explicit in the video. Afraid there’s not a lot more detail that I’ve access to in order to add more.
Though, I could do some additional debugging as you suggested. Just didn’t have any time yesterday.
We are looking into this right now. @intcultcom Thank you so much for the login details.
Can everyone who is experiencing this builder load issue temporarily switch to 1.5.2, save the affected page as a template, export this template, and share the JSON file here in this thread or email it to help@bricksbuilder.io? That’d be a great help to debug & fix this issue for everyone.
You can save a page as a template by clicking the template (folder) icon in the builder toolbar, then click on the save (disk) icon. Make sure you have not selected any elements on the page to ensure the entire page is saved as a template.
Also, have you guys created those affected pages from scratch with Bricks or via a pre-designed/imported template? If it’s a pre-designed template where is the template coming from?
Thanks, Chris. We got enough data & a fix now that we will include in the next update this week. Some of the elements of the Frames template had some odd IDs that caused an endless loop which caused the builder to hang. The fix includes additional data consistency & verification checks on builder load.
that we will include in the next update this week. Some of the elements of the Frames template had some odd IDs that caused an endless loop which caused the builder to hang. The fix includes additional data consistency & verification checks on builder load.