Category A image replaced by uploading to Category B

[stephan-cream]

Preconditions (*)

1. Magento version: 2.3.*
2. PHP version: Any
3. SQL version: Any

Steps to reproduce (*)

1. Add an image with the name 'test.jpg' to Category A
2. Check the image (should be uploaded properly).
3. Add a different image with the same name 'test.jpg' to Category B.
4. Check the image (should be uploaded properly).
5. Go back to check the image of Category A (image replaced by image uploaded to Category B).

Expected result (*)

1. The image for Category A is what is uploaded for Category A.
2. The image for Category B is what is uploaded for Category B.

Actual result (*)

1. The image for Category A is what is uploaded for Category B (basically it's replaced).
2. The image for Category B is what is uploaded for Category B.

This is caused because there is no category identifier differentiation.
Everything is saved directly under /media/catalog/category/.
In this example, when checking the URL of the image on both categories it was:
/media/catalog/category/test.jpg

[m2-assistant]

Hi @stephan-cream. 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.3-develop instance - upcoming 2.3.x release

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

@stephan-cream 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 @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).

  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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

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

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

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-17764, MC-17765 were created

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.

[sanjay-github]

@engcom-Bravo : I am working on this issue.