[FEATURE] Rename top-level module "file" to "media" (#6133)

References: TYPO3-Documentation/Changelog-To-Doc#1378
Releases: main

Author: linawolf

Documentation/Administration/UserManagement/Groups/GroupPermissions.rst

@@ -196,7 +196,7 @@ File mounts are similar to DB mounts but instead are used to manage access to
 files.
 
 File mounts need to be created first, for example using the context menu on the
-file tree in module "Filelist", or in the
+file tree in module :guilabel:`Media > Filelist`, or in the
 `File mounts submodule of the Backend Users module <https://docs.typo3.org/permalink/t3coreapi:user-management-backend-users-file-mounts>`_
 
 They can then be selected when editing a backend user group:

Documentation/ApiOverview/Backend/AccessControl/MoreAboutFileMounts/Index.rst

@@ -46,7 +46,7 @@ File mounts
 Create a new file mount
 =======================
 
-To create a new file mount go to the module :guilabel:`File > Filelist` and create the
+To create a new file mount go to the module :guilabel:`Media > Filelist` and create the
 folder for the mount if it didn't exist yet. Then open the context menu on that
 folder and choose :guilabel:`New File mount`, then give the new file mount a name.
 The entry point is already set.
@@ -159,7 +159,7 @@ and:
 we have to create a directory :file:`/path/to/web/root/fileadmin/groups/1/`.
 
 Having set up all these properties and folders, the user
-should see the following when moving to the **FILE > Filelist**
+should see the following when moving to the :guilabel:`Media > Filelist`
 module:
 
 .. figure:: /Images/ManualScreenshots/AccessControl/AccessUserFileTree.png

Documentation/ApiOverview/Backend/BackendModules/ModuleConfiguration/Index.rst

@@ -145,7 +145,7 @@ Module configuration options
             The page tree as used in the :guilabel:`Content` module.
 
         :js:`@typo3/backend/tree/file-storage-tree-container`
-            The file tree as used in the :guilabel:`Filelist` module.
+            The file tree as used in the :guilabel:`Media` module.
 
         ..  rubric:: Migration
 

Documentation/ApiOverview/Backend/ButtonComponents.rst

@@ -64,10 +64,10 @@ icon representation to the icon of the the first active radio icon in the
 dropdown list.
 
 ..  figure:: /Images/ManualScreenshots/Backend/FileModuleDropDownButton.png
-    :alt: DropDown button component in the File > Filelist module
+    :alt: DropDown button component in the :guilabel:`Media > Filelist` module
     :class: with-border with-shadow
 
-    DropDown button component in the :guilabel:`File > Filelist` module
+    DropDown button component in the :guilabel:`Media > Filelist` module
 
 
 ..  _dropdown-button-components-button:

Documentation/ApiOverview/CodeEditor/Index.rst

@@ -18,7 +18,7 @@ Code editor
 The code editor provides a backend editor with syntax highlighting. The editor
 is used by TYPO3 itself for :ref:`TCA fields with type "text" and renderType
 "codeEditor" <t3tca:columns-text-renderType-codeEditor>` and in the module
-:guilabel:`File > Filelist`. Under the hood, `CodeMirror`_ is used.
+:guilabel:`Media > Filelist`. Under the hood, `CodeMirror`_ is used.
 
 ..  contents::
     :local:
@@ -188,7 +188,7 @@ The following configuration options are available:
     :type: array
 
     Binds the mode to specific file extensions. This is important for using
-    the code editor in the module :guilabel:`File > Filelist`.
+    the code editor in the module :guilabel:`Media > Filelist`.
 
 ..  confval:: default
     :name: code-editor-register-mode-default

Documentation/ApiOverview/DataHandler/Introduction/Index.rst

@@ -47,7 +47,7 @@ Files
 =====
 
 DataHandler can also handle files. The file operations are normally
-performed in the :guilabel:`File > Filelist` module where you can manage a
+performed in the :guilabel:`Media > Filelist` module where you can manage a
 directory on the server by copying, moving, deleting and editing files
 and directories. The file operations are managed by two Core classes,
 :php:`\TYPO3\CMS\Core\Utility\File\BasicFileUtility` and

Documentation/ApiOverview/Events/Events/Filelist/ModifyEditFileFormDataEvent.rst

@@ -8,7 +8,7 @@ ModifyEditFileFormDataEvent
 
 The PSR-14 event :php:`\TYPO3\CMS\Filelist\Event\ModifyEditFileFormDataEvent`
 allows to modify the form data, used to render the file edit form in the
-:guilabel:`File > Filelist` module using
+:guilabel:`Media > Filelist` module using
 :ref:`FormEngine data compiling <FormEngine-DataCompiling>`.
 
 

Documentation/ApiOverview/Events/Events/Filelist/ProcessFileListActionsEvent.rst

@@ -8,10 +8,10 @@ ProcessFileListActionsEvent
 
 The PSR-14 event :php:`\TYPO3\CMS\Core\Configuration\Event\ProcessFileListActionsEvent`
 is fired after generating the actions for the files and folders listing in the
-:guilabel:`File > Filelist` module.
+:guilabel:`Media > Filelist` module.
 
 This event can be used to manipulate the icons/actions, used for the edit control
-section in the files and folders listing within the :guilabel:`File > Filelist`
+section in the files and folders listing within the :guilabel:`Media > Filelist`
 module.
 
 Example

Documentation/ApiOverview/Fal/Administration/Storages.rst

@@ -14,7 +14,7 @@ deserve further explanation.
 
 Is browsable?
     If this box is not checked, the storage will not be browsable by
-    users via the :guilabel:`File > Filelist` module, nor via the link browser
+    users via the :guilabel:`Media > Filelist` module, nor via the link browser
     window.
 
 Is publicly available?

Documentation/ExtensionArchitecture/HowTo/CreateNewDistribution.rst

@@ -193,7 +193,7 @@ from the root of the page tree using the :ref:`export module <ext_impexp:export>
    previous exports were stored that you do not want included in the export.
 
    Therefore, delete any temporary files that you do not want to export from the
-   fileadmin. Use the :guilabel:`Filelist` module to delete these files.
+   fileadmin. Use the :guilabel:`Media > Filelist` module to delete these files.
    If you delete them directly from the file system, the corresponding entries in
    :sql:`sys_file` will not be deleted and an error will occur during export,
    which must then be corrected directly by manually deleting the database entries.