SOLVED: Bricks v1.8 issue with repositioning elements in Nav nestable

The problem

Dragging elements around in the structure panel within the nav nestable sometimes causes an error, and moves the element into the wrong place.

Message in console..

'element zrikfn has a different parent ID'
'Moved element to the root'

Basically it can’t find the parent element when it’s being repositioned, and so is just then just positioned at the root. Sometimes clicking the element forces into the correct position, sometimes not, it remains at the root until the builder is refreshed.

It can be replicated by following the steps;

  • Add an image element to a page.
  • Add a nav nestable element to the page.
  • In the structure panel, move the image inside a dropdown. Then move it back out to inside another element (outside of the dropdown).
  • Notice the error in the console.
  • Moving it in/out of the mega menu will keep causing the same issue.

Video showing it

https://komododecks.com/recordings/kVDFsw30CTlfurjnyTjD

Extra info - i had actually bumped into this issue when testing out some ideas for a new custom element, (that I didn’t end up building in the end) with some of the v1.8 betas, the only similularity was that it was also a nestable element, like this dropdown is, also had an HTML structure (not just a container containing the child elements only) and that there was no x-template using render_builder function. Haven’t seen this with any others (but also haven’t tried any other nestable elements that don’t use render_builder before).

Hi David,
Thanks so much for your report!

I was able to reproduce the issue and added it to our bug tracker.

Best regards,
timmse

Hi,

If it helps, I’m just adding that I was able to replicate with the nestable slider quite easily also. Maybe this has been an issue for a while, I’m not sure. I haven’t really been using this element.

Thanks for the additional info, David!

We’ve tested these moves on the current development version: moving an image in and out of a normal dropdown, a mega menu, and a nested slider placed it correctly without the reported console error, and the relationships persisted after saving and reloading. We’re marking this as solved based on those results. If you can still reproduce it in the latest Bricks release, please share updated steps to reproduce it.