[!!!][TASK] Remove legacy BE entry point handling #1147 (#5036)

Resolves: TYPO3-Documentation/Changelog-To-Doc#1147
Releases: main

Author: linawolf

Documentation/ApiOverview/Autoloading/Index.rst

@@ -95,7 +95,7 @@ Loading classes without Composer mode
 
 This means, you did not install TYPO3 via a `require` statement inside your
 :file:`composer.json`. It's a regular old-school install where the TYPO3 source
-and the symlinks (:file:`typo3/index.php`) are setup manually.
+and the symlinks (:file:`index.php`) are setup manually.
 
 In this case, every time you install an extension, the autoloader scans the
 whole extension directory for classes. No matter if they follow any convention

Documentation/ApiOverview/DirectoryStructure/Index.rst

@@ -219,13 +219,12 @@ another folder name than :file:`fileadmin/` can be in use.
 :file:`public/typo3/`
 ~~~~~~~~~~~~~~~~~~~~~
 
-This directory contains the two PHP files for accessing the TYPO3
-backend (:file:`typo3/index.php`) and install tool (:file:`typo3/install.php`).
+If :composer:`typo3/cms-install` is installed, this directory contains the PHP
+file for accessing the install tool (:file:`public/typo3/install.php`).
 
-..  versionchanged:: 12.0
-    Starting with TYPO3 v12 (or v11 using `typo3/cms-composer-installers` v4)
-    the system extensions are not located in this directory anymore. They can now
-    be found in the :ref:`directory-vendor` folder.
+..  versionchanged:: 14.0
+    The TYPO3 backend entry point PHP file :file:`public/typo3/index.php` has
+    been removed. The backend can be accessed via the :ref:`backend-entry-point`.
 
 .. _directory-public-typo3temp:
 

Documentation/ApiOverview/DirectoryStructure/LegacyInstallations.rst

@@ -54,8 +54,12 @@ structure.
 :file:`typo3/`
 --------------
 
-Among others, this directory contains the two PHP files for accessing the TYPO3
-backend (:file:`typo3/index.php`) and install tool (:file:`typo3/install.php`).
+Among others, this directory contains the PHP
+file for accessing the install tool (:file:`public/typo3/install.php`).
+
+..  versionchanged:: 14.0
+    The TYPO3 backend entry point PHP file :file:`typo3/index.php` has
+    been removed. The backend can be accessed via the :ref:`backend-entry-point`.
 
 
 .. _legacy-directory-typo3-sysext:

Documentation/ApiOverview/RequestLifeCycle/Bootstrapping.rst

@@ -124,7 +124,7 @@ to have an overview of these base values, it is worth taking a look into the fol
 
 -  :php:`SystemEnvironmentBuilder::calculateScriptPath()` calculates the script
    path. This is the absolute path to the entry script. This can be something
-   like '.../public/index.php' or '.../public/typo3/index.php' for web calls,
+   like '.../public/index.php' for web calls,
    or '.../bin/typo3' or similar for CLI calls.
 
 -  :php:`SystemEnvironmentBuilder::initializeGlobalVariables()` sets

Documentation/CodingGuidelines/CodingBestPractices/NamedArguments.rst

@@ -240,7 +240,7 @@ developers often overlook argument positions and names:
             [
                 'RewriteCond %{REQUEST_FILENAME} !-d',
                 'RewriteCond %{REQUEST_FILENAME} !-l',
-                'RewriteRule ^typo3/(.*)$ %{ENV:CWD}typo3/index.php [QSA,L]',
+                'RewriteRule ^typo3/(.*)$ %{ENV:CWD}index.php [QSA,L]',
             ]
         ))),
         replacement: 'RewriteRule ^typo3/(.*)$ %{ENV:CWD}index.php [QSA,L]',

Documentation/Configuration/BackendEntryPoint/Index.rst

@@ -12,12 +12,14 @@ Backend entry point
 
 ..  versionadded:: 13.0
     Before TYPO3 v13 the backend entry point path for accessing the backend has
-    always been :samp:`/typo3`. Since TYPO3 v13 the backend entry point can be
+    always been :path:`/typo3`. Since TYPO3 v13 the backend entry point can be
     adjusted to something else. See :ref:`backend-entry-point-configuration`
     and :ref:`backend-entry-point-migration`.
 
-    The legacy entry point :samp:`/typo3/index.php` is no longer needed and
-    therefore deprecated. See :ref:`backend-entry-point-legacy-free`.
+..  versionchanged:: 14.0
+
+    The legacy entry point :file:`/typo3/index.php` is no longer needed and
+    has been removed.
 
 The TYPO3 backend URL is configurable in order to enable optional protection
 against application administrator interface infrastructure enumeration
@@ -88,33 +90,6 @@ Note that the :php:`$GLOBALS['TYPO3_CONF_VARS']['SYS']['cookieDomain']` is
 necessary, so that backend users can preview website pages or use the admin
 panel.
 
-..  _backend-entry-point-legacy-free:
-
-Legacy-free installation
-------------------------
-
-The legacy entry point `/typo3/index.php` is no longer needed and deprecated in
-favor of handling all backend and frontend requests with :samp:`/index.php`. The
-entry point is still in place in case webserver configuration has not been
-adapted yet and the maintenance and emergency tool is still available via
-:samp:`/typo3/install.php` in order to work in edge cases like broken web server
-routing.
-
-In Composer mode, an additional configuration option for the deactivation of
-the legacy entry point is provided, which can be defined in the project's
-:file:`composer.json`.
-
-..  code-block:: json
-    :caption: /path/to/project/composer.json (Excerpt)
-
-    {
-        "extra": {
-            "typo3/cms": {
-                "install-deprecated-typo3-index-php": false
-            }
-        }
-    }
-
 ..  _backend-entry-point-migration:
 
 Migration
@@ -136,7 +111,7 @@ Apache configuration
 
 It is most important to rewrite all `typo3/*` requests to `/index.php`, but also
 `RewriteCond %{REQUEST_FILENAME} !-d` should be removed in order for a request
-to `/typo3/` to be directly served via `/index.php` instead of the deprecated
+to `/typo3/` to be directly served via `/index.php` instead of the removed
 entry point `/typo3/index.php`.
 
 Apache configuration before: