From 7702d64857a57ffbceef9913b2a44221885136d3 Mon Sep 17 00:00:00 2001
From: Anja Leichsenring <aleichsenring@ab-softlab.de>
Date: Sat, 1 May 2021 21:37:29 +0200
Subject: [PATCH] [TASK] Move Changelog files into 11.2 folder for upcoming
 release

Resolves: #94038
Releases: master
Change-Id: Iff2a240929531c69fcd4f833efb3f673b7737405
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68961
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Oliver Hader <oliver.hader@typo3.org>
Reviewed-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
---
 .../core/Documentation/Changelog-11.rst       |  1 +
 ...3331-DescriptionOfSelectCheckBoxItems.rst} |  0
 ...lidationOfExtensionsComposerjsonFiles.rst} | 14 ++---
 ...cation-92494-ExtbaseEnvironmentService.rst | 13 ++--
 ...st3lib_parsehtml_procphptransformation.rst | 37 ++++++++++++
 ...catedTypoScriptParserRelatedProperties.rst |  0
 ...n-93837-SpecialPropertyOfTCATypeSelect.rst | 56 +++++++++++++++++
 ...ginesRequestConfirmationOnFieldChange.rst} |  6 +-
 ...ileTreeAsIframeMigratedToSVG-basedTree.rst | 47 +++++++++++++++
 ...recation-93975-TBE_EDITORfieldChanged.rst} |  6 +-
 .../Feature-57082-NewTCATypeLanguage.rst      | 47 ++++++++-------
 ...leTreesInRecordSelectorsAndLinkPickers.rst | 59 ++++++++++++++++++
 ...e-89762-AddPaginationForFormManagement.rst |  8 +--
 ...88-PossibilityToDisableHreflangPerPage.rst |  6 +-
 ...AddGetFileToTYPO3CMSCoreResourceFolder.rst | 11 ++--
 ...pIdLookupInConditionsWithArrayOperator.rst | 10 ++--
 ...6-PossibilityToDisableCanonicalPerPage.rst |  8 +--
 ...51-ProvideListOfAvailableSystemLocales.rst |  7 ++-
 ...sersPreferredUILanguageStoredAsDBField.rst | 60 +++++++++++++++++++
 ...794-OverrideTCADescriptionWithTSconfig.rst |  4 +-
 ...nComponentForAllElementRecordSelectors.rst |  6 +-
 ...Feature-93908-Image-decoding-attribute.rst | 20 +++----
 ...oduleURLsReflectIntoBrowserAddressbar.rst} | 12 ++--
 ...ant-88824-AddCacheForErrorPageHandling.rst |  0
 ...gnoreSubmittedValuesInHiddenViewHelper.rst |  8 +--
 .../Documentation/Changelog/11.2/Index.rst    | 51 ++++++++++++++++
 ...st3lib_parsehtml_procphptransformation.rst | 41 -------------
 ...precatedSpecialPropertyOfTCATypeSelect.rst | 56 -----------------
 ...ileTreeAsIframeMigratedToSVG-basedTree.rst | 48 ---------------
 ...leTreesInRecordSelectorsAndLinkPickers.rst | 58 ------------------
 ...sersPreferredUILanguageStoredAsDBField.rst | 55 -----------------
 .../Php/MethodCallMatcher.php                 |  2 +-
 32 files changed, 410 insertions(+), 347 deletions(-)
 rename typo3/sysext/core/Documentation/Changelog/10.4.x/{Important--93331-DescriptionOfSelectCheckBoxItems.rst => Important-93331-DescriptionOfSelectCheckBoxItems.rst} (100%)
 rename typo3/sysext/core/Documentation/Changelog/10.4.x/{Important-93931-ValidationOfExensionsComposerjsonFiles.rst => Important-93931-ValidationOfExtensionsComposerjsonFiles.rst} (72%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Deprecation-92494-ExtbaseEnvironmentService.rst (68%)
 create mode 100644 typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-92992-HookT3libclasst3lib_parsehtml_procphptransformation.rst
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Deprecation-93726-DeprecatedTypoScriptParserRelatedProperties.rst (100%)
 create mode 100644 typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93837-SpecialPropertyOfTCATypeSelect.rst
 rename typo3/sysext/core/Documentation/Changelog/{master/Deprecation-93899-FormEnginesRequestConfirmationOnFieldChangeDeprecated.rst => 11.2/Deprecation-93899-FormEnginesRequestConfirmationOnFieldChange.rst} (95%)
 create mode 100644 typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93944-FileTreeAsIframeMigratedToSVG-basedTree.rst
 rename typo3/sysext/core/Documentation/Changelog/{master/Deprecation-93975-DeprecatedTBE_EDITORfieldChanged.rst => 11.2/Deprecation-93975-TBE_EDITORfieldChanged.rst} (86%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Feature-57082-NewTCATypeLanguage.rst (56%)
 create mode 100644 typo3/sysext/core/Documentation/Changelog/11.2/Feature-73176-FilterableTreesInRecordSelectorsAndLinkPickers.rst
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Feature-89762-AddPaginationForFormManagement.rst (62%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Feature-93188-PossibilityToDisableHreflangPerPage.rst (75%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Feature-93209-FALAddGetFileToTYPO3CMSCoreResourceFolder.rst (61%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Feature-93591-AllowGroupIdLookupInConditionsWithArrayOperator.rst (72%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Feature-93606-PossibilityToDisableCanonicalPerPage.rst (66%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Feature-93651-ProvideListOfAvailableSystemLocales.rst (60%)
 create mode 100644 typo3/sysext/core/Documentation/Changelog/11.2/Feature-93663-BackendUsersPreferredUILanguageStoredAsDBField.rst
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Feature-93794-OverrideTCADescriptionWithTSconfig.rst (88%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Feature-93857-ResizableNavigationComponentForAllElementRecordSelectors.rst (84%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Feature-93908-Image-decoding-attribute.rst (50%)
 rename typo3/sysext/core/Documentation/Changelog/{master/Feature-93988-BackendModuleURLsReflectIntoBrowserAdressbar.rst => 11.2/Feature-93988-BackendModuleURLsReflectIntoBrowserAddressbar.rst} (64%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Important-88824-AddCacheForErrorPageHandling.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 11.2}/Important-93398-PossibilityToIgnoreSubmittedValuesInHiddenViewHelper.rst (67%)
 create mode 100644 typo3/sysext/core/Documentation/Changelog/11.2/Index.rst
 delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Deprecation-92992-HookT3libclasst3lib_parsehtml_procphptransformation.rst
 delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Deprecation-93837-DeprecatedSpecialPropertyOfTCATypeSelect.rst
 delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Deprecation-93944-FileTreeAsIframeMigratedToSVG-basedTree.rst
 delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Feature-73176-FilterableTreesInRecordSelectorsAndLinkPickers.rst
 delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Feature-93663-BackendUsersPreferredUILanguageStoredAsDBField.rst

diff --git a/typo3/sysext/core/Documentation/Changelog-11.rst b/typo3/sysext/core/Documentation/Changelog-11.rst
index b920c668454e..81c512819b94 100644
--- a/typo3/sysext/core/Documentation/Changelog-11.rst
+++ b/typo3/sysext/core/Documentation/Changelog-11.rst
@@ -11,5 +11,6 @@ Every change to the TYPO3 Core which might affect your site is documented here.
 .. toctree::
    :titlesonly:
 
+   Changelog/11.2/Index
    Changelog/11.1/Index
    Changelog/11.0/Index
diff --git a/typo3/sysext/core/Documentation/Changelog/10.4.x/Important--93331-DescriptionOfSelectCheckBoxItems.rst b/typo3/sysext/core/Documentation/Changelog/10.4.x/Important-93331-DescriptionOfSelectCheckBoxItems.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/10.4.x/Important--93331-DescriptionOfSelectCheckBoxItems.rst
rename to typo3/sysext/core/Documentation/Changelog/10.4.x/Important-93331-DescriptionOfSelectCheckBoxItems.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/10.4.x/Important-93931-ValidationOfExensionsComposerjsonFiles.rst b/typo3/sysext/core/Documentation/Changelog/10.4.x/Important-93931-ValidationOfExtensionsComposerjsonFiles.rst
similarity index 72%
rename from typo3/sysext/core/Documentation/Changelog/10.4.x/Important-93931-ValidationOfExensionsComposerjsonFiles.rst
rename to typo3/sysext/core/Documentation/Changelog/10.4.x/Important-93931-ValidationOfExtensionsComposerjsonFiles.rst
index 0f8febf85214..9a0ccf7f91c6 100644
--- a/typo3/sysext/core/Documentation/Changelog/10.4.x/Important-93931-ValidationOfExensionsComposerjsonFiles.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.4.x/Important-93931-ValidationOfExtensionsComposerjsonFiles.rst
@@ -1,8 +1,8 @@
 .. include:: ../../Includes.txt
 
-================================================================
-Important: #93931 - Validation of Exensions' composer.json files
-================================================================
+=================================================================
+Important: #93931 - Validation of Extensions' composer.json files
+=================================================================
 
 See :issue:`93931`
 
@@ -10,15 +10,15 @@ Description
 ===========
 
 Future TYPO3 versions will require extensions to have a valid
-`composer.json` file as a replacement for `ext_emconf.php`.
+:file:`composer.json` file as a replacement for :file:`ext_emconf.php`.
 This description file is used to define dependencies and the
 loading order of extensions within TYPO3.
 
 In order to support site administrators by creating valid
-composer.json files for their extensions, the Extension manager
+:file:`composer.json` files for their extensions, the Extension manager
 now lists all affected extensions with details about the necessary
 adaptations. Site administrators can also use the new proposal
-functionality, which suggests a possible and valid composer.json
+functionality, which suggests a possible and valid :file:`composer.json`
 file for those extensions by accessing TYPO3.org (TER). TYPO3.org
 is used to resolve dependencies to extensions, available in the TER.
 
@@ -26,7 +26,7 @@ You can also check your current installation for such extensions
 in the reports module.
 
 Further information on the transition phase and examples
-of valid composer.json files for TYPO3 Extensions can be found on
+of valid :file:`composer.json` files for TYPO3 Extensions can be found on
 https://extensions.typo3.org/help/composer-support
 
 .. index:: Backend, ext:extensionmanager
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-92494-ExtbaseEnvironmentService.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-92494-ExtbaseEnvironmentService.rst
similarity index 68%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-92494-ExtbaseEnvironmentService.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-92494-ExtbaseEnvironmentService.rst
index c2650de5d7e3..938778c90d60 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-92494-ExtbaseEnvironmentService.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-92494-ExtbaseEnvironmentService.rst
@@ -10,24 +10,23 @@ Description
 ===========
 
 The extbase class :php:`TYPO3\CMS\Extbase\Service\EnvironmentService` is an API
-for TYPO3's legacy constant :php:`TYPO3_MODE`. That constant has been
+for TYPO3's legacy constant :php:`TYPO3_MODE`. That constant has been marked as
 deprecated in v11 and superseded by core API class
-:php:`TYPO3\CMS\Core\Http\ApplicationType` which relies on a PSR-7 request
-to determine frontend or backend mode. The EnvironmentService has now been
-deprecated as a logical follow-up to these works.
+:php:`TYPO3\CMS\Core\Http\ApplicationType`, which relies on a PSR-7 request
+to determine frontend or backend mode. The :php:`EnvironmentService` has now
+been marked as deprecated as a logical follow-up to these works.
 
 
 Impact
 ======
 
-Using the class will raise a PHP deprecation log level entry and the class will
-be removed in v12. The class has been marked :php:`@internal` a while ago already.
+Using the class will trigger a PHP :php:`E_USER_DEPRECATED` error.
 
 
 Affected Installations
 ======================
 
-Even though EnvironmentService is :php:`@internal`, some extensions
+Even though :php:`TYPO3\CMS\Extbase\Service\EnvironmentService` is :php:`@internal`, some extensions
 may still rely on it. The extension scanner will find usages.
 
 
diff --git a/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-92992-HookT3libclasst3lib_parsehtml_procphptransformation.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-92992-HookT3libclasst3lib_parsehtml_procphptransformation.rst
new file mode 100644
index 000000000000..81b0960737d2
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-92992-HookT3libclasst3lib_parsehtml_procphptransformation.rst
@@ -0,0 +1,37 @@
+.. include:: ../../Includes.txt
+
+==================================================================
+Deprecation: #92992 - Hook t3lib_parsehtml_proc.php:transformation
+==================================================================
+
+See :issue:`92992`
+
+Description
+===========
+
+Since the deprecation of several internal functions in the
+:php:`TYPO3\CMS\Core\Html\RteHtmlParser` in TYPO3 10.2 (`Changelog entry #86440
+<https://docs.typo3.org/c/typo3/cms-core/10.2/en-us/Changelog/9.5/Deprecation-86440-InternalMethodsAndPropertiesWithinRteHtmlParser.html>`_)
+the hook :php:`t3lib/class.t3lib_parsehtml_proc.php:transformation` became quite useless.
+
+It is therefore marked as deprecated and will be removed with TYPO3 v12.
+
+Impact
+======
+
+Calling the hook will trigger a PHP :php:`E_USER_DEPRECATED` error.
+
+
+Affected Installations
+======================
+
+All installations with extensions installed that implement the hook.
+
+
+Migration
+=========
+
+Migrate to use the public API only and use other options (such as
+:php:`allowAttributes`) in order to only run certain instructions on the :php:`RteHtmlParser` object.
+
+.. index:: RTE, NotScanned, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-93726-DeprecatedTypoScriptParserRelatedProperties.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93726-DeprecatedTypoScriptParserRelatedProperties.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-93726-DeprecatedTypoScriptParserRelatedProperties.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93726-DeprecatedTypoScriptParserRelatedProperties.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93837-SpecialPropertyOfTCATypeSelect.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93837-SpecialPropertyOfTCATypeSelect.rst
new file mode 100644
index 000000000000..de4467c176b1
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93837-SpecialPropertyOfTCATypeSelect.rst
@@ -0,0 +1,56 @@
+.. include:: ../../Includes.txt
+
+=========================================================
+Deprecation: #93837 - special property of TCA type select
+=========================================================
+
+See :issue:`93837`
+
+Description
+===========
+
+The :php:`special` property of TCA type :php:`select` was introduced to enrich the
+items array with dynamic values, e.g. the available site languages or
+page types.
+
+Since this usually is exactly what an :php:`itemsProcFunc` does, all
+those options are migrated to such functions, removing complexity
+from the TCA :php:`select` type. As these options are mainly for internal
+use in the backend user and backend usergroup records, the new
+:php:`itemsProcFunc` functions are marked as :php:`@internal`. This means, they
+are not considered public API and therefore not part of TYPO3s backwards
+compatibility promise.
+
+The only option which is considered public API is :php:`special=languages`,
+which was already migrated to the new TCA type :php:`language` in :issue:`57082`.
+
+Impact
+======
+
+Using the TCA property :php:`special` inside the :php:`[columns][config]`
+section of columns with TCA type :php:`select` triggers a PHP :php:`E_USER_DEPRECATED` error.
+
+When extending :php:`AbstractItemProvider` and directly calling
+:php:`addItemsFromSpecial()`, also a PHP :php:`E_USER_DEPRECATED` error will be raised.
+The extension scanner will also detect such calls.
+
+Affected Installations
+======================
+
+All installations using the :php:`special` property with TCA type :php:`select` or
+directly calling :php:`AbstractItemProvider->addItemsFromSpecial()`.
+
+Migration
+=========
+
+While it's very unlikely that the :php:`special` property with another option
+than :php:`languages` is used in custom extension code, you nevertheless have to
+replace them with a :php:`itemsProcFunc` in such case. Either by creating
+your own implementation or by copying the one from Core. Have a look at the
+:php:`index_config` TCA configuration in EXT:indexed_search how this can be
+achieved. You can also find detailed information about :php:`itemsProcFunc`
+in the documentation_.
+
+.. _documentation: https://docs.typo3.org/m/typo3/reference-tca/master/en-us/ColumnsConfig/CommonProperties/ItemsProcFunc.html
+
+.. index:: Backend, TCA, FullyScanned, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-93899-FormEnginesRequestConfirmationOnFieldChangeDeprecated.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93899-FormEnginesRequestConfirmationOnFieldChange.rst
similarity index 95%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-93899-FormEnginesRequestConfirmationOnFieldChangeDeprecated.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93899-FormEnginesRequestConfirmationOnFieldChange.rst
index a40340f034fb..153a546a414c 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-93899-FormEnginesRequestConfirmationOnFieldChangeDeprecated.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93899-FormEnginesRequestConfirmationOnFieldChange.rst
@@ -1,8 +1,8 @@
 .. include:: ../../Includes.txt
 
-==============================================================================
-Deprecation: #93899 - FormEngine's requestConfirmationOnFieldChange deprecated
-==============================================================================
+===================================================================
+Deprecation: #93899 - FormEngine's requestConfirmationOnFieldChange
+===================================================================
 
 See :issue:`93899`
 
diff --git a/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93944-FileTreeAsIframeMigratedToSVG-basedTree.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93944-FileTreeAsIframeMigratedToSVG-basedTree.rst
new file mode 100644
index 000000000000..0ce42096a4ab
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93944-FileTreeAsIframeMigratedToSVG-basedTree.rst
@@ -0,0 +1,47 @@
+.. include:: ../../Includes.txt
+
+====================================================================
+Deprecation: #93944 - File Tree as iframe migrated to SVG-based tree
+====================================================================
+
+See :issue:`93944`
+
+Description
+===========
+
+When registered backend modules have the legacy-tree navigation frame
+:html:`file_navframe` set via the module configuration
+:php:`navigationFrameModule`, the modules are now using the new SVG-based Folder
+tree view as component (non-iFrame).
+
+
+Impact
+======
+
+Modules still registering the old :html:`file_navframe` option via
+Module Configuration :php:`navigationFrameModule` will automatically be migrated
+to the new Component, and a PHP :php:`E_USER_DEPRECATED` error will be triggered.
+
+
+Affected Installations
+======================
+
+TYPO3 installations with custom extensions having backend modules
+using the filelist navigation frame (folder-based tree).
+
+Modules that use the implicit main module configuration and are
+located directly within the "File" module are not affected.
+
+
+Migration
+=========
+
+Change the affected code in your ext_tables.php:
+
+:php:`'navigationFrameModule' => 'file_navframe'`
+
+to
+
+:php:`'navigationComponentId' => 'TYPO3/CMS/Backend/Tree/FileStorageTreeContainer'`
+
+.. index:: Backend, NotScanned, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-93975-DeprecatedTBE_EDITORfieldChanged.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93975-TBE_EDITORfieldChanged.rst
similarity index 86%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-93975-DeprecatedTBE_EDITORfieldChanged.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93975-TBE_EDITORfieldChanged.rst
index 25daf8c2361f..66969d2de87f 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-93975-DeprecatedTBE_EDITORfieldChanged.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Deprecation-93975-TBE_EDITORfieldChanged.rst
@@ -1,8 +1,8 @@
 .. include:: ../../Includes.txt
 
-==========================================================
-Deprecation: #93975 - Deprecated TBE_EDITOR.fieldChanged()
-==========================================================
+===============================================
+Deprecation: #93975 - TBE_EDITOR.fieldChanged()
+===============================================
 
 See :issue:`93975`
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-57082-NewTCATypeLanguage.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-57082-NewTCATypeLanguage.rst
similarity index 56%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-57082-NewTCATypeLanguage.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Feature-57082-NewTCATypeLanguage.rst
index e40967115b35..ddba9dd07469 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-57082-NewTCATypeLanguage.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-57082-NewTCATypeLanguage.rst
@@ -9,31 +9,31 @@ See :issue:`57082`
 Description
 ===========
 
-A new TCA field type called `language` has been added to TYPO3 Core. It's main
+A new TCA field type called :php:`language` has been added to TYPO3 Core. Its main
 purpose is to simplify the TCA language configuration. It therefore supersedes
-the `special=languages` option of TCA columns with `type=select` as well as the
-now mis-use of the `foreign_table` option, being set to `sys_language`.
+the :php:`special=languages` option of TCA columns with :php:`type=select` as well as the
+now mis-use of the :php:`foreign_table` option, being set to :sql:`sys_language`.
 
 Since the introduction of site configurations and the corresponding site
-languages back in v9, the `sys_language` table was not longer the only source
-of thruth regarding available languages. Actually, the languages, available for
-a record, are defined by the associated site configuration.
+languages back in v9, the :sql:`sys_language` table was not longer the only source
+of truth regarding available languages. The languages available for a record are
+defined by the associated site configuration.
 
-The new field therefore allows to finally decouple the actually available site
-languages from the `sys_language` table. This effectively reduces quite an
+Therefore, the new field allows to finally decouple the available site
+languages from the :sql:`sys_language` table. This effectively reduces quite an
 amount of code and complexity, since no relations have to be fetched and
-processed anymore. This also makes the `sys_refindex` table a bit smaller,
+processed anymore. This also makes the :sql:`sys_refindex` table a bit smaller,
 since no entries have to be added for this relation anymore. To clean up your
-exisiting reference index, you might use the CLI command
+existing reference index, you might use the CLI command
 :php:`bin/typo3 referenceindex:update`.
 
-Another pain point was the special `-1` language which always had to be added
+Another pain point was the special :php:`-1` language which always had to be added
 to each TCA configuration manually. Thus, a lot of different implementations
 of this special case could be found in one and the same TYPO3 installation.
 
 The new TCA type now automatically displays all available languages for the
 current context (the corresponding site configuration) and also automatically
-adds the special `-1` language for all record types, except `pages`.
+adds the special :php:`-1` language for all record types, except :sql:`pages`.
 
 .. code-block:: php
 
@@ -56,6 +56,7 @@ adds the special `-1` language for all record types, except `pages`.
       'type' => 'language'
    ]
 
+
 .. code-block:: php
 
    // Before
@@ -80,21 +81,23 @@ adds the special `-1` language for all record types, except `pages`.
       'type' => 'language'
    ]
 
-Since the new TCA type is mostly based on the `type=select` internally, most
+
+Since the new TCA type is mostly based on the :php:`type=select` internally, most
 of the associated TCA and TSconfig options can still be applied. This includes
-e.g. the `selectIcons` field wizard, as well as the :typoscript:`keepItems`
+e.g. the :php:`selectIcons` field wizard, as well as the :typoscript:`keepItems`
 and :typoscript:`removeItems` page TSconfig options.
 
-In records on root level (`pid=0`) or on a page, outside of a site context,
-all languages form all site configurations are displayed in the new field.
+In records on root level (:sql:`pid=0`) or on a page, outside of a site context,
+all languages from all site configurations are displayed in the new field.
 
-An automatic TCA migration is performed on the fly, migrating all occurences
-to the new TCA type and adding a deprecation message to the deprecation log
-where code adaption has to take place. Occurences are all columns, defined as
-:php:`$TCA['ctrl']['languageField']`, as well as all columns, using the
-`special=languages` option in combination with `type=select`.
+An automatic TCA migration is performed on the fly, migrating all occurrences
+to the new TCA type and triggering a PHP :php:`E_USER_DEPRECATED` error
+where code adaption has to take place. Columns defined as
+:php:`$TCA['ctrl']['languageField']`, as well as all columns using the
+:php:`special=languages` option in combination with :php:`type=select` are
+affected.
 
-Note that the migration resets the whole `config` array to use the new TCA
+Note that the migration resets the whole :php:`config` array to use the new TCA
 type. Custom setting such as field wizards are not evaluated until the TCA
 configuration is adapted.
 
diff --git a/typo3/sysext/core/Documentation/Changelog/11.2/Feature-73176-FilterableTreesInRecordSelectorsAndLinkPickers.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-73176-FilterableTreesInRecordSelectorsAndLinkPickers.rst
new file mode 100644
index 000000000000..785044855376
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-73176-FilterableTreesInRecordSelectorsAndLinkPickers.rst
@@ -0,0 +1,59 @@
+.. include:: ../../Includes.txt
+
+=======================================================================
+Feature: #73176 - Filterable Trees in Record Selectors and Link Pickers
+=======================================================================
+
+See :issue:`73176`
+
+Description
+===========
+
+TYPO3's Page Tree, which was reworked in TYPO3 v9 to be powered by SVG rendering,
+and the Folder Tree in the File list module, which was also migrated to SVG
+rendering in TYPO3 v11.1, have been integrated in the so-called Record
+Selectors / File Selector ("Element Browser") and Link Pickers of TYPO3
+backend.
+
+The Record Selectors are used when e.g. choosing a :guilabel:`Target Page` for a
+:guilabel:`Shortcut Page`, or selecting a :guilabel:`Storage Page` in a plugin.
+
+The file selectors are used when choosing a file for a IRRE-based FAL-based
+file reference.
+
+Link Pickers are used when linking to a specific page, content element, file,
+folder or custom records, such as news ("related news" in EXT:news).
+
+All of these components within TYPO3 backend are now powered by SVG-based
+tree renderings. In addition, this means they ship with the same feature-set
+as the main navigation components, such as:
+
+*  A filter within the items of a tree (for folder-based trees, this means,
+   searching for file names within a folder is also possible)
+*  A JSON-based AJAX-loading functionality for fetching just parts of the tree,
+   keeping the same expand/collapse state as the main tree
+*  The Page Tree's "Temporary Mount Point" feature has the same functionality
+   and styling as the main navigation component
+*  Resizing and expand/collapse of the tree area in all modals
+*  Keyboard navigation within the tree components
+
+The newly added tree components have the following addons:
+
+*  When selecting (Record Selector) or linking to a specific page or folder, the
+   item can be selected by a specific "link" action on the right hand of the tree.
+*  Only showing specific mount points configurable via
+   TSconfig :typoscript:`options.pageTree.altElementBrowserMountPoints`
+*  The content area (for selecting a record on a specific page) is dynamically
+   loaded via AJAX and loads much faster than before
+
+
+Impact
+======
+
+All page- and folder-based trees are now completely streamlined all over TYPO3's
+backend, in terms of UX and code / implementation.
+
+The overall UX feels much faster for every editor of TYPO3, and the consistency
+makes TYPO3 more intuitive with an improved search/filter and record selector.
+
+.. index:: Backend, JavaScript, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-89762-AddPaginationForFormManagement.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-89762-AddPaginationForFormManagement.rst
similarity index 62%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-89762-AddPaginationForFormManagement.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Feature-89762-AddPaginationForFormManagement.rst
index 67e8d01b1d61..75a1bb34352c 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-89762-AddPaginationForFormManagement.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-89762-AddPaginationForFormManagement.rst
@@ -9,15 +9,15 @@ See :issue:`89762`
 Description
 ===========
 
-To increase the usability, a pagination is now integrated in the
-FormManagement module. Thus, the listing is now limited to 20 forms
+To enhance usability, a pagination is now integrated in the
+form management module. Thus, the listing is now limited to 20 forms
 per page.
 
 Impact
 ======
 
 You'll notice a pagination above and below the forms listing in the
-FormManagement module, which can be used to navigate through the
-paginated forms.
+form management module, which can be used to navigate through the
+forms listing.
 
 .. index:: Backend, ext:form
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-93188-PossibilityToDisableHreflangPerPage.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93188-PossibilityToDisableHreflangPerPage.rst
similarity index 75%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-93188-PossibilityToDisableHreflangPerPage.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Feature-93188-PossibilityToDisableHreflangPerPage.rst
index e11174071534..202afcd09a2e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-93188-PossibilityToDisableHreflangPerPage.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93188-PossibilityToDisableHreflangPerPage.rst
@@ -10,8 +10,8 @@ Description
 ===========
 
 Although it should not be needed to disable the hreflang generation, people might
-have a reason to disable the hreflang generation. If for some reason core does not
-render the proper hreflang tags and also the PSR-14 event called `ModifyHrefLangTagsEvent`
+have a reason to disable it. If for some reason Core does not
+render the proper hreflang tags and also the :php:`ModifyHrefLangTagsEvent` PSR-14 event
 is not enough, you are now able to disable the generation of the hreflang tags
 via TypoScript. This can be done per page or part of your tree depending on where
 you set the configuration.
@@ -27,6 +27,6 @@ TypoScript setup.
 Impact
 ======
 
-Only when you set this option, the hreflang generation will be skipped.
+If the option is set to :typoscript:`1`, hreflang generation will be skipped.
 
 .. index:: Frontend, TypoScript, ext:seo
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-93209-FALAddGetFileToTYPO3CMSCoreResourceFolder.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93209-FALAddGetFileToTYPO3CMSCoreResourceFolder.rst
similarity index 61%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-93209-FALAddGetFileToTYPO3CMSCoreResourceFolder.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Feature-93209-FALAddGetFileToTYPO3CMSCoreResourceFolder.rst
index 4747e51679a4..201e0f7ea3c7 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-93209-FALAddGetFileToTYPO3CMSCoreResourceFolder.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93209-FALAddGetFileToTYPO3CMSCoreResourceFolder.rst
@@ -9,17 +9,18 @@ See :issue:`93209`
 Description
 ===========
 
-The FAL Folder object now contains a new convenience method :php:`getFile()`.
+The FAL :php:`\TYPO3\CMS\Core\Resource\Folder` object now contains a new
+convenience method :php:`getFile()`.
 
-The :php:`FolderInterface` does not contain the definition yet, as this would
-be a breaking change, thus, a comment is added to make sure the Interface
-gets this addition in v12 as well.
+The :php:`\TYPO3\CMS\Core\Resource\FolderInterface` does not contain the
+definition yet, as this would be a breaking change, thus, a comment is added to
+make sure the interface gets this addition in TYPO3 v12 as well.
 
 Impact
 ======
 
 When dealing as a developer with FAL Folder objects, the method
 :php:`$folder->getFile("filename.ext")` can now be used instead of
-:php:`$folder->getStorage()->getFileInFolder("filename.ext", $folder)`
+:php:`$folder->getStorage()->getFileInFolder("filename.ext", $folder)`.
 
 .. index:: FAL, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-93591-AllowGroupIdLookupInConditionsWithArrayOperator.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93591-AllowGroupIdLookupInConditionsWithArrayOperator.rst
similarity index 72%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-93591-AllowGroupIdLookupInConditionsWithArrayOperator.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Feature-93591-AllowGroupIdLookupInConditionsWithArrayOperator.rst
index 1c2986de8ae3..d5c73483379b 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-93591-AllowGroupIdLookupInConditionsWithArrayOperator.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93591-AllowGroupIdLookupInConditionsWithArrayOperator.rst
@@ -10,14 +10,16 @@ Description
 ===========
 
 In the backend and frontend the array of user group ids of the current backend user
-is now available as backend.user.userGroupIds. In the frontend the the array of
-user group ids of the current frontend user is available as frontend.user.userGroupIds.
+is now available as :typoscript:`backend.user.userGroupIds`.
+
+In the frontend the array of user group ids of the current frontend user is available
+as :typoscript:`frontend.user.userGroupIds`.
 
 
 Impact
 ======
 
-This allows for a native Symfony Expression Syntax in TypoScript conditions, eg.
+This allows for a native Symfony Expression Syntax in TypoScript conditions, e.g.
 
 .. code-block:: typoscript
 
@@ -26,6 +28,6 @@ This allows for a native Symfony Expression Syntax in TypoScript conditions, eg.
    [2 in backend.user.userGroupIds]
 
 With this syntax you can match backend user groups in the frontend without
-an awkward "like" expression on the comma-separated list of user group ids.
+a "like" expression on the comma-separated list of user group ids.
 
 .. index:: Backend, Frontend, TSConfig, TypoScript, ext:backend, ext:frontend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-93606-PossibilityToDisableCanonicalPerPage.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93606-PossibilityToDisableCanonicalPerPage.rst
similarity index 66%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-93606-PossibilityToDisableCanonicalPerPage.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Feature-93606-PossibilityToDisableCanonicalPerPage.rst
index 3d892076ad36..00ff26ba2522 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-93606-PossibilityToDisableCanonicalPerPage.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93606-PossibilityToDisableCanonicalPerPage.rst
@@ -9,9 +9,9 @@ See :issue:`93606`
 Description
 ===========
 
-Although it should not be needed to disable the canonical generation, people might
-have a reason to disable the canonical generation. If for some reason core does not
-render the proper canonical tag and also the PSR-14 event called `ModifyUrlForCanonicalTagEvent`
+Although it should not be needed to disable the generation of :html:`canonical`, people might
+have a reason to disable it. If for some reason Core does not
+render the proper canonical tag and also the :php:`ModifyUrlForCanonicalTagEvent` PSR-14 event
 is not enough, you are now able to disable the generation of the canonical tag
 via TypoScript. This can be done per page or part of your tree depending on where
 you set the configuration.
@@ -27,6 +27,6 @@ TypoScript setup.
 Impact
 ======
 
-Only when you set this option, the canonical generation will be skipped.
+If the option is set to :typoscript:`1`, the canonical generation will be skipped.
 
 .. index:: Frontend, TypoScript, ext:seo
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-93651-ProvideListOfAvailableSystemLocales.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93651-ProvideListOfAvailableSystemLocales.rst
similarity index 60%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-93651-ProvideListOfAvailableSystemLocales.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Feature-93651-ProvideListOfAvailableSystemLocales.rst
index 5c35f4a74c67..91c29f7fc611 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-93651-ProvideListOfAvailableSystemLocales.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93651-ProvideListOfAvailableSystemLocales.rst
@@ -10,7 +10,12 @@ Description
 ===========
 
 Every language of a site requires at least one locale which is used to format times, dates,
-currencies and other values. Additional locales can be added as fallback locales (comma separated).
+currencies and other locale-dependent values. Additional locales can be added as fallback
+locales (comma separated).
+
+The site configuration form for site languages provides the available locales as a select field,
+enabling easy selection of a value, rather than typing in the expected one, which might or might not
+be available.
 
 
 Impact
diff --git a/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93663-BackendUsersPreferredUILanguageStoredAsDBField.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93663-BackendUsersPreferredUILanguageStoredAsDBField.rst
new file mode 100644
index 000000000000..0e1e76cb2e5a
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93663-BackendUsersPreferredUILanguageStoredAsDBField.rst
@@ -0,0 +1,60 @@
+.. include:: ../../Includes.txt
+
+=========================================================================
+Feature: #93663 - Backend user's preferred UI language stored as DB field
+=========================================================================
+
+See :issue:`93663`
+
+Description
+===========
+
+In previous TYPO3 versions, administrators could create new backend
+users and select from the list of all supported TYPO3-internal
+languages for their backend language (= all labels from
+XLIFF files). This information was stored in the database field
+:sql:`be_users.lang` and was only used on the first login of a user
+into TYPO3 backend.
+
+The backend users themselves could use the :guilabel:`User settings` module
+to change the UI language to their preferred language, based on the
+available language packs in the system.
+
+This information was then stored in the user's :sql:`uc` (user configuration),
+an arbitrary settings field.
+
+This approach - built over 18 years ago without any significant
+changes ever since - had several downsides:
+
+*  The database field :sql:`be_users.lang` was not really needed
+*  Administrators did not see available language packs when changing the language
+*  Administrators could only change an editor's preferred language by
+   switching to the user (:pn:`Switch User Mode`).
+*  Administrators could not filter / sort editors to see what languages the
+   users had chosen
+*  Fetching the user's preferred language always meant to fetch the whole
+   :sql:`uc` information and unpack it.
+*  The preferred language was only selected if the user had logged in for
+   the first time to initialize the :sql:`uc` values.
+
+Instead, TYPO3 now keeps the current language preference in the
+database field :sql:`be_users.lang`, allowing both editors and administrators
+to access the same value for fetching this information.
+
+
+Impact
+======
+
+When the user changes their language in the user settings module,
+the database record gets updated, and it is clear where this information is
+stored. It is now the same logic when an administrator updates the editor's
+record via FormEngine.
+
+The value is now always filled, and if English is chosen, the value
+is set to the string :php:`default` (instead of an empty value).
+
+An upgrade wizard migrates existing :sql:`uc` values into the database
+fields. The :sql:`uc` entry :sql:`user->uc['lang']` is kept in sync for
+backwards-compatibility.
+
+.. index:: Backend, JavaScript, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-93794-OverrideTCADescriptionWithTSconfig.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93794-OverrideTCADescriptionWithTSconfig.rst
similarity index 88%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-93794-OverrideTCADescriptionWithTSconfig.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Feature-93794-OverrideTCADescriptionWithTSconfig.rst
index 4f1690efd1c7..617c015c80ea 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-93794-OverrideTCADescriptionWithTSconfig.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93794-OverrideTCADescriptionWithTSconfig.rst
@@ -9,7 +9,7 @@ See :issue:`93794`
 Description
 ===========
 
-The TCA description, introduced in #85410, allows to define a description
+The TCA description, introduced in :issue:`85410`, allows to define a description
 for a TCA field, next to its label. Since the purpose of a field may change
 depending on the current page, it is now possible to override the TCA
 description property with page TSconfig.
@@ -39,7 +39,7 @@ Also referencing language labels is supported.
 
 .. note::
 
-   The new option can not only be used to override an exisiting property,
+   The new option can not only be used to override an existing property,
    but also to set a description for a field, that has not yet been
    configured a description in TCA.
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-93857-ResizableNavigationComponentForAllElementRecordSelectors.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93857-ResizableNavigationComponentForAllElementRecordSelectors.rst
similarity index 84%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-93857-ResizableNavigationComponentForAllElementRecordSelectors.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Feature-93857-ResizableNavigationComponentForAllElementRecordSelectors.rst
index 3bfa92ca69f1..bb455ca0514e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-93857-ResizableNavigationComponentForAllElementRecordSelectors.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93857-ResizableNavigationComponentForAllElementRecordSelectors.rst
@@ -17,9 +17,9 @@ All modal areas with a Page Tree or File-based Folder Tree now
 contain the same feature-set of collapsing / resizing, except
 that the width is not installation-wide but is kept for the
 main navigation area (initially 300 pixels) in a different place (set in the
-Backend Users' "uc" `navigation.width` property) than for the element browser's
-modal areas (initially 250 pixels, set in the Backend Users' "uc"
-`selector.navigation.width` property).
+backend user's :sql:`uc` :php:`navigation.width` property) than for the element browsers
+modal areas (initially 250 pixels, set in the backend user's :sql:`uc`
+:php:`selector.navigation.width` property).
 
 A custom Lit-based web component is added, which is now re-used
 in various places, and uses the same markup in all contexts.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-93908-Image-decoding-attribute.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93908-Image-decoding-attribute.rst
similarity index 50%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-93908-Image-decoding-attribute.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Feature-93908-Image-decoding-attribute.rst
index fcad8ec01b2c..8632aaa1c4d2 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-93908-Image-decoding-attribute.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93908-Image-decoding-attribute.rst
@@ -9,10 +9,10 @@ See :issue:`93908`
 Description
 ===========
 
-TYPO3 now supports the `decoding` HTML attribute in :html:`<img>`
+TYPO3 now supports the :html:`decoding` HTML attribute in :html:`<img>`
 tags.
 
-Supported browsers then choose to decode these images asynchronously to not
+Supported browsers choose to decode these images asynchronously to not
 prevent presentation of other content. This has an effect of presenting
 non-image content faster. However, the image content is missing on screen until
 the decode finishes. Once the decode is finished, the screen is updated with the
@@ -20,20 +20,20 @@ image.
 
 The configuration option is available via TypoScript constants and
 can be easily adjusted via the TypoScript Constant Editor in the Template
-module. The default value is "".
+module. The default value is an empty string.
 
 Impact
 ======
 
-TYPO3 Frontend now decodes images in content elements asynchronously by default
-when using TYPO3's templates from Fluid Styled Content.
+TYPO3 frontend decodes images in content elements asynchronously by default
+when using TYPO3 templates from Fluid Styled Content.
 
-Using the TypoScript constant `styles.content.image.imageDecoding`,
-the behavior can be modified generally to be either set to `sync`, `async`
-`auto` or to an empty value which removes the property.
+Using the TypoScript constant :typoscript:`styles.content.image.imageDecoding`,
+the behavior can be modified generally to be either set to :typoscript:`sync`, :typoscript:`async`
+:typoscript:`auto` or to an empty value which removes the property.
 
-The Fluid ImageViewHelper and MediaViewHelper have the possibility to set this
-attribute via :html:`<f:image src="{fileObject}" treatIdAsReference="true" decoding="async">`
+The Fluid :php:`ImageViewHelper` and :php:`MediaViewHelper` have the possibility to set this
+attribute via :html:`<f:image src="{fileObject}" decoding="async">`
 and :html:`<f:media file="{fileObject}" decoding="async">`.
 
 .. index:: Frontend, ext:fluid_styled_content
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-93988-BackendModuleURLsReflectIntoBrowserAdressbar.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93988-BackendModuleURLsReflectIntoBrowserAddressbar.rst
similarity index 64%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-93988-BackendModuleURLsReflectIntoBrowserAdressbar.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Feature-93988-BackendModuleURLsReflectIntoBrowserAddressbar.rst
index 08dfca9fdb32..c4369fb39430 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-93988-BackendModuleURLsReflectIntoBrowserAdressbar.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Feature-93988-BackendModuleURLsReflectIntoBrowserAddressbar.rst
@@ -1,22 +1,22 @@
 .. include:: ../../Includes.txt
 
-====================================================================
-Feature: #93988 - Backend module URLs reflect into browser adressbar
-====================================================================
+======================================================================
+Feature: #93988 - Backend module URLs reflect into browser address bar
+======================================================================
 
 See :issue:`93988`
 
 Description
 ===========
 
-Backend module URLs are now reflected into the browser adressbar, whenever a
+Backend module URLs are now reflected into the browser address bar, whenever a
 backend module or a FormEngine record is opened.
 
 The given URL can be bookmarked or shared with other editors and allows to
 re-open the TYPO3 backend with the given context.
 
-A custom Lit-based web componenent router is added which reflects module URLs
-into the browser adress bar and at the same time prepares for native web
+A custom Lit-based web component router is added which reflects module URLs
+into the browser address bar and at the same time prepares for native web
 components to be used as future iframe module alternatives.
 
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-88824-AddCacheForErrorPageHandling.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Important-88824-AddCacheForErrorPageHandling.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-88824-AddCacheForErrorPageHandling.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Important-88824-AddCacheForErrorPageHandling.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-93398-PossibilityToIgnoreSubmittedValuesInHiddenViewHelper.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Important-93398-PossibilityToIgnoreSubmittedValuesInHiddenViewHelper.rst
similarity index 67%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-93398-PossibilityToIgnoreSubmittedValuesInHiddenViewHelper.rst
rename to typo3/sysext/core/Documentation/Changelog/11.2/Important-93398-PossibilityToIgnoreSubmittedValuesInHiddenViewHelper.rst
index 9f5dbd6ed599..fbc0315c2795 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-93398-PossibilityToIgnoreSubmittedValuesInHiddenViewHelper.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Important-93398-PossibilityToIgnoreSubmittedValuesInHiddenViewHelper.rst
@@ -9,11 +9,11 @@ See :issue:`93398`
 Description
 ===========
 
-A new argument :php:`respectSubmittedDataValue` is added to the Fluid
-:php:`HiddenViewHelper`. It allows to enable or disable the usage of
+A new argument :php:`respectSubmittedDataValue` is added to Fluid's
+:php:`HiddenViewHelper` view helper. It allows to enable or disable the usage of
 previously submitted values for the corresponding field. This is especially
-usefull if dealing with sub requests, e.g. when a :php:`FowardResponse` is
-being dispatched within extbase.
+useful if dealing with sub requests, e.g. when a :php:`\TYPO3\CMS\Extbase\Http\ForwardResponse` is
+being dispatched within Extbase.
 
 Example
 =======
diff --git a/typo3/sysext/core/Documentation/Changelog/11.2/Index.rst b/typo3/sysext/core/Documentation/Changelog/11.2/Index.rst
new file mode 100644
index 000000000000..9488633d2594
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/11.2/Index.rst
@@ -0,0 +1,51 @@
+.. include:: ../../Includes.txt
+
+============
+11.2 Changes
+============
+
+**Table of contents**
+
+.. contents::
+   :local:
+   :depth: 1
+
+Breaking Changes
+================
+
+None since TYPO3 v11.0 release.
+
+.. attention::
+
+   After TYPO3 v11.0, only new functionality with a solid migration path can be added on top,
+   with aiming for as little as possible breaking changes after the initial v11.0 release on the way to LTS.
+
+Features
+========
+
+.. toctree::
+   :maxdepth: 1
+   :titlesonly:
+   :glob:
+
+   Feature-*
+
+Deprecation
+===========
+
+.. toctree::
+   :maxdepth: 1
+   :titlesonly:
+   :glob:
+
+   Deprecation-*
+
+Important
+=========
+
+.. toctree::
+   :maxdepth: 1
+   :titlesonly:
+   :glob:
+
+   Important-*
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-92992-HookT3libclasst3lib_parsehtml_procphptransformation.rst b/typo3/sysext/core/Documentation/Changelog/master/Deprecation-92992-HookT3libclasst3lib_parsehtml_procphptransformation.rst
deleted file mode 100644
index 4bb5104ed15c..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-92992-HookT3libclasst3lib_parsehtml_procphptransformation.rst
+++ /dev/null
@@ -1,41 +0,0 @@
-.. include:: ../../Includes.txt
-
-==================================================================
-Deprecation: #92992 - Hook t3lib_parsehtml_proc.php:transformation
-==================================================================
-
-See :issue:`92992`
-
-Description
-===========
-
-Since the deprecation of several internal functions in the RteHtmlParser in
-TYPO3 10.2 (
-.. _linked: https://docs.typo3.org/c/typo3/cms-core/10.2/en-us/Changelog/9.5/Deprecation-86440-InternalMethodsAndPropertiesWithinRteHtmlParser.html)
-the hook :php:`t3lib/class.t3lib_parsehtml_proc.php:transformation` became quite useless.
-
-It is now impossible to access the tsconfig configuration and other information
-that you would need for examples that we had the documentation like here:
-.. _linked: https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/Rte/Transformations/CustomApi.html
-
-
-Impact
-======
-
-Calling the hook will trigger a PHP :php:`E_USER_DEPRECATED` error and not be executed anymore with TYPO3 v12.
-
-
-Affected Installations
-======================
-
-All installations with extensions installed that implement the hook.
-
-
-Migration
-=========
-
-Migrate to use the public API only and use other options (such as
-:php:`allowAttributes` instead of :php:`dontRemoveUnknownTags_db`) in order to
-only run certain instructions on the :php:`RteHtmlParser` object.
-
-.. index:: RTE, NotScanned, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-93837-DeprecatedSpecialPropertyOfTCATypeSelect.rst b/typo3/sysext/core/Documentation/Changelog/master/Deprecation-93837-DeprecatedSpecialPropertyOfTCATypeSelect.rst
deleted file mode 100644
index 9edf7c3a1910..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-93837-DeprecatedSpecialPropertyOfTCATypeSelect.rst
+++ /dev/null
@@ -1,56 +0,0 @@
-.. include:: ../../Includes.txt
-
-====================================================================
-Deprecation: #93837 - Deprecated special property of TCA type select
-====================================================================
-
-See :issue:`93837`
-
-Description
-===========
-
-The `special` property of TCA type `select` was introduced to enrich the
-items array with dynamic value, e.g. the available site languages or
-page types.
-
-Since this usually is exactly what an :php:`itemsProcFunc` does, all
-those options are migrated to such functions, removing complexity
-from the TCA `select` type. As these options are mainly for internal
-use in `be_users` and `be_groups`, the new :php:`itemsProcFunc` functions
-are marked as :php:`@internal`. This means, they are not considered public
-API and therefore not part of TYPO3's backwards-compatibility promise.
-
-The only option which is considered public API is `special=languages`,
-which was already migrated to the new TCA type `language` in :issue:`57082`.
-
-Impact
-======
-
-Using the TCA property `special` inside the :php:`[columns][config]`
-section of columns with TCA type `select` adds a deprecation message to
-the deprecation log.
-
-When extending :php:`AbstractItemProvider` and directly calling
-:php:`addItemsFromSpecial()`, a deprecation message will be added to
-the deprecation log. The extension scanner will also detect such calls.
-
-Affected Installations
-======================
-
-All installations using the `special` property with TCA type `select` or
-directly calling :php:`AbstractItemProvider->addItemsFromSpecial()`.
-
-Migration
-=========
-
-While it's very unlikely that the `special` property with another option
-than `languages` is used in custom extension code, you nevertheless have to
-replace them with a :php:`itemsProcFunc` in such case. Either by creating
-your own implementation or by copying the one from Core. Have a look at the
-:php:`index_config` TCA configuration in EXT:indexed_search how this can be
-achieved. You can also find detailed information about :php:`itemsProcFunc`
-in the documentation_.
-
-.. _documentation: https://docs.typo3.org/m/typo3/reference-tca/master/en-us/ColumnsConfig/CommonProperties/ItemsProcFunc.html
-
-.. index:: Backend, TCA, FullyScanned, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-93944-FileTreeAsIframeMigratedToSVG-basedTree.rst b/typo3/sysext/core/Documentation/Changelog/master/Deprecation-93944-FileTreeAsIframeMigratedToSVG-basedTree.rst
deleted file mode 100644
index f42077334a75..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-93944-FileTreeAsIframeMigratedToSVG-basedTree.rst
+++ /dev/null
@@ -1,48 +0,0 @@
-.. include:: ../../Includes.txt
-
-====================================================================
-Deprecation: #93944 - File Tree as iframe migrated to SVG-based tree
-====================================================================
-
-See :issue:`93944`
-
-Description
-===========
-
-When registering Backend modules having the legacy-tree navigation frame
-"file_navframe" set via the module configuration "navigationFrameModule",
-the modules are now using the new SVG-based Folder tree view as
-component (non-iFrame).
-
-
-Impact
-======
-
-Modules still registering the old "file_navframe" option via
-Module Configuration "navigationFrameModule" will automatically
-be migrated to the new Component, and a deprecation warning will
-be triggered.
-
-
-Affected Installations
-======================
-
-TYPO3 installations with custom extensions having Backend modules
-using the filelist navigation frame (folder-based tree).
-
-Modules that use the implicit main module configuration and are
-located directly within the "File" module, are not affected.
-
-
-Migration
-=========
-
-Change the affected code in your ext_tables.php:
-
-   "navigationFrameModule" => "file_navframe"
-
-to
-
-   "navigationComponentId" => "TYPO3/CMS/Backend/Tree/FileStorageTreeContainer"
-
-.. index:: Backend, NotScanned, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-73176-FilterableTreesInRecordSelectorsAndLinkPickers.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-73176-FilterableTreesInRecordSelectorsAndLinkPickers.rst
deleted file mode 100644
index fa4a7055f198..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-73176-FilterableTreesInRecordSelectorsAndLinkPickers.rst
+++ /dev/null
@@ -1,58 +0,0 @@
-.. include:: ../../Includes.txt
-
-=======================================================================
-Feature: #73176 - Filterable Trees in Record Selectors and Link Pickers
-=======================================================================
-
-See :issue:`73176`
-
-Description
-===========
-
-TYPO3's Page Tree, which was reworked in TYPO3 v9 to be powered by SVG rendering,
-and the Folder Tree in the File list module, which was also migrated to SVG
-rendering in TYPO3 v11.1, have been integrated in the so-called Record
-Selectors / File Selector ("Element Browser") and Link Pickers of TYPO3
-Backend.
-
-The Record Selectors are used when e.g. choosing a Target Page for a
-Shortcut-Page, or selecting a Storage Page in a plugin.
-
-The File Selectors are used when choosing a File for a IRRE-based FAL-based
-File Reference.
-
-Link Pickers are used when linking to a specific page, content element, file,
-folder or custom records, such as news ("related news" in EXT:news).
-
-All of these components within TYPO3 Backend are now powered by SVG-based
-tree renderings. In addition, this means they ship with the same feature-set
-as the main navigation components, such as:
-
-* A filter within the items of a tree (for folder-based trees, this means,
-  searching for file names within a folder is also possible)
-* A JSON-based AJAX-loading functionality for fetching just parts of the tree,
-  keeping the same expand/collapse state as the main tree
-* The Page Tree's "Temporary Mount Point" feature has the same functionality
-  and styling as the main navigation component
-* Resizing and expand/collapse of the tree area in all modals are available
-* Keyboard Navigation within the tree components
-
-The newly added tree components have the following addons:
-* When selecting (Record Selector) or linking to a specific page or folder, the
-  item can be selected by a specific "link" action on the right hand of the tree.
-* Only showing specific mount points configurable via
-  TSconfig `options.pageTree.altElementBrowserMountPoints`
-* The content area (for selecting a record on a specific page) is dynamically
-  loaded via AJAX and loads much faster than before.
-
-
-Impact
-======
-
-All page- and folder-based trees are now completely streamlined all over TYPO3
-Backend, in terms of UX and code / implementation.
-
-The overall UX feels much faster for every editor of TYPO3, and the consistency
-makes TYPO3 more intuitive with an improved search/filter and record selector.
-
-.. index:: Backend, JavaScript, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-93663-BackendUsersPreferredUILanguageStoredAsDBField.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-93663-BackendUsersPreferredUILanguageStoredAsDBField.rst
deleted file mode 100644
index 2e8c17557a0c..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-93663-BackendUsersPreferredUILanguageStoredAsDBField.rst
+++ /dev/null
@@ -1,55 +0,0 @@
-.. include:: ../../Includes.txt
-
-========================================================================
-Feature: #93663 - Backend Users preferred UI language stored as DB field
-========================================================================
-
-See :issue:`93663`
-
-Description
-===========
-
-In previous TYPO3 versions, Administrators could create new backend
-users and select from the list of all supported TYPO3-internal
-languages for their Backend Language (= all labels from
-XLIFF files). This information was stored in the database field
-"be_users.lang" and was only used on the first log in of a user
-into TYPO3 Backend.
-
-The backend users themselves could use the User settings module
-to change the UI language to their preferred language, based on the
-available language packs in the system.
-
-This information was then stored in the users' "uc" (user configuration),
-an arbitrary settings field.
-
-This approach - built over 18 years ago without any significant
-changes - had several downsides:
-* The database field "be_users.lang" was not really needed
-* Administrators did not see available language packs when changing
-* Administrators could only change an Editors' preferred language by switching to the user (Switch User Mode).
-* Administrators could not filter / sort editors to see what languages the users had chosen
-* Fetching the users' preferred language always meant to fetch the whole "uc" information and unpack it.
-* The preferred language was only selected if the user had logged in for the first time to initialize the "uc" values.
-
-Instead, TYPO3 now keeps the current language preference in the
-database field "be_users.lang", allowing both editors and administrators
-to access the same value for fetching this information.
-
-
-Impact
-======
-
-When the user changes their language in the user settings module,
-the database record gets updated, and it is clear where this information is
-stored. It is now the same logic when an Administrator updates the Editor's
-record via FormEngine.
-
-The value is now always filled, and if English is chosen, the value
-is set to "default" (instead of an empty value).
-
-An upgrade wizard migrates existing "uc" values into the database
-fields. The "uc" entry "user->uc[lang]" is kept in sync for
-backwards-compatibility.
-
-.. index:: Backend, JavaScript, ext:backend
diff --git a/typo3/sysext/install/Configuration/ExtensionScanner/Php/MethodCallMatcher.php b/typo3/sysext/install/Configuration/ExtensionScanner/Php/MethodCallMatcher.php
index 4bb58f1084f7..0f95392153a9 100644
--- a/typo3/sysext/install/Configuration/ExtensionScanner/Php/MethodCallMatcher.php
+++ b/typo3/sysext/install/Configuration/ExtensionScanner/Php/MethodCallMatcher.php
@@ -4792,7 +4792,7 @@ return [
         'numberOfMandatoryArguments' => 3,
         'maximumNumberOfArguments' => 3,
         'restFiles' => [
-            'Deprecation-93837-DeprecatedSpecialPropertyOfTCATypeSelect.rst'
+            'Deprecation-93837-SpecialPropertyOfTCATypeSelect.rst'
         ],
     ],
 ];
-- 
GitLab