Unfortunately, I have the same issue. It is not resolved.
The images are overlapping at initial rendering:
When I then click on refresh and the browser loads the page data again, the gallery and all its images are properly shown in masonry.
I am using Google Chrome on Windows.
Cheers
Patric
I’m sorry if it appeared I was giving you tips, I am but a novice builder and my site is my first WP and first with Bricks.
My gallery still seems to be holding up, least on my viewing systems, macOS, iOS, Chrome & Safari.
I’m sure you are busy trying to solve your own problems but if anyone has a moment to check my gallery on your browsers you can find my first portfolio via the page with links to the others at the bottom of each page.
It would be interesting to discover if you get the same corruption. Thanks…
It seems like the masonry gets weird when it’s using a template on a CPT. My masonry gallery on index is working fine.
Mine is built on a Bricks template gallery element pulling in from an ACF Pro CPT gallery (Advanced Themer version).
I did experienced the corruption in the previous Bricks 1.9.7 theme.
Mine is also an ACF pro CPT gallery field.
Please may I know if you have any performance-related plugins that lazyload the images?
Suspect the images added with attribute loading="lazy" caused the masonry layout mess up.
Can both of you provide admin access for me to check? Please send to help@bricksbuilder.io and include this forum thread as a reference.
Regards,
Jenn
I made a temporary admin account for you and sent it by mail.
As for lazy load, from what I know, I don’t use anything specific although I do have Litespeed installed. The lazy load option has been desactivated on the plugin setting.
For comparison - I have lazy loading disabled in the Bricks settings (cannot remember if that was my response to the masonry issue or not), but lazy loading is selected on in the Siteground caching plugin but with thumbnails excluded.
I am not sure if you would term the gallery page as a collection of thumbnails prior ro lightbox selection or not?
It is also true that the Siteground Speed Optimizer might be considered be unsophisticated and/or ‘heavy-handed’ when it comes to caching…not sure if that is a help or hindrance?
Yeap. It seems like it solves partially the issue when I disable lazy loading from Bricks settings.
Hi itchy
no, I don’t have any lazyload plugins and also lazyload setting in Bricks is off.
Access is a bit tricky in this case because the gallery sits behind a password protected front.
Cheers
Patric
Hi @Patric
I can provide you with a potential fix zip file to test.
Please email us with your purchased license email 
Regards,
Jenn
Hi itchy
your new zip file works!
Masonry images show correctly.
Thanks as always
Patric
Hi Jenn
Seems the fix works. Will you be rolling this out in the next update? Despite the gallery appearing to work on my interfaces it might still be affected on others. Thanks.
David
The code still needs to be reviewed before being merged into the next release.
If you want to try the new fix, kindly email us.
Regards,
Jenn
Thanks Jenn, email sent. Is there a specific email address for the forum, I couldn’t find one? I used help@
Thanks, David
Hi itchy
after updating the cache plugin WP Meteor the problem came back.
I have now deacticated WP Meteor and the problem is gone again.
It seems to me that this plugin does something to the cache that the Masonry does not like…
Best regards
Patric
Hi @Patric
Kindly send us an email with temp admin access.
It could be conflict with their lazyload feature. You could check if the plugin provide any setting to turn off so you can use Bricks native lazyload + Bricks masonry without issue.
Regards,
Jenn
Hi Jenn
Thankfully I have not had any further problems since my last post. I’m using 1.9.8 and the suggested settings for loading.
I eventually tested the modified theme you sent and it did not break anything and the masonry gallery functions as it should.
Thanks for your help,
David
Hi guys,
We’ve fixed this issue in Bricks 1.9.9 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/live website. It is only meant for testing in a local or staging environment.
