We have discovered a bug in connection with the theme setting “Images captions on Photo Swipe lightbox” for WooCommerce product pages. This also occurs on a test environment without other plugins (with current WoodMart version and all Patches installed). The problem does not occur with the “Twenty Twenty-Four” theme.
The captions are not displayed correctly for variant images:
Once the very first image has been opened in the lightbox and the corresponding caption has been displayed, this text remains for the first image.
If I then select a variation to which a variant image is assigned, the first image is replaced accordingly. However, the caption in the lightbox is not adjusted.
And the same applies:
If I first select a variation and then open the image in the lightbox, the matching caption for this variation image appears. And this caption remains for the first image, regardless of whether it is replaced by another variation image or, if a variation is not selected, by the regular first image of the main product.
A concrete example:
a) Configuration of product and images:
Variable parent product with the images:
image1.jpg – Caption: This is image 1
image2.jpg – Caption: This is image 2
image3.jpg – Caption: This is image 3
Variant 1:
variation1.jpg – Caption: This is variation 1
variation2.jpg – Caption: This is variation 2
b) Behaviour in the frontend – example 1:
- Open product page
- Open first image in lightbox:
image1.jpg – Caption: This is image 1
- Select variation 1 and open first image in lightbox:
variation1.jpg – Caption: This is image 1 ❌
- Select variation 2 and open first image in lightbox:
variation2.jpg – Caption: This is image 1 ❌
b) Behaviour in the frontend – example 2:
- Open product page
- Select variation 1 and open first image in lightbox:
variation1.jpg – Caption: This is variation 1
- Select variation 2 and open first image in lightbox:
variation2.jpg – Caption: This is variation 1 ❌
- Deselect variation and open first image in lightbox:
image1.jpg – Caption: This is variation 1 ❌
When will this bug be fixed?
.
