WIP: WooCommerce Loop + WP Grid Builder Facets shows placeholder image instead of featured image after filtering

Browser: Chrome 110
OS: / Windows
URL: https://staging.elementojade.pe/
Video: Short screen recording that illustrates this issue (free tools: birdeatsbug.com or jam.dev)

Hi, I have a template created for Woocommerce store with a query loop created with the featured image of the product with WP Grid Builder filters and every time I activate a filter the featured image is changed by the placeholder that has woocommerce, I do not know very well why, if I update the page with the filter the image is fixed, but if I return to use the filter, pagination or something else the same thing happens again. I have looked if in the console there was a problem, but I have not found anything.

I commented this error to WP Grid Builder support, and they told me “This is a problem with Bricks that should be fixed in the next version of Bricks”, but I still wanted to comment it here in case someone else has the same error as me.

The page is:

1 Like

Hey,

This likely has to do with bricks lazy loading. I bet if you disable it, the images won’t switch to placeholders after filtering.

If you don’t like that option, the most likely solution is to run bricksLazyLoad(); after each WPGB event. I don’t have WPGB, so I can’t give you much direction but you can check out their docs and possibly reach out to them for further help.

Hi Smith,
Thanks so much for your report!

We have already received a ticket about this problem. Curtis’s approach sounds good at first but doesn’t help in this case. As I said, we already have the issue on our radar and are trying to find a solution as soon as possible.

Best regards,
timmse

3 Likes

@Smith_Benites, I’m having the same issue. Lazy load was disabled from the start, so cannot be this.

Can you confirm if this fix be in the next release, @timmse?

This has just come up for me in a new build - hopefully it’s a prompt resolution, because it’s making me look really bad right now

Also, definitely not lazy loading for me, as it’s disabled right from the start of all my builds