Category image deletes after initial upload and category save

[vivekkumar945744]

Preconditions and environment

• Magento Version 2.4.5
• PHP version 8.2

Steps to reproduce

• Installed with composer: composer create-project --repository=https://repo.magento.com/ magento/project-community-edition
• Installed and logged into the admin
• Click on Stores > Configuration > General > Web
• Change 'Base URL for User Media Files' And 'Secure Base URL for User Media Files'
• Click on catalog > categories
• Upload category image
• Save category
• Save category again

Expected result

• After the initial category image upload and save, if you save the category again without changing the image. The category should retain the original category image.

Actual result

• Instead, after my initial category image upload and save. The image disappears if I save the category.

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.
• [X] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

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

[vivekkumar945744]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @vivekkumar945744, here is your Magento Instance: https://9c30287a025d01de2ec34b4b3349dc23.instances.magento-community.engineering Admin access: https://9c30287a025d01de2ec34b4b3349dc23.instances.magento-community.engineering/admin_8268 Login: 8a35141c Password: 443462fcf93b

[m2-assistant[bot]]

Hi @ajijshekh123. 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!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[ajijshekh123]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @ajijshekh123, here is your Magento Instance: https://9c30287a025d01de2ec34b4b3349dc23.instances.magento-community.engineering Admin access: https://9c30287a025d01de2ec34b4b3349dc23.instances.magento-community.engineering/admin_8ae1 Login: d3f099a8 Password: 28e8742ae858

[vivekkumar945744]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @vivekkumar945744, here is your Magento Instance: https://9c30287a025d01de2ec34b4b3349dc23.instances.magento-community.engineering Admin access: https://9c30287a025d01de2ec34b4b3349dc23.instances.magento-community.engineering/admin_0572 Login: f102e56b Password: 33b799cd474f

[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, here is your Magento Instance: https://9c30287a025d01de2ec34b4b3349dc23.instances.magento-community.engineering Admin access: https://9c30287a025d01de2ec34b4b3349dc23.instances.magento-community.engineering/admin_8fe3 Login: e4e3759a Password: f81cce3b046d

[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).
• [ ] 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!
• [ ] 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]

Verified the issue on Magento 2.4-develop instance and the issue is reproducible. Hence confirming the issue.

[github-jira-sync-bot]

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

[m2-assistant[bot]]

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

[vivekkumar945744]

@magento I am working on this

[Kannakiraj123]

@magento I am working on this

[Kannakiraj123]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @Kannakiraj123, here is your Magento Instance: https://9c30287a025d01de2ec34b4b3349dc23.instances-prod.magento-community.engineering Admin access: https://9c30287a025d01de2ec34b4b3349dc23.instances-prod.magento-community.engineering/admin_dfd0 Login: 132b916b Password: ed1834dddbc1

[Kannakiraj123]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @Kannakiraj123, here is your Magento Instance: https://9c30287a025d01de2ec34b4b3349dc23.instances-prod.magento-community.engineering Admin access: https://9c30287a025d01de2ec34b4b3349dc23.instances-prod.magento-community.engineering/admin_3735 Login: 51722f16 Password: 67345a4189f6

[Kannakiraj123]

@magento I am working on this

[Kannakiraj123]

@magento I am working on this

[Kannakiraj123]

@vivekkumar945744

Change 'Base URL for User Media Files' And 'Secure Base URL for User Media Files' ->Can you please give which url did you passed in this step

if I set as "base_url" of site.The images will be broken. if I set as "base_url/media/",I cannot reproduce this issue.

[sezio]

Hi

Is there any update on this ? I also have the problem. Did you, by any chance, found any solution ?

I can confirm that as Base URL for User Media Files and Secure Base URL for User Media Files, the path are configured as {{unsecure_base_url}}/media/ and {{secure_base_url}}/media/

Thank you