Hi @peter.hrnciar and welcome to the forum
.
For a future bug reports, it’s much better to create one topic per one report. That way, we can properly link and organize them internally.
But now to your reports.
-
I am unable to replicate it. My component had one property, and it was working. I’ve created a group, and assigned the property to that group, but the component was still working.
Can you export the component that is causing the issues, before you created a group, and record a video how and where you created groups, so I can replicate it with same setup as you? -
I don’t understand this one. How can I replicate the issue? What is not saving?
-
That’s true, there is no way to duplicate the component now. We have it on the roadmap though. (It’s also not a bug). We will update the following topic, once we release this improvement: WIP: Duplicate Component feature
Ps. There is a dirty workaround for this. You could export the component, change the ID of it, and import it back. -
Thank you for your repot. I can confirm that this is an issue and it was already reported here: WIP: Bricks 2.0 Beta: Unlink component breaks Nested component - #2 by Matej
We will update the topic above when we release a fix. -
You mean this confirmation:
If yes, this is a browser default confirmation dialog and so, we don’t have any control over it.
Best regards,
Matej
