SOLVED: Unlink component breaks Nested component

[HOSEIN]

Browser: Chrome 137.0.7151.41
OS: Windows

Hi team,

After we unlink a component, the Nested component breaks.

Just out of curiosity, once this bug is fixed, what happens to the Nested component after the parent component is unlinked? Will it still be a component, or will it be unlinked like the parent component?

Thank you

[Matej]

Hey @HOSEIN,

is this happening only on imported components, like you reported here:

WIP: Bricks 2.0 Beta: Unlink component breaks the components that were imported

Browser: Chrome 137.0.7151.41 OS: Windows Hi team, If we import a component, add it to the canvas, and then unlink it, it will completely break. In fact, after Unlink, the internal elements of the component are deleted. In the video below, the component I add has already been imported. [Unlink component]

Or you can also replicate this on a component that you created inside the builder?

@HOSEIN

Just out of curiosity, once this bug is fixed, what happens to the Nested component after the parent component is unlinked? Will it still be a component, or will it be unlinked like the parent component?

I think it should be unlinked, just like parent one.

Best regards,
Matej

[HOSEIN]

@Matej

is this happening only on imported components, like you reported here:

Hi Matej,

No, I tried this before reporting it. It doesn’t matter if the component is imported or newly created.

[Matej]

Ahh, I see. I missed that it needs to be a nested component. My bad.
It might be the same issue, but I still created a separated internal task for this.

Also, I’m not sure if we will decide whether the nested one should also “unlink” or not.

Thank you,
Matej

[Victor1999]

I think it should be unlinked, just like parent one.

I think it would make more sense if the child component remained as a component by unlinking the parent component. In fact, this is the behavior that also exists in webflow component.

I suggest that if you have time, you should definitely analyze the Webflow component. It can help a lot in improving the component in bricks. For example, in Bricks we can’t create a new component inside a component. We have to create it outside the component first and then add it inside another component. And many other things that need careful consideration.

Best regards

[timmse]

We’ve fixed this issue in Bricks 2.0.2 now available as a one-click update in your WordPress Dashboard.

Please take your time to read the changelog entry before updating: Bricks 2.0.2 Changelog – Bricks, and let us know if you continue to experience issues.