Hi @bhushan-cs. 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.

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.

Hi @bhushan-cs,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is not reproducible.Kindly refer the attached video.

The "logo.png" file was exclusively visible within the "Testing" directory.

Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

@engcom-Bravo: have you tested this on a Linux operating system, or on macOS or Windows? Because the latter 2 use a filesystem that by default is case insensitive and Linux normally uses filesystems that are case sensitive. That might explain why you can't reproduce it. So please make sure you test this on a system with a case sensitive filesystem.

Hi @engcom-Bravo,

The steps are same as I provided in the report. I didn't get the "could not create directories" error on my instance when creating the directory without case.
I recheck the issue in Latest 2.4-develop instance, it is reproducible. Please refer to the attached video.

My instance details:
OS name: Ubuntu 20.04.6 LTS
Server version: Apache/2.4.41 (Ubuntu)
Server built: 2024-07-17T18:58:09
PHP 8.2.25

The issue is also present in a couple of our live instances, so I think this is not an isolated occurrence. If required, I can provide the server service versions as well.

Please let me know if I can provide any other information for the issue verification process.

Thanks.

Hi @bhushan-cs ,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is not reproducible. Kindly refer the attached screenshot.

Steps to reproduce

1. Navigate to Content > Media Gallery
2. Create a folder under wysiwyg "Testing"
3. Upload an image in the newly created folder.
4. Select wysiwyg folder and try to create another folder named "testing"
5. Observe error displays
   

Thanks.

Hi @engcom-Delta,

Thanks for trying to recreate the issue.

Can you please confirm which OS you are using in your test instance? It's plausible, as @hostep also mentioned, that the OS might be playing a part in this issue.

I have confirmed that my issue is reproducible on my local Ubuntu and live Debian system, and since both are listed as a supported OS in Magento 2 system requirements, can you please try recreating the issue on the same if you haven't yet?

Thanks.

I agree with @bhushan-cs

@engcom-Delta: your video shows you are using macOS, which by default uses a case-insensitive filesystem.
You should try to reproduce this issue on a filesystem that is case-sensitive.
So either reformat your partition/volume as APFS (Case-sensitive) (which as a Magento developer on macOS you should definitively do in my opinion, I've been doing this for 12 years like that), or switch to Linux.

Hi @bhushan-cs @hostep ,

Thanks for your reporting and collaboration.
We have verified the issue in Latest 2.4-develop instance and the issue is reproducible. Kindly refer the screenshots.
Earlier tests were run in Mac and Windows OS.

Steps to reproduce

1. OS - Ubuntu
2. Navigate to Content > Media Gallery
3. Create a folder under wysiwyg "Testing"
4. Upload an image in the newly created folder.
5. Select wysiwyg folder and try to create another folder named "testing"
6. Observe error displays
   

Thanks.

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

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

❌ You don't have permission to export this issue.

@magento I am working on this

Hi @bhushan-cs! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

@magento add to contributors team

Hi @bhushan-cs! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

@magento I am working on this