Wrong gallery main image and active preview after updating for configurable products.

[sergiy-v]

Wrong gallery main image and active preview after gallery data updating for configurable products.

Preconditions

1. Magento 2.4

Steps to reproduce

1. Create a configurable product (the color attribute uses for example) with associated products:

• product with 'Black' color
• product with 'White' color

2. Add image and video for each products like on the screenshot below.

Expected result

1. Expected result for case when the color attribute has 'Dropdown' type.

2. Expected result for case when the color attribute has 'Visual Swatch' type.

Actual result

1. Actual result for case when the color attribute has 'Dropdown' type. Wrong main image and active preview for 'Black' option.

2. Actual result for case when the color attribute has 'Visual Swatch' type. Wrong main image and active preview for 'White' option. Swatch logic always use first image after gallery updating.

[m2-assistant]

Hi @sergiy-v. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@sergiy-v do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @Leandry. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[Leandry]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @Leandry. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @Leandry, here is your Magento instance.
Admin access: https://i-26856-2-4-develop.instances.magento-community.engineering/admin_989a
Login: 75a38337 Password: b6581c639d16
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

@Leandry Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

✅ Confirmed by @Leandry
Thank you for verifying the issue. Based on the provided information internal tickets MC-31478 were created

Issue Available: @Leandry, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant]

Hi @sergiy-v. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-engcom-team]

Hi @sergiy-v. Thank you for your report.
The issue has been fixed in #26560 by @sergiy-v in 2.4-develop branch
Related commit(s):

• 54f93e22ae3d9387d5a8c259d6933efbcd5461e8

The fix will be available with the upcoming 2.4.0 release.