SOLVED: Masonry not working while used in repeated gallery

Bricks: 1.9.4
Browser: Firefox 121 / Chrome 120 (independent imo)
OS: Windows
URL: Galeria zdjęć – Placówki Opiekuńczo – Wychowawcze w Powiecie Wodzisławskim

Hello, I’ve probably discovered a bug with the isotope implementation in bricks.

  1. Create an ACF Repeater with a gallery field, for one specific page. Make two+ rows with sample images.
  2. Create a query loop with containers with Gallery block, and use the gallery from the ACF repeater as a source
  3. Use a masonry layout
  4. The masonry (isotope) script works only on the first gallery

Hi @KamilMark ,

We are aware of the issue. The root cause is an update in 1.9.4
I have recorded your report as well.
We will tackle it soon. Sorry for the inconvenience caused.

Regards,
Jenn

Hello @itchycode,

sure, thanks! I’ll change layout on that page to standard gallery for now.

Best Regards,
Kamil

Hi guys,

We’ve fixed this issue since Bricks 1.9.6

Please let us know if you are still experiencing issues.

Missed out on this thread update.

Best regards,
Jenn

1 Like

I have just updated to the newest release ( 1.9.7.1) and the issue is back again
I am using an ACF flexible content field structure.

Hi Albert,
Would you be so kind as to send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase?

Hi. Did you get your problem solved? I’m having the same issue.

The “solved” in the title refers to the original report from Dec ’23 @Maru.

We have already received several reports on the current problem by e-mail and are working on a solution. I will add this report to the task and change the title. I will happily change it again and let you know when the problem has been solved :slight_smile:

Perfect. In that case, I will revert the gallery to normal until you update the theme. Thank you.

Reporting that I have faced the same issue especially on mobile devices.
A refresh in browser usually fixes it but not always.

Version: 1.9.7.1

No caching
Tested in Desktop Browser (inspect to Mobile resolution)
and in Mobile
On Local and on Production site.

Hi guys,

We’ve fixed this issue (again) in Bricks 1.9.8 beta, now available as a manual download in your account (see changelog).

Please let us know if you are still experiencing issues.

As with any beta release, please do not use it on a production or live website. It is only meant for testing in a local or staging environment.

I am still having issues with overlapping images in 1.9.8. Are there any other settings or adjustments I need to make to get this to display properly?

Hi Ryan,
Welcome to the forum!

You should clear the cache (browser + plugin) if you are using caching. If it still does not work, please send temporary login credentials, information on where we can see the issue, and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase.

Thank you, email sent!

Hi. It seems like that the update didn’t solve anything for me either as long as Safari on Mac goes. It seems like the issue is no more present on other browsers including Chrome and Opera. Haven’t tested it on IE as I’m on a Mac.

Hi Maru,
We are currently investigating the problem and will let you know as soon as we have any news.

2 Likes

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

Changelog: Bricks 1.9.8 Changelog – Bricks

Please let us know if you are still experiencing issues.

Best regards,
timmse

Hi.

Unfortunately, it seems like the issue has not been solved on my website. Weirdly, I only see the problem on Safari on Mac and not on Opera or Chrome.

Hello

I was experiencing the same masonry style problem as you, fortunately it is working on Chrome and Safari, desktop and mobile with 1.9.8 installed, caches cleared.

There does seem to be a very slight lazy load going on with some of the images but it is so short it doesn’t have a negative effect.

I also cleared my cache of course. Here is the affected page. The rendering issue is resolved if I resize the window so basically it bugs at the initial display rendering