Browser: Chrome 133.0.6943.98 OS: Windows 11 Video: Synology Drive
Hello everyone,
I have discovered a strange behavior in Bricks in connection with Bricksable elements. Whenever I delete or move a child element, the content is not updated. It still appears as if the child element is still in place, although it is not. Only when I then move the element somewhere else or refresh the page is the real state displayed, which can be very annoying because, depending on the workflow, there are frequent pagereloads. Is this problem unique to me, or have I discovered a bug? I would be very happy to receive feedback.
Kind regards
David Weninger
that’s an interesting one. Can you also reproduce it with native nestable elements? Or it’s only happening in this exact element?
Can you try maybe this way:
When you open a builder, make sure that “nestable” is set to false
Set “nestable” to true
Refresh builder
Check if it’s still happening.
You can also try to disable all caching and other plugins. But it would be good if you coul also reproduce it in native brick elements, then we can check what’s happening.
Thank you for the quick reply. I followed your instructions without success. I can’t reproduce the behavior with native Bricks elements. I guess because these constructs are made of base elements, such as blocks? The problem occurs with elements from Bricksable and with self-programmed elements where the user has no option to toggle the “nestable” property. Sometimes it seems to work without any problems, but if the last child element is removed, for example, it remains visually and is only removed after a page-reload. I have not and have not yet installed a cache plugin. I’ll test the whole thing again in a fresh Wordpress and Bricks installation.
I have just made another interesting discovery. Apparently the problem is related to the removal of the last child element. If there is more than one child element, removing or moving elements seems to work fine. As soon as the last child element is removed and the nestable parent element becomes empty, the last child element remains visually. If further elements are then added and removed, all these elements remain visually in place. I have attached another video.
I see. Hmm, do you see any errors in the console? I’m undecided if this is somethig that is Bricks or Bricksable issue.
You mentioned that this occurs also with self-programmed elements. Did you create any, that have this issue? If yes, can you create a minimum, most simplistic example, and send it over, so I can test on it?
I have now been able to reproduce the problem with the native Bricks element “back to top”. The problem also shows up in a fresh Wordpress and Bricks installation (see video). The problem exists in Google Chrome as well as in Firefox and Safari. No errors are displayed in the console.
thank you. I was able to reproduce the issue locally. I’ve added it to the local bug tracker.
From what I tested, it seems that (at least for “Back to top” element), if I switch between breakpoints, it does then render correctly (most of the time).