Product Images loosing inheritance scoping in multisite after storeview rest API PUT

[eraq]

Preconditions and environment

Magento 2.4.4, multisite with more than one store view. Occurs in cloud docker, as well as staging and product cloud environments.

Steps to reproduce

1. have or create a product with a product image (image, thumbnail, small_image) assigned to default scope value
2. use the storeview scoped products PUT rest api to update a single attribute such as 'name' on that sub storeview (e.g {{domain}}/rest/{{store_view_code}}/V1/products/{{sku}}).

Expected result

name attribute is updated creating a single row with store_id=1 in catalog_product_entity_varchar. No other rows with store_id != 0 are created in catalog_product_entity_varchar, and no rows are created in catalog_product_entity_media_gallery_value

Actual result

attribute row of store_id=1 for name attribute is created successfully, but several rows of store_id=1 are created for attributes 'image', 'thumbnail', and 'small_image' which then breaks inheritance of the image from default level. Also a store_id=1 row is created in catalog_product_entity_media_gallery_value.

Additional information

No response

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 @eraq. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

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

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.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant[bot]]

Hi @engcom-November. 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).

  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.

[engcom-November]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @engcom-November, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-November]

Hi @eraq , Thank you for reporting and collaboration. Verified the issue on Magento 2.4-develop branch but cannot able to reproduce the issue. Steps performed:

1. Magento multi store setup
2. Created a product without image and assigned product to both websites
3. Change scope to default store view scope and added image with options "Small" and ""Thumbnail - Save
4. Verified DB tables: catalog_product_entity_varchar and - 13 records got created catalog_product_entity_media_gallery_value - 2 records created for store id's 0 and 1
5. Send PUT request using below payload for default store view scope: http://mg24ce.local/rest/default/V1/products/simple234 { "product": { "sku": "simple234", "name": "efefefefe" } } No new row/records created in catalog_product_entity_media_gallery_value table and only one new row created with store id 1 in catalog_product_entity_varchar for product name image Kindly recheck the issue again on magento 2.4-develop branch and provide missing steps if any if the issue is still reproducible. Thank you.

[engcom-November]

Hi @eraq , We are closing this issue as there has been no latest update on the same. Kindly reopen/ create new issue if you are still facing issues. Thank you.