After the latest update from Bricks and the introduction of the feature “Code review” allowing users to view all codes and functions, I have observed an issue that I believe requires attention.
It appears that some data is being saved on each Bricks page, even after it has been deleted from the Builder. This includes custom codes, echo functions, and other elements. This data does not seem to be sourced from the old History or Revision features. Furthermore, these remnants of deleted content are only visible within the Bricks Builder interface for each page and are not displayed on the frontend. and it’s stored in this script ‘<script id=“bricks-builder-js-extra”…’
data like this: {"id":"811a62","name":"button","parent":"b509c1","children":[],"settings":{"text":"Back to the homepage","style":"primary","_cssGlobalClasses":["btn--primary","lmneir"],"link":{"type":"meta","useDynamicData":"{echo:get_home_url}"}}},{"id":"86ec75","name":"div"
Many deleted IDs and their content are still inside that script.
I’m not sure why we’re keeping this old and deleted stuff. Could you look into it and let us know why it’s happening? And if there’s a way to stop it from holding onto old content, that would be great to know too.
@Ahmad This script contains various information needed inside the builder but shouldn’t contain any no longer existing page data.
I’m happy to look at your site to replicate and debug the issue. Could you email us at help@bricksbuilder.io some WordPress admin login details, plus the builder URL where this data is located and a link to this forum post. Also, which data are you referring to exactly?
We built a WordPress plugin to clean up the trash data from the database. It searches for elements whose parent does not exist (orphans) and lets you delete them.
We found trash data on all of our website and cleaned it up using our tool.
We are considering to release the plugin to help the Bricks community. Even better would be a bugfix directly in Bricks
You can identify the issue when you install the Cleaner plugin on a Bricks WP instance with a lot of content. The orphaned elements will then be displayed as shown in the screenshot. We encountered this issue on 5 out of 5 instances ourselves and used the plugin to clean up the database.
We’re running into this same issue. Seems it’s still not resolved. We’re just switching to bricks and it’s leading to hours of confusion. Been wondering if Bricks is something we have the time for because of this as it’s been such a headache. Tried to see if we could get the plugin and unfortunately the link is yielding a 404.
EDIT Turned out that I was editing in a breakpoint and didn’t notice it. Thanks Matej!
from your descriptions, I would say that this is actually the same issue as the one mentioned here: SOLVED: Copy Paste full page creates artifact doms - but possibly with different steps to reproduce it.
We are working on a solution, that will notify you if the elements like this exists, and you will be able to remove it. We also identified a few options, how this element could be generated and we fixed them.
To fix the issue, you can copy-paste all top-section elements individually (not with copy-all), and the issue should be gone.
But, if you can update the website to the 2.0 beta (on staging!), then I suggest that you enable “Orphaned element checker” here: Bricks 2.0-beta Changelog – Bricks, and try to save the page you have issues with.
Thank you so much Matej, appreciate your quick response. As we determined over email this was a user error on my part as I hadn’t realized I was editing within one of the breakpoints.
