UPSTREAM FIX

magento2-39502: Media Gallery images visible in directories with different case names

Community fix magento2-39502 merged into magento/magento2 on 2025-11-20, released in 2.4.9; applies cleanly to 33 releases from 2.4.6 to 2.4.8-p5.

Fixes Media Gallery images visible in directories with different case names edited

Pull request title: Media gallery displays incorrect images from directories with identical names but different case
Pull request: magento/magento2#39502
Issues: #39382 human
Author: @bhushan-cs
Merged: 2025-11-20
Fixed in: 2.4.9
Reported on: 2.4.7
Categories: Content
Components: magento/module-media-gallery-ui

Labels

Area: Content / CMS
Component: MediaGallery
Priority: P2
Severity: —
Reported on (labels): 2.4.7

Issue

Title and steps come from the upstream issue and pull request.

Description

The "logo.png" file is incorrectly displayed within the "testing" directory as well, despite the difference in case. This behavior is unexpected and inconsistent with standard file system behavior.

Steps to reproduce

1. Create folder "Testing"
2. Upload file "logo.png" to "Testing" folder
3. Create folder "testing"
4. "logo.png" file will show in "testing" folder

Expected result

When a file is uploaded to a specific directory, it should only be accessible within that directory. In this case, the "logo.png" file should be exclusively visible within the "Testing" directory.

Actual result

The "logo.png" file is incorrectly displayed within the "testing" directory as well, despite the difference in case. This behavior is unexpected and inconsistent with standard file system behavior.

Taken from the upstream issue.

Code match per tag

Each tag was checked with git apply --check against that tag's files. A clean match means the change applies; it is not a test result. Tags that already contain the fix are marked.

Line	Code match per tag	Tests
2.4.6	2.4.6 clean 2.4.6-p1 clean 2.4.6-p2 clean 2.4.6-p3 clean 2.4.6-p4 clean 2.4.6-p5 clean 2.4.6-p6 clean 2.4.6-p7 clean 2.4.6-p8 clean 2.4.6-p9 clean 2.4.6-p10 clean 2.4.6-p11 clean 2.4.6-p12 clean 2.4.6-p13 clean 2.4.6-p14 clean 2.4.6-p15 clean	2.4.6: no test data 2.4.6-p1: no test data 2.4.6-p2: no test data 2.4.6-p3: no test data 2.4.6-p4: no test data 2.4.6-p5: no test data 2.4.6-p6: no test data 2.4.6-p7: no test data 2.4.6-p8: no test data 2.4.6-p9: no test data 2.4.6-p10: no test data 2.4.6-p11: no test data 2.4.6-p12: no test data 2.4.6-p13: no test data 2.4.6-p14: no test data 2.4.6-p15: no test data
2.4.7	2.4.7 clean 2.4.7-p1 clean 2.4.7-p2 clean 2.4.7-p3 clean 2.4.7-p4 clean 2.4.7-p5 clean 2.4.7-p6 clean 2.4.7-p7 clean 2.4.7-p8 clean 2.4.7-p9 clean 2.4.7-p10 clean	2.4.7: no test data 2.4.7-p1: no test data 2.4.7-p2: no test data 2.4.7-p3: no test data 2.4.7-p4: no test data 2.4.7-p5: no test data 2.4.7-p6: no test data 2.4.7-p7: no test data 2.4.7-p8: no test data 2.4.7-p9: no test data 2.4.7-p10: fails before, passes afterunit: fails before, passes after · integration: fails before, passes after
2.4.8	2.4.8 clean 2.4.8-p1 clean 2.4.8-p2 clean 2.4.8-p3 clean 2.4.8-p4 clean 2.4.8-p5 clean	2.4.8: no test data 2.4.8-p1: no test data 2.4.8-p2: no test data 2.4.8-p3: no test data 2.4.8-p4: no test data 2.4.8-p5: fails before, passes afterunit: fails before, passes after · integration: fails before, passes after
2.4.9	2.4.9 conflictcontains the fix	2.4.9: no test data

Triage

Model @cf/cloudflare/clef. Probability this is a bug fix: 98.1%. Probability it is security relevant: 1.0%.

Show the model's answers and probabilities

Question	Answer	Probabilities	Confidence
Change kind	bugfix	bugfix 96.4%, refactor 1.2%, tests_only 1.1%, feature 0.6%, dependency 0.4%, docs_only 0.3%	91.5%
Area	admin	admin 68.2%, other 13.6%, catalog 5.1%	41.8%
Reported version	2.4.7	2.4.7 58.1%, 2.4.7-p1 3.3%, 2.4.7-p2 1.4%	33.3%
Scope	0.86 of 2	1 49.1%, 0 32.5%, 2 18.4%	7.1%
Risk	0.26 of 2	0 77.9%, 1 17.8%, 2 4.3%	46.0%
Worth backporting	1.39 of 2	2 56.3%, 1 25.9%, 0 17.8%	12.3%

Download

For cweagans/composer-patches, choose a version below and download the bundle. Copy its magento2-39502/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Test files are always removed; paths are relative to each package root, using the default -p1 level.

Bundle README (what the ZIP ships)

# magento2-39502

Community fix merged upstream into magento/magento2, adapted by magento.watch.
This is not a patch published by Adobe.

Pull request: https://github.com/magento/magento2/pull/39502
Issue: https://github.com/magento/magento2/issues/39382
Author: @bhushan-cs
Source commit: 4737be609920d070e32ac8513928a4cbca955d72
Modifications: test files and documentation removed, paths rewritten relative to each Composer package.
Licence: OSL-3.0 / AFL-3.0, as the original Magento Open Source code.
Maintainer: Łukasz Bajsarowicz (@lbajsarowicz)

Licence: Magento Open Source code under OSL-3.0 and AFL-3.0. The bundle carries the original author, source commit and the list of modifications.