[Magento 2.3.5 p2] Upload fails in image uploader

[raghav111jain]

Preconditions (*)

1.magento 2.3.5 p2
2.php 7.3

Steps to reproduce (*)

Expected result (*)

1. [Screenshots, logs or description]

Actual result (*)

1. [Screenshots, logs or description]

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

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

show this error please help ASAP

"Fatal error: Uncaught Error: Call to undefined function mime_content_type() in /home/designoneonline/public_html/shop/vendor/magento/module-cms/Model/Wysiwyg/Images/Storage.php:365 Stack trace: #0 /home/designoneonline/public_html/shop/generated/code/Magento/Cms/Model/Wysiwyg/Images/Storage/Interceptor.php(37): Magento\Cms\Model\Wysiwyg\Images\Storage->getFilesCollection('/home/designone...', NULL) #1 /home/designoneonline/public_html/shop/vendor/magento/module-cms/Block/Adminhtml/Wysiwyg/Images/Content/Files.php(60): Magento\Cms\Model\Wysiwyg\Images\Storage\Interceptor->getFilesCollection('/home/designone...', NULL) #2 /home/designoneonline/public_html/shop/vendor/magento/module-cms/Block/Adminhtml/Wysiwyg/Images/Content/Files.php(74): Magento\Cms\Block\Adminhtml\Wysiwyg\Images\Content\Files->getFiles() #3 /home/designoneonline/public_html/shop/vendor/magento/module-cms/view/adminhtml/templates/browser/content/files.phtml(13): Magento\Cms\Block\Adminhtml\Wysiwyg\Images\Content\Files->getFilesCount() #4 /home/designoneonl in /home/designoneonline/public_html/shop/vendor/magento/module-cms/Model/Wysiwyg/Images/Storage.php on line 365"

[m2-assistant]

Hi @raghav111jain. 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.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

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

[m2-assistant]

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: 👇

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

[ajijshekh123]

Hello @raghav111jain,
Please add proper Steps to be reproduced, Actual result and Expected result.
Thanks.

[ihor-sviziev]

@raghav111jain
please check if you have installed fileinfo extension, usually it goes bundled with php

[raghav111jain]

@raghav111jain
please check if you have installed fileinfo extension, usually it goes bundled with php
Thanks @ihor-sviziev its working man (fileinfo extension not installed)

[ihor-sviziev]

I'd like to reopen this task and add ext-fileinfo to the composer.json.
Could you provide more info how we can get the same php configuration as you had?

[ihor-sviziev]

This issue duplicates #24332.

@raghav111jain FYI we have a pull request that solves this issue: #29671, so after accepting this PR it will work even w/o fileinfo php extension.

As for now we have a workaround to install fileinfo extension.

[magento-engcom-team]

Hi @raghav111jain. Thank you for your report.
The issue has been fixed in #29671 by @konarshankar07 in 2.4-develop branch
Related commit(s):

• 8344b1193b33ec89457b3717362dd923f4a7c97d
• 8da5e70859784f0cf097fae1bcbaa240db55fb85
• d312ab5f63f22329c3dde98cbcebb2347c8f077c
• f7503ea597d79ed29b544daf169c7ced14ba42f9
• c09a26144f24548271e908efb4232baec079b92a
• 12098680bbfa555b8aad268bf8156ada710d507b
• 60c01638fe0f00d92184308eba1599cd58a74f6f
• 21f1eb357ce85f236f9af06ba3e429643ad28e3c
• 0cf0e09cf5453c7fb4f8502722b1a0447c00b9db
• 09bd902440a57c2253f8f44abbbe1da8e98901fc

The fix will be available with the upcoming 2.4.2 release.