SOLVED: Gap problems with masonry layout (version 2.3.9)

Bugs
1

Quick question: does anyone else find that the masonry layout gap setting doesn’t set a gap between columns in bricks version 2.3.9? It sets the gap between rows, but not between columns. The gap setting works fine on image galleries with masonry layout, but not on other masonry layouts.

Thanks for looking into this.

2

Stuff works fine for me when creating a grid layout.

Services-Builder--07-11-2026_04_28_AM
Services-Builder--07-11-2026_04_28_AM1920×917 84.8 KB

3

Thanks for checking! Just to be clear, you’re using version 2.3.9?

4

Yes, I am using the latest WP and latest Bricks with a child theme.

What other things do you have setup? Plugins? Custom Code? Those can make a difference as well.

6

I also see issues with gaps in Masonry Layout when using the default flex.

7

Thank you. No plugins, and not much custom code. Curious to see if anyone else experiences this.

8

Hi @T-bone ,

Thanks for reporting the issue in the forum.
It’s a bug in 2.3.9, we are aware of the issue when using Masonry Layout, and already in our bug tracker.

Regards,
Jenn

9

I have the same problem. Looking forward to the fix

11

Any ETA on this? We’re about to relaunch our website, and this bug is breaking the layout on most of our landing pages.

13

I think the issue is that Bricks applies the selector ‘.bricks-gutter-sizer’ to the gutter parameter of isotope/masonry. According to the docs Isotope · masonry the horizontal space between elements will take the width of this element. But Bricks hasn’t set a width. So I’m using the following in my Bricks → Settings → Custom Code → Custom CSS as a work-around until a fix is released:

@layer bricks {
.bricks-masonry .bricks-gutter-sizer {
width: var(–gutter);
}
}

Don’t know if this is proper or will work in all scenarios but works for me.

15

Is it safe to simply re-upload v2.3.8, since that version didn’t have this bug, or could doing so cause any conflicts?

Version 2.3.8

Bricks-2.3.8
Bricks-2.3.82298×1304 270 KB

The scanner element has a calculated CSS left value of 34.2727% .

Version 2.3.9

Bricks-2.3.9
Bricks-2.3.92180×1230 264 KB

The scanner element has a calculated CSS left value of 31.3636% .

17

Hi @Borlabs-Ben ,

The fix for this issue is already merged into our next release code.

There is no actual ETA for the release yet.

You can re-upload 2.3.8 as a workaround for now.

Regards,
Jenn

18

Just tested this, and it works perfectly as a workaround. Thank you!

27

Thank you very much. That works like a charm.
Caution for copy&paste: This forum converted the variable’s two dashes to an mdash.

29

We’ve addressed this in Bricks 2.3.10, now available as a one-click update in your WordPress Dashboard.

Please read the changelog entry before updating, and let us know if you experience any issues.