WAIT: Multiple Component Issues in Bricks Builder 2.0.1

Bugs
1

Browser: Chrome 110
OS: Windows
URL: Builder

Issue #1: Component Content Disappears After Adding/Editing Property Groups

Description

When adding groups to properties in an existing component or editing existing groups, the entire component content disappears.

Steps to Reproduce

  1. Create a new component without property groups
  2. Add properties directly without groups
  3. Save the component
  4. Component works correctly and displays
  5. Later decide to organize properties into groups
  6. Create groups in the component
  7. Map existing properties to these groups
  8. Save changes OR
  9. Edit existing groups in a component

Expected Behavior

Component should continue functioning normally after reorganizing properties into groups or editing existing groups.

Actual Behavior

  • Entire component content disappears
  • Unlinking properties doesn’t resolve the issue
  • Only solution is to recreate the component from scratch

Issue #2: Default Property Values Not Saved Properly

Description

Not all properties with default text or images are actually saved. Icons particularly require manual setting of size, color, etc. for each instance.

Specific Problems

  • Icon properties don’t retain default size and color settings
  • Each icon needs manual configuration of size, color, and other attributes
  • Very inefficient workflow, especially with grids containing 6+ blocks
  • Cannot be controlled via CSS classes
  • Need to add size and color instructions in field notes for users

Impact

This makes component creation extremely slow and forces users to manually configure basic styling that should be inherited from defaults.

Issue #3: Components Cannot Be Duplicated

Description

There’s no way to copy/duplicate existing components. When creating derived components, everything must be built from scratch.

Impact

Significantly slows down development workflow when creating similar components or component variations.

Issue #4: Nested Components Deleted on Unlink

Description

When unlinking a component that contains nested components, the nested components are deleted instead of being preserved.

Expected Behavior

Nested components should remain intact when parent component is unlinked.

Issue #5: Unlink Confirmation Popup Button Issue

Description

In the system popup for component unlinking, only part of the confirmation button is clickable - specifically just the text area. Clicking on the button edges doesn’t trigger the action.

Steps to Reproduce

  1. Try to unlink any component
  2. Click on the edges of the confirmation button in the popup
  3. Action doesn’t execute

Expected Behavior

Entire button area should be clickable for confirmation.

Environment

  • Bricks Version:2.0.1
  • WordPress Version:6.8.2
  • PHP Version:8.1

Temporary Workarounds

  • Issue #1: Create groups before adding properties to avoid this problem
  • Issue #2: Add detailed instructions in field notes for users
  • Issue #3: None available - manual recreation required
  • Issue #4: Be cautious when unlinking components with nested elements
  • Issue #5: Click precisely on the button text, not edges

Has anyone experienced similar issues or found any fixes for these problems?

2

Hi @peter.hrnciar and welcome to the forum :partying_face:.

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.

  1. 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?

  2. I don’t understand this one. How can I replicate the issue? What is not saving?

  3. 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.

  4. 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.

  5. You mean this confirmation:

    CleanShot 2025-08-05 at 10.37.36@2x
    CleanShot 2025-08-05 at 10.37.36@2x844×388 16.3 KB

    If yes, this is a browser default confirmation dialog and so, we don’t have any control over it.

Best regards,
Matej

1 Like
3

Hi @Matej,

For issue 2, add an image property to the component selecting a specific image size as the default. I have a set of custom image sizes defined in functions.php.

Add the component to the page and when you go to select the image for the component, the default size is not set, instead the first size at the top of the list of image sizes is selected.

4

Hi @simon,

I see, and can replicate this. However, this setting, the way it works, is related to that exact image. You can only choose it after you select the image, so I don’t think it should be connected. If it was it’s own control, then yes.

Best regards,
Matej

5

Ok, understood, thanks.