Magento creates copies of image files in products that share the same images

[cptX]

Preconditions and environment

• Magento version 2.4.7-p3

I have several products that share the same images. For example I sell several electric scooters which share the same characteristics except from the power of the motor and the battery capacity (check them here ). This makes me duplicate the product for every scooter and recreate all the configurations (colors) for every product from scratch. In the configurations I reupload the images for every color from scratch and this creates new copies of the images by adding _1 at the end of the files. This results in a huge disk space consumption and most importantly a high page load time because the system needs to upload all the copies of the images instead of only one! I consider this a major flow in the methodology of image handling in magento. Is there any way to solve this?

Note: I have searched and found some other corresponding issues but almost all of them refer to this problem during csv import which is not my case, because I create the products manually. Also, there are some attempts to use hashing to check for duplicates but probably are not impemented...

Steps to reproduce

1. Create a configurable product with 2 colors
2. Upload images in the configurations
3. Duplicate the product
4. Delete the configurations (because they reference the original configurations and are not copies)
5. Create new configurations where you should upload the same images
6. Check the file names of the images of the new configurations. They are not the same! The system created new copies of the files.

Expected result

Images uploaded should be checked some how if they already exist (eg there are some suggestions to do hashing) and if they are the same the reference to the original file (or files regarding thumbnails) should be used. This can also save processing power for recreating new thumbnails...

Actual result

Currently new uploaded images in new products are not checked if they already exist in the system and they are stored as a new copy, leading to more disk space consumption and higher page load times.

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.
• 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]

Hi @cptX. 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.

• 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.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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]

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

  - 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-Bravo]

Hi @cptX,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Magento creating copies of the same image for the product.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

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

[m2-assistant]

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