Issue with Image roles in Environment with Multiple Store Views and Unchecked "Use Default" Attribute

[carlosyrm]

Preconditions and environment

• 2.4.4-p4
• Clean environment (just magento)

Steps to reproduce

Starting with a clean Magento installation, follow these steps:

1. Create a new store view.
2. Create a new simple product and add an image to it.
3. Navigate to the frontend and verify that the product is visible in all store views.
4. In the backend, edit the product and change the store view to a particular store view.
5. Modify an attribute, such as the name, specifically for that store view. Click "Save".
6. On the frontend, navigate through all store views and verify that the attribute is different in the selected store view.
7. In the backend, edit the product and select "All Store Views". Upload a new image and click "Save".
8. Check the frontend in all store views to ensure the new image is displayed.
9. Edit the product using the "All Store Views" option and update all roles to the new image. Click "Save".
10. Delete the first image and click "Save".

Expected result

Two expected results:

1. As result of step 9, the image should take the same roles in all store views.
2. As result of step 10, the image should be deleted.

Actual result

Two actual results:

1. Result of Step 9: In the edited store view from steps 4 and 5, the image retains the initial roles and does not reflect the last roles that were set in the "All Store Views" option.
2. Result of Step 10: The backend prevents the deletion of the image because it is still being used in other roles or contexts.

Additional information

It doesn't matter if the same steps are accomplished using the API.

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @carlosyrm. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Dash. 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: :point_down:

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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!

---

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

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://91a07777b8ef54e6dfa718d0ea9927f7.instances-prod.magento-community.engineering Admin access: https://91a07777b8ef54e6dfa718d0ea9927f7.instances-prod.magento-community.engineering/admin_e6a4 Login: 2747c523 Password: 923d81e4c67f

[engcom-Dash]

Hi @carlosyrm ,

Verified the issue in 2.4-develop instance and the issue is not reproducible,Kindly recheck the behaviour in 2.4-develop instance. Kindly refer the below screenshots: 1.All the roles assigned in first image

2.All the roles assinged to new image

3.First image deleted successfully in admin as well as Store front

Steps to reproduce: as per the main description

We are getting expected result which is the new image should taken the same roles in all store views and first image deleted successfully. Kindly recheck the behaviour in 2.4-develop instance and let us know if we are missing anything!

Thanks

[carlosyrm]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @carlosyrm. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @carlosyrm, here is your Magento Instance: https://91a07777b8ef54e6dfa718d0ea9927f7.instances-prod.magento-community.engineering Admin access: https://91a07777b8ef54e6dfa718d0ea9927f7.instances-prod.magento-community.engineering/admin_9e18 Login: 6131d1e1 Password: 45ae92c12939

[carlosyrm]

Hi @engcom-Dash

Thank you for taking the time to review my report.

I have successfully reproduced the issue in a 2.4-develop instance, and I have recorded a video demonstrating all the steps in the development environment.

Before recording the video, the only action I took was creating a new store view.

In the video, you will observe that as soon as I set a different attribute for the name in the second store view, the image role begins to disregard the parameters set through the "all store view" option.

Please let me know if you need any further information or if there is anything else I can assist you with.

Screencast_07_12_2023_08:08:56_AM.webm

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://91a07777b8ef54e6dfa718d0ea9927f7.instances-prod.magento-community.engineering Admin access: https://91a07777b8ef54e6dfa718d0ea9927f7.instances-prod.magento-community.engineering/admin_d479 Login: 7430d73f Password: fb45ac428afc

[engcom-Dash]

Hi @carlosyrm , Thanks for reporting and collaboration! Verified the issue in 2.4-develop instance and the issue is reproducible,Hence we are confirming the issue. Kindly refer the below screenshot:

Thanks

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-9144 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Dash. Thank you for verifying the issue.
Issue Available: @engcom-Dash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[github-jira-sync-bot]

:x: You don't have permission to export this issue.