89079[TASK] Rename "Filelist" backend module to "Media"
Commit message
Review
-
Code review CR +1
- Sarah McCarthy +1
- Mathias Bolt Lesniak +1
- Rachel Foucard +1
-
Verified V 0
- core-ci +1 CI
Issues 1
Files 34
- typo3/sysext/backend/Classes/Clipboard/Clipboard.php+1 −1
- typo3/sysext/backend/Classes/Configuration/TranslationConfigurationProvider.php+1 −1
- typo3/sysext/backend/Classes/Middleware/BackendModuleValidator.php+1 −1
- typo3/sysext/backend/Classes/Middleware/SiteResolver.php+2 −2
- typo3/sysext/backend/Classes/View/BackendViewFactory.php+2 −2
- typo3/sysext/backend/Configuration/ContentSecurityPolicies.php+1 −1
- typo3/sysext/beuser/Resources/Private/Language/locallang.xlf+1 −1
- typo3/sysext/core/Classes/Resource/Filter/FileExtensionFilter.php+1 −1
- typo3/sysext/core/Classes/Resource/Folder.php+3 −3
- typo3/sysext/core/Classes/Resource/ResourceFactory.php+1 −1
- typo3/sysext/core/Classes/Resource/ResourceStorage.php+2 −2
- typo3/sysext/core/Configuration/TCA/sys_file_reference.php+1 −1
- typo3/sysext/core/Documentation/Changelog/14.0/Important-106471-RenameTheFilelistModuleToMedia.rst9new+31 −0
- typo3/sysext/core/Resources/Private/Language/locallang_core.xlf+3 −3
- typo3/sysext/core/Tests/Acceptance/Application/FileList/FileMetaDataCest.php+1 −1
- typo3/sysext/core/Tests/Acceptance/Application/FileList/FileOperationsCest.php+1 −1
- typo3/sysext/core/Tests/Acceptance/Application/FormEngine/FalMetadataCest.php+1 −1
- typo3/sysext/core/Tests/Acceptance/Application/Topbar/NavigationComponentTreeCest.php+1 −1
- typo3/sysext/extbase/Classes/Configuration/BackendConfigurationManager.php+1 −1
- typo3/sysext/filelist/Classes/Controller/File/CreateFileController.php+1 −1
Show 14 more files
- typo3/sysext/filelist/Classes/Controller/File/EditFileController.php+1 −1
- typo3/sysext/filelist/Classes/Controller/FileListController.php2+4 −4
- typo3/sysext/filelist/Classes/Event/ModifyEditFileFormDataEvent.php+1 −1
- typo3/sysext/filelist/Classes/Event/ProcessFileListActionsEvent.php+1 −1
- typo3/sysext/filelist/Classes/FileList.php+2 −2
- typo3/sysext/filelist/Resources/Private/Language/locallang_mod_file_list.xlf+1 −1
- typo3/sysext/filelist/composer.json2+1 −1
- typo3/sysext/filelist/ext_emconf.php2+2 −2
- typo3/sysext/filelist/README.rst2+1 −1
- typo3/sysext/form/Documentation/E/FormElements/Index.rst+4 −2
- typo3/sysext/frontend/Configuration/ContentSecurityPolicies.php+1 −1
- typo3/sysext/frontend/Resources/Private/Language/locallang_ttc.xlf+1 −1
- typo3/sysext/setup/Resources/Private/Language/locallang.xlf+1 −1
- typo3/sysext/workspaces/Documentation/Administration/Versioning/Index.rst+1 −1
Review log 3744
Show 1419 earlier messages
-
Lina Wolf uploaded patch set 1 04/12/25, 06:05
-
core-ci voted on patch set 1 V +1 04/12/25, 06:11 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/77606
-
Benni Mack commented on patch set 1 04/12/25, 07:50
Hey Lina, while this has been a long standing topic for me personally as well - and I am very much in favor, I always been hesitant to do so in the past - mainly because I didn't have a full concept for all the modules (you know, we could rename the "Page" module to "Layout" or "Content" module, because everything in "Web" is a page). I also thought about removing the main module "File" here, and just move it to media. My main question is: Do you - by any chance - have more information / ideas on a bigger strategy for the UX overhaul? Is this part of the bigger fresh look + feel initiative for v14? Do you know if there is somebody making the final call / decision on naming? -
Lina Wolf commented on patch set 1 04/12/25, 07:57
Reply
I have been discussing this topic in detail with @mathias.bolt.lesniak@typo3.org who would support this change (see attached forge ticket) and is working on creating a guide on how to name things. -
Benni Mack commented on patch set 1 04/12/25, 08:17
Reply
OK. I see this is coming from the Best Practices Roadmap Objective. Got it. I thought it was part of the User Experience Improvements Objective https://typo3.org/article/roadmap-for-typo3-v14-the-high-level-objectives-and-strategic-goals "It should have a clear and intuitive interface, built for editors and marketers with varying levels of technical expertise." -
Lina Wolf commented on patch set 1 04/12/25, 08:23
Reply
I think the topic touches various teams and goals. For me from the Documentation Team point of view we have to keep explaining ppl where to find their media because the names make no real sense to them and we have to keep explaining that this is not the correct place to store assets like CSS because the name does not make much sense. I would suggest that we revive slack channel #t3docs-sig-microcopy to have a central place to discuss topics of Microcopy. -
Lina Wolf commented on patch set 1 04/12/25, 08:36
-
Mathias Bolt Lesniak commented on patch set 1 04/12/25, 13:03
I suggest changing "File>Media" to "File > Media" for legibility reasons.Reply
I also support this change. The most central argument is the alignment with other CMSs, which lowers the entry barrier (TYPO3 v14 high-level roadmap objective 3). If larger UX changes are committed for v14, this patch heralds their coming, rather than obstruct their progress. If a later UX decision reverts back from "Media" to "Filelist," I will eat my hat.Important-106471-RenameTheFilelistModuleToMedia.rst:5```suggestion ============================================================ ```Important-106471-RenameTheFilelistModuleToMedia.rst:7```suggestion ============================================================ ```README.rst:5```suggestion This TYPO3 backend module (File > Media) is used for managing media files. ```composer.json:4```suggestion "description": "TYPO3 CMS Media Module - TYPO3 backend module (File > Media) used for managing media files.", ```ext_emconf.php:5```suggestion 'description' => 'TYPO3 backend module (File > Media) used for managing files.', ``` -
Lina Wolf commented on patch set 2
V +104/12/25, 16:28Published edit on patch set 1. -
Lina Wolf commented on patch set 3 04/12/25, 16:29
Published edit on patch set 2. -
Lina Wolf commented on patch set 4 04/12/25, 16:29
Published edit on patch set 3. -
Lina Wolf commented on patch set 5 04/12/25, 16:30
Published edit on patch set 4. -
Lina Wolf commented on patch set 5 04/12/25, 16:30
Important-106471-RenameTheFilelistModuleToMedia.rst:5ReplyAcknowledgedImportant-106471-RenameTheFilelistModuleToMedia.rst:7ReplyAcknowledgedREADME.rst:5ReplyAcknowledgedcomposer.json:4ReplyAcknowledgedext_emconf.php:5ReplyAcknowledged -
core-ci voted on patch set 2 V +1 04/12/25, 16:37 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/77631
-
core-ci voted on patch set 3 V +1 04/12/25, 16:40 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/77632
-
core-ci voted on patch set 4 V +1 04/12/25, 16:41 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/77633
-
core-ci voted on patch set 5 V +1 04/12/25, 16:43 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/77634
-
Sarah McCarthy commented on patch set 5 CR +1 04/13/25, 06:11
I agree that Media is a better name. I think names in the CMS, particularly in the sidebar, that reflect more "meta" concepts would help users. -
Simon Schaufelberger commented on patch set 5 04/13/25, 10:21
FileListController.php:74I would also rename this controller and then add an alias
-
Lina Wolf commented on patch set 5 04/13/25, 10:25
FileListController.php:74ReplyIf we start like this we could rename the whole extension. However both changes would be beyond the scope of this PR. -
Simon Schaufelberger wrote 04/13/25, 15:07
Removed cc Simon Schaufelberger. -
Mathias Bolt Lesniak commented on patch set 5 04/14/25, 06:34
Reply
There seems to be general agreement here, so I suggest marking this thread as resolved. -
Lina Wolf commented on patch set 5 04/14/25, 07:11
Reply
Resolved -
Benni Mack commented on patch set 5 04/14/25, 07:17
OK. I assume now that the plan is to change the Module label only? That would mean we a) keep code with File List naming b) keep TSconfig option with mod.file_list c) keep extension name and composer name as is -
Lina Wolf commented on patch set 5 04/14/25, 07:20
Reply
I would suggest to concentrate this change on changing the module label only. In the long run of course it would be nice to have the wording uinified across the code as well however this is beyond the scope of improving backend labels. -
Garvin Hicking commented on patch set 5 04/14/25, 07:25
Missing replacements: - typo3/sysext/core/Resources/Private/Language/locallang_core.xlf:file_upload.reload.filelist + file_upload.reload.filelist.message - typo3/sysext/setup/Resources/Private/Language/locallang.xlf:showHiddenFilesAndFolders - typo3/sysext/beuser/Resources/Private/Language/locallang.xlf:filemount.link.openInFilelist - typo3/sysext/filelist/Classes/Controller/File/CreateFileController.php:L55 - typo3/sysext/filelist/Classes/FileList.php:L906 - typo3/sysext/frontend/Configuration/ContentSecurityPolicies.php:L32 - typo3/sysext/backend/Configuration/ContentSecurityPolicies.php:L41 - typo3/sysext/frontend/Resources/Private/Language/locallang_ttc.xlf:filelink_sorting - typo3/sysext/workspaces/Documentation/Administration/Versioning/Index.rst:L210 All the docs and screenshots for v14 will need some retro-fitting then too (e.g. screenshots showing the left hand navigation), but I guess that's on the radar? -
Lina Wolf commented on patch set 5 CR -1 04/14/25, 07:34
Working on it... -
Lina Wolf commented on patch set 5 CR 0 04/14/25, 07:56
Done -
Lina Wolf commented on patch set 5 04/14/25, 07:57
Reply
Done -
Lina Wolf uploaded patch set 6
CR +1V +104/14/25, 07:57 -
core-ci voted on patch set 6 V -1 04/14/25, 08:08 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/77691
-
Lina Wolf uploaded patch set 7
V -104/14/25, 08:15 -
core-ci voted on patch set 7 V +1 04/14/25, 08:21 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/77692
-
Mathias Bolt Lesniak voted on patch set 7 CR +1 04/14/25, 08:56
-
Sarah McCarthy voted on patch set 7 CR +1 04/14/25, 11:56
-
Lina Wolf commented on patch set 7 04/15/25, 03:49
We will collect all labels and terminology that needs to be changed in a central document and change approve and change them at once. Setting this on "WIP" for now. -
Lina Wolf marked it work in progress 04/15/25, 03:49
-
Rachel Foucard voted on patch set 7 CR +1 04/15/25, 06:26
-
Lina Wolf marked it ready for review 04/15/25, 14:03
-
Lina Wolf commented on patch set 7 04/15/25, 14:04
As there is wide support and the work already done and reviewed I would suggest to merge this PR. Here is the Terminology Descision: https://docs.typo3.org/m/typo3/terminology/main/en-us/Filelist.html UX and Doku team and native speakers of different languagages were involved. -
Benjamin Franzke commented on patch set 7 04/16/25, 13:03
What about the section identifier (the category) of the "Media" module? It is still named "File" which seems inappropriate given the argumentation that this module is not just about files. With this change the structure in the Modulemenu is displayed as: ``` Web Page ... File Media ``` What's your plan regarding this "File" label?Important-106471-RenameTheFilelistModuleToMedia.rst:15I do not understand this reasoning. What exactly is denglish here? Do what have any source for such a statement? I could only find argument for the opposite - it seems to be a reasonable termin in tech industry, for example https://developer.mozilla.org/en-US/docs/Web/API/FileList uses the same terminology.Important-106471-RenameTheFilelistModuleToMedia.rst:22I think other systems should not influence our naming. We should remove any occurence of external influence in our changes. If we change the term to something better - which is fine for me in general - it should be based on good arguments only (like your argumentation regarding media being not just files) and not be reasoned because other do the same. -
Lina Wolf commented on patch set 7 04/16/25, 14:18
Reply Unresolved
The section File might contain different modules provided by third party extensions. I would suggest to investigate the wording here separately.Important-106471-RenameTheFilelistModuleToMedia.rst:15Reply UnresolvedThank you for your feedback —you're right that `FileList` (camel case) is a recognized term in the context of web APIs, such as in the Mozilla documentation. However, the use of `Filelist` (as a single lowercase word) in TYPO3 seems to be a different case entirely. In standard English, `Filelist` written as one word is not a proper noun, nor is it a standard term. It appears to be a German-influenced construction—often seen in “Denglish”—where English words are combined into compound nouns following German language conventions (e.g., Downloadbereich, Fileadmin, etc.). In contrast, FileList in the Mozilla context is a formal interface name used in code, not a user-facing label or UI term. It is tightly scoped to represent a collection of files selected via an HTML <input type="file">, which is quite different from the broader functionality of TYPO3's module (uploading, organizing, and managing media assets). So while `FileList` (camel case) is valid in a programming context, `Filelist` (one word) as a UI label feels linguistically awkward in English and may be unclear to international users unfamiliar with TYPO3 conventions. A more descriptive and standard English term like Media Module might better communicate the module's purpose and improve overall UX.Important-106471-RenameTheFilelistModuleToMedia.rst:22ReplyThe UX team working together with the documentation team, @benni@typo3.org and @mathias.bolt.lesniak@typo3.org proposed a general set of rules for "good" Terminology https://docs.typo3.org/m/typo3/terminology/main/en-us/#terminology-evaluation-criteria You are invited to share your view in slask in #t3docs-sig-microcopy. Maybe we need to make some adjustments. However using Familiar terms — Commonly used in similar contexts outside TYPO3. is an important improvement to lower entry barriers. -
Mathias Bolt Lesniak commented on patch set 7 04/17/25, 09:18
Important-106471-RenameTheFilelistModuleToMedia.rst:22Reply UnresolvedFamiliar and common terminology across platforms is important in sales and marketing. It should of course not be the only criteria for a change (and it isn't in this case), but we live in a world where the perception of our product is influenced by other systems. In addition to easing migration to TYPO3, a common terminology makes it easier to compare general features in marketing and during a sales process. Incompatible terminologies can lead to lost sales and waste valuable time on translation — leaving less time to discuss the real benefits TYPO3 can offer. This is a topic in other open source CMS communities as well. -
Lina Wolf abandoned the change 06/25/25, 14:09
This needs more thorough thought and planning