I have a query loop for related products inside the product template (see URL at the end) which somehow messes up the product image gallery. For some reason, it uses the image from the last loop item (related products) as the main product image.
The other products have the same problem.
If I remove the related products section, it shows the correct image.
Hmm… weird
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?
unfortunately, it’s also not working without slider. Do you have a workaround for the problem? Or do you at least know what causes the problem? Maybe I can find a workaround myself then.
Not yet, with a regular loop, it worked fine in my tests. I exported your template and imported it into my test installation: no problem at all. I’m still investigating…
Hi Tobias @0x7466 , this is an update on the investigation.
The root cause of the issue is because of multiple variable product add-to-cart forms appear on the same page.
Explanation:
In your MUC product page, MUC itself is a variable product. Coincident, the other 2 related products were variable products too. At this moment, 1 of the WooCommerce JS script “accidentally” grabs the last variable product image from the entire DOM and shows it in the product gallery.
Temporary Solution:
You could remove the Add to cart element in your product item template and the product gallery should works as usual. Alternatively, you could replace the Add to cart element with normal button + dynamic post_url to link visitor to the respective single product page.
By default, WooCommerce will do the same and auto-replace add-to-cart button with “Select Option” button in any products loop too.
We have recorded this in the bug tracker and will improve this in future updates.
However, I think you’ve introduced a new bug with the sticky header. When the header scroll hiding feature is enabled, it moves the site up when the header is hidden and down when it’s shown.
Hey Tobias,
Thanks for confirming. True… the content jumps up because of changing the position property from sticky to fixed, which is needed to fix an issue with the mobile menu set to position right
Definitely have to look at it again, thanks for the tip!
Hey Tobias,
We’ve fixed this “jumping content” in Bricks 1.6.1, now available as a one-click update within your WordPress Dashboard. Please let us know if you are still experiencing issues.