Issue Bug Needs Feedback Quiet

#108272Changing the case of folder names does not work

Dennis Purisevic 11/23/25, 10:53 updated 10/24/26, 07:13

Description

Steps to reproduce

Open the backend module Filelist.
Rename a folder from “name” to “NAME”.

Current behaviour

Before rename: “name“
After rename: “name” (case change not applied)

Expected behaviour

Before rename: “name“
After rename: “NAME” (case change applied)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] Changing the case of folder names does not work Resolves: #108272 Releases: main

History 7

  1. Garvin Hicking commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2025-11-23T11:10:11+00:00" > 11/23/25, 11:10 </span>

    What’s your server’s OS and which filesystem type is used?

  2. Dennis Purisevic commented <span data-processor="relativetime" data-value="2025-11-23T11:22:59+00:00" > 11/23/25, 11:22 </span>

    Local:
    • DDEV Unix PHP 8.2.28 v14 Local filesystem (Doesn’t work)
    • DDEV Unix PHP 8.3.23 v13 Local filesystem (Works)
    Server 1:
    • Unix PHP 8.3.23 v13 Local filesystem (Doesn’t work)
    Server 2:
    • Unix PHP 8.3.27 v12 Local filesystem (Works)
    • Unix PHP 8.3.27 v13 Local filesystem (Works)
    Server 3:
    • Unix PHP 8.2.28 v13 Local filesystem (Works)

    So sometimes it works, sometimes it doesn’t. Besides, I think that a test in the core can’t hurt.

  3. Garvin Hicking commented <span data-processor="relativetime" data-value="2025-11-23T11:25:45+00:00" > 11/23/25, 11:25 </span>

    I would specifically need to know if you’re using a case sensitive filesystem or not.

    Tests for thos are hard because many use macOS with case insensitive, so there “is no casing”. We couldnt test for it, and some CI runners would also be case insensitive…

  4. Dennis Purisevic commented <span data-processor="relativetime" data-value="2025-11-23T11:32:28+00:00" > 11/23/25, 11:32 </span>

    If tested this with “touch lower” and “ls LOWER” (thanks ChatGPT) and all are case-sensitive.

    Ah, okay, good to know. Interestingly, recasing files work perfectly on all installations.

  5. Garvin Hicking commented <span data-processor="relativetime" data-value="2025-11-23T11:48:18+00:00" > 11/23/25, 11:48 </span>

    Thanks – needs some investigation.

    Probably you can workaround it by naming the folder “nameNew” and then “Name”. So ensure that the name is different than just by its case, then upper/lowercase should be respected.

  6. Dennis Purisevic commented <span data-processor="relativetime" data-value="2025-11-23T11:53:55+00:00" > 11/23/25, 11:53 </span>

    I had the idea for an implementation to check first if the current name and new name has just changed in case and if so, first rename it into name_[uuid] and then from the name_[uuid] into NAME.

  7. Benni Mack commented <span data-processor="relativetime" data-value="2026-10-24T07:13:32+00:00" > 10/24/26, 07:13 </span>

    Reproduced on main: a rename that only changes case fails silently on case-insensitive filesystems mounted into Linux (Docker Desktop/DDEV on macOS, likely SMB/NFS). The driver’s rename() call doesn’t rename anything, but TYPO3 still treats it as successful and updates sys_file identifiers to the new casing. Renaming via a temporary name works.

    Maybe flysystem could help with that