-
Notifications
You must be signed in to change notification settings - Fork 9.4k
[2.4.7-p3] Duplicate image when product is edited through API #39349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @iwanzijderveld. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-Delta. Thank you for working on this issue.
|
Hi @iwanzijderveld , Thanks for your reporting and collaboration. Steps to reproduce
Thanks. |
✅ Jira issue https://jira.corp.adobe.com/browse/AC-13337 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-Delta. Thank you for verifying the issue. |
Hello, Are there any news regarding this issue? It has been 5 months since this was reported. Magento 2.4.8 has been release and I didn't find anything regarding this issue. |
@magento I am working on this |
@engcom-Delta @iwanzijderveld for tests i used rest/all/async/bulk/V1/products with body
\Magento\Catalog\Model\Product::setMediaGalleryEntries ![]() first clue, in body I didn't give "id" param in "media_gallery_entries" \Magento\Catalog\Model\ProductRepository\MediaGalleryProcessor::processMediaGallery ![]() with no "value_id" entry will go to "$newEntries" array admin product edit page ![]() "catalog_product_entity_media_gallery" table ![]() let's add "id" param with another base64 image to body
check admin product edit page and "catalog_product_entity_media_gallery" table ![]() ![]() my conclusion - we should add "id" param to body if we want to change existing entity |
Preconditions and environment
bin/magento queue:consumers:start async.operations.all
Steps to reproduce
Expected result
Existing image to be overridden.
Actual result
Image is duplicated
Additional information
No response
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: