diff --git a/typo3/sysext/core/Documentation/Changelog-10.rst b/typo3/sysext/core/Documentation/Changelog-10.rst
index 3c9837886f981612bdadbdfe3cc6c3c6f56bcc37..188a8a97189109a6d4ff4472c24eb40598f49488 100644
--- a/typo3/sysext/core/Documentation/Changelog-10.rst
+++ b/typo3/sysext/core/Documentation/Changelog-10.rst
@@ -14,3 +14,4 @@ Every change to the TYPO3 Core which might affect your site is documented here.
Changelog/10.0/Index
Changelog/10.1/Index
Changelog/10.2/Index
+ Changelog/10.3/Index
diff --git a/typo3/sysext/core/Documentation/Changelog/10.1/Feature-84250-SeparatelyEnableDisableAddMediaByURLAndSelectUploadFiles.rst b/typo3/sysext/core/Documentation/Changelog/10.1/Feature-84250-SeparatelyEnableDisableAddMediaByURLAndSelectUploadFiles.rst
index 22c15f8ed7a78354741c8591f8fed975357aa8d1..941b625afbbe1c76a4ef02105bf3e076db0dd493 100644
--- a/typo3/sysext/core/Documentation/Changelog/10.1/Feature-84250-SeparatelyEnableDisableAddMediaByURLAndSelectUploadFiles.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.1/Feature-84250-SeparatelyEnableDisableAddMediaByURLAndSelectUploadFiles.rst
@@ -18,7 +18,7 @@ If "elementBrowserType" is set to "file" both values are true by default.
Example
-.. codeblock:: php
+.. code-block:: php
$GLOBALS['TCA']['pages']['columns']['media']['config']['appearance'] = [
'fileUploadAllowed' => false,
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-89139-ConsoleCommandsConfigurationMigratedToSymfonyServiceTags.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89139-ConsoleCommandsConfigurationFormatCommandsPhp.rst
similarity index 66%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-89139-ConsoleCommandsConfigurationMigratedToSymfonyServiceTags.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89139-ConsoleCommandsConfigurationFormatCommandsPhp.rst
index 4e373e7d45d65f6d8088fb36e516370303c7eed3..29619d5561f919454039aaf3f38f1b3229873327 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-89139-ConsoleCommandsConfigurationMigratedToSymfonyServiceTags.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89139-ConsoleCommandsConfigurationFormatCommandsPhp.rst
@@ -1,8 +1,8 @@
.. include:: ../../Includes.txt
-=====================================================================================
-Deprecation: #89139 - Console Commands configuration migrated to Symfony service tags
-=====================================================================================
+========================================================================
+Deprecation: #89139 - Console Commands configuration format Commands.php
+========================================================================
See :issue:`89139`
@@ -10,8 +10,8 @@ Description
===========
The console command configuration file format :php:`Configuration/Commands.php`
-has been deprecated in favor of the dependency injection service tag
-`console.command`. The tag allows to configure dependency injection and
+has been marked as deprecated in favor of the symfony service tag
+:yaml:`console.command`. The tag allows to configure dependency injection and
command registration in one single location.
@@ -19,11 +19,11 @@ Impact
======
Providing a command configuration in :php:`Configuration/Commands.php` will
-trigger a deprecation warning when the respective commands have not already
-been defined via dependency injection service tags.
+trigger a PHP :php:`E_USER_DEPRECATED` error when the respective commands have not already
+been defined via symfony service tags.
Extensions that provide both, the deprecated configuration file and service
-tags, will not trigger a deprecation message in order to allow extensions to
+tags, will not trigger a PHP :php:`E_USER_DEPRECATED` error in order to allow extensions to
support multiple TYPO3 major versions.
@@ -38,8 +38,8 @@ service tags.
Migration
=========
-Add the `console.command` tag to command classes. Use the tag attribute `command`
-to specify the command name. The optional tag attribute `schedulable` may be set
+Add the :yaml:`console.command` tag to command classes. Use the tag attribute :yaml:`command`
+to specify the command name. The optional tag attribute :yaml:`schedulable` may be set
to false to exclude the command from the TYPO3 scheduler.
.. code-block:: yaml
@@ -57,14 +57,14 @@ to false to exclude the command from the TYPO3 scheduler.
schedulable: false
Command aliases are to be configured as separate tags.
-The optonal tag attribute `alias` should be set to true for alias commands.
+The optional tag attribute :yaml:`alias` should be set to true for alias commands.
.. code-block:: yaml
MyVendor\MyExt\Commands\BarCommand
tags:
- name: 'console.command'
- command: 'my:bar' }
+ command: 'my:bar'
- name: 'console.command'
command: 'my:old-bar-command'
alias: true
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-89463-DeprecateSwitchableControllerActions.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89463-SwitchableControllerActions.rst
similarity index 64%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-89463-DeprecateSwitchableControllerActions.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89463-SwitchableControllerActions.rst
index c95068592d36f64bc6836bc2a390507a4691c4bb..755637261da9f6027b028bed3aa3e37b45a7d53a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-89463-DeprecateSwitchableControllerActions.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89463-SwitchableControllerActions.rst
@@ -1,8 +1,8 @@
.. include:: ../../Includes.txt
-===============================================================
-Deprecation: #89463 - Deprecate `switchable controller actions`
-===============================================================
+=====================================================
+Deprecation: #89463 - `Switchable Controller Actions`
+=====================================================
See :issue:`89463`
@@ -12,41 +12,41 @@ Description
`Switchable controller actions` have been marked as deprecated and will be removed in one of the next major versions
of TYPO3, probably version 11.0 or 12.0.
-`Switchable controller actions` are used to override the allowed set of controllers and actions via typoscript or plugin
+:ts:`Switchable controller actions` are used to override the allowed set of controllers and actions via TypoScript or plugin
flexforms. While this is convenient for reusing the same plugin for a lot of different use cases, it's also very
problematic as it completely overrides the original configuration defined via
:php:`\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin`.
-`Switchable controller actions` therefore have bad implications that rectify their removal.
+:ts:`Switchable controller actions` therefore have bad implications that rectify their removal.
-First of all, `switchable controller actions` override the original configuration of plugins at runtime and possibly
+First of all, :ts:`switchable controller actions` override the original configuration of plugins at runtime and possibly
depending on conditions which contradicts the idea of :php:`\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin`
being the authoritative way to define configuration.
Using the same plugin as an entry point for many different functionalities contradicts the idea of a plugin serving one
-specific purpose. `Switchable controller actions` allow for creating one central plugin that takes care of everything.
+specific purpose. :ts:`Switchable controller actions` allow for creating one central plugin that takes care of everything.
Impact
======
-All plugins that are using `switchable controller actions` need to be split into multiple different plugins. Usually, one
-would create a new plugin for each possible `switchable controller actions` configuration entry.
+All plugins that are using :ts:`switchable controller actions` need to be split into multiple different plugins. Usually, one
+would create a new plugin for each possible :ts:`switchable controller actions` configuration entry.
Affected Installations
======================
-All installations that make use of `switchable controller actions`, either via flexform configuration of plugins or via
-typoscript configuration.
+All installations that make use of :ts:`switchable controller actions`, either via flexform configuration of plugins or via
+TypoScript configuration.
Migration
=========
-Unfortunately an automatic migration is not possible. As `switchable controller actions` allowed to override the whole
+Unfortunately, an automatic migration is not possible. As :ts:`switchable controller actions` allowed to override the whole
configuration of allowed controllers and actions, the only way to migrate is to create dedicated plugins for each former
-`switchable controller actions` configuration entry.
+:ts:`switchable controller actions` configuration entry.
Example:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-89673-DeprecateExtbasesWebRequestAndWebResponse.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89673-ExtbasesWebRequestAndWebResponse.rst
similarity index 63%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-89673-DeprecateExtbasesWebRequestAndWebResponse.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89673-ExtbasesWebRequestAndWebResponse.rst
index 6edaa947457b2f8c2ecca5b6701095b00243d8b4..357e1d38bec8cc970051d032e1b8010cc55c3637 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-89673-DeprecateExtbasesWebRequestAndWebResponse.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89673-ExtbasesWebRequestAndWebResponse.rst
@@ -1,16 +1,16 @@
.. include:: ../../Includes.txt
-====================================================================
-Deprecation: #89673 - Deprecate Extbase's WebRequest and WebResponse
-====================================================================
+==========================================================
+Deprecation: #89673 - Extbase's WebRequest and WebResponse
+==========================================================
See :issue:`89673`
Description
===========
-Both classes, :php:`\TYPO3\CMS\Extbase\Mvc\Web\Request` and :php:`\TYPO3\CMS\Extbase\Mvc\Web\Response`
-have been deprecated. Along with their deprecation, all relevant logic has been moved into their parent
+Both classes :php:`\TYPO3\CMS\Extbase\Mvc\Web\Request` and :php:`\TYPO3\CMS\Extbase\Mvc\Web\Response`
+have been marked as deprecated. Along with their deprecation, all relevant logic has been moved into their parent
classes :php:`\TYPO3\CMS\Extbase\Mvc\Request` and :php:`\TYPO3\CMS\Extbase\Mvc\Response`.
This is done to simplify the request/response handling of Extbase and to ease the transition towards
@@ -21,7 +21,7 @@ Impact
======
There is no impact yet as the "web" versions of the request and response are still used by Extbase.
-The only thing that is worth mentioning is that those who implement custom requests and/or responses,
+The only thing that is worth mentioning is that those who implement custom requests and/or responses
should derive from the non "web" versions now.
@@ -37,9 +37,9 @@ Those who don't change the request/response handling, will not realize this chan
Migration
=========
-As mentioned, all installations that implement custom request/response objects that derive from
+All installations that implement custom request/response objects that derive from
:php:`\TYPO3\CMS\Extbase\Mvc\Web\Request` and :php:`\TYPO3\CMS\Extbase\Mvc\Web\Response` should now
derive from :php:`\TYPO3\CMS\Extbase\Mvc\Request` (and override the :php:`$format` property) and
-:php:`\TYPO3\CMS\Extbase\Mvc\Response` (and override the `:php:`shutdown` method).
+:php:`\TYPO3\CMS\Extbase\Mvc\Response` (and override the :php:`shutdown` method).
.. index:: PHP-API, NotScanned, ext:extbase
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-89866-Global-TYPO3-information-related-constants.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89866-Global-TYPO3-information-related-constants.rst
similarity index 94%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-89866-Global-TYPO3-information-related-constants.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89866-Global-TYPO3-information-related-constants.rst
index 6fddc9fd281090ad1bab2537f9bf219c1e17f86a..f6148cef4f7a1dfb5e6f4a38b0190107a978ec4a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-89866-Global-TYPO3-information-related-constants.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89866-Global-TYPO3-information-related-constants.rst
@@ -10,7 +10,7 @@ Description
===========
The following global constants, which are initialized at the very
-beginning of each TYPO3-related PHP process, have been deprecated:
+beginning of each TYPO3-related PHP process, have been marked as deprecated:
* :php:`TYPO3_copyright_year`
* :php:`TYPO3_URL_GENERAL`
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-89868-RemoveReqCHashFunctionalityForPlugins.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89868-RemoveReqCHashFunctionalityForPlugins.rst
similarity index 78%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-89868-RemoveReqCHashFunctionalityForPlugins.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89868-RemoveReqCHashFunctionalityForPlugins.rst
index f0b885fef47ca85063969f9a7c356f6156a9759e..a7a25b82afe7302f39d7d468ccbc9c08d134981f 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-89868-RemoveReqCHashFunctionalityForPlugins.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89868-RemoveReqCHashFunctionalityForPlugins.rst
@@ -17,30 +17,30 @@ In Extbase plugins, this could be configured via a TypoScript feature toggle (en
:typoscript:`config.tx_extbase.features.requireCHashArgumentForActionArguments = 1`
-In Pi-based plugins the public property :php:`AbstractPlugin->pi_checkCHash`
+In Pi-based plugins the public property :php:`AbstractPlugin->pi_checkCHash`
was used to enable the cHash validation for non-cacheable plugins.
-Both plugin systems triggered the method :php:`TypoScriptFrontendController->reqCHash` which
-validated relevant GET parameters. However, the `PageArgumentValidator` PSR-15 middleware now
-always validates the cHash, so a plugin does not need to know about cHash validation anymore and
+Both plugin systems triggered the method :php:`TypoScriptFrontendController->reqCHash` which
+validated relevant GET parameters. However, the :php:`PageArgumentValidator` PSR-15 middleware now
+always validates the cHash, so a plugin does not need to know about cHash validation anymore and
therefor does not need to set the option.
This means the options are not needed anymore, as the validation already happens during the Frontend
request handling process. The options are removed.
-In addition, the method :php:`TypoScriptFrontendController->reqCHash()` is marked as deprecated and
-not in use anymore.
+In addition, the method :php:`TypoScriptFrontendController->reqCHash()` has been marked as deprecated and
+is not in use anymore.
Impact
======
-Setting the options in Extbase or Pi-Base have no effect anymore.
+Setting the option in Extbase or Pi-Base has no effect anymore.
Calling the PHP method :php:`TypoScriptFrontendController->reqCHash()`
-will trigger a deprecation warning.
+will trigger a PHP :php:`E_USER_DEPRECATED` error.
-Internal classes such as the `CacheHashEnforcer` are removed.
+Internal classes such as the :php:`CacheHashEnforcer` are removed.
Affected Installations
@@ -55,7 +55,7 @@ Migration
Remove the options / flags as they have no effect in TYPO3 v10 anymore.
-Calling the method directly is also not needed, as the PageArgumentValidator is executing this
+Calling the method directly is also not needed, as the PageArgumentValidator is executing this
validation now at every request.
.. index:: Frontend, PartiallyScanned, ext:frontend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-89870-NewPSR-14EventsForExtbase-relatedSignals.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89870-NewPSR-14EventsForExtbase-relatedSignals.rst
similarity index 93%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-89870-NewPSR-14EventsForExtbase-relatedSignals.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89870-NewPSR-14EventsForExtbase-relatedSignals.rst
index c78dad3c82b4df84f9042b0fb44ee2e0dbefd136..81a8d12b97fd9c6343b59f126498cd6afc318119 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-89870-NewPSR-14EventsForExtbase-relatedSignals.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-89870-NewPSR-14EventsForExtbase-relatedSignals.rst
@@ -22,16 +22,16 @@ The following signals have been marked as deprecated in favor of new PSR-14 even
- :php:`TYPO3\CMS\Extbase\Persistence\Generic\Backend::afterRemoveObject`
The method :php:`emitBeforeCallActionMethodSignal` in :php:`ActionController`
-has been deprecated and is not called by Extbase itself anymore.
+has been marked as deprecated and is not called by Extbase itself anymore.
Impact
======
Using any of the signals will still work as expected, but will trigger
-a deprecation warning.
+a PHP :php:`E_USER_DEPRECATED` error.
Calling the method :php:`emitBeforeCallActionMethodSignal` will trigger a
-deprecation warning.
+PHP :php:`E_USER_DEPRECATED` error.
Affected Installations
======================
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90007-GlobalConstantsTYPO3_versionAndTYPO3_branch.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90007-GlobalConstantsTYPO3_versionAndTYPO3_branch.rst
similarity index 80%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-90007-GlobalConstantsTYPO3_versionAndTYPO3_branch.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90007-GlobalConstantsTYPO3_versionAndTYPO3_branch.rst
index 1a609be35de7ac2ff02ead945b27fc0ab0f1c70e..b9b87e74ff7997c48955a1007d481682f2fadee0 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90007-GlobalConstantsTYPO3_versionAndTYPO3_branch.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90007-GlobalConstantsTYPO3_versionAndTYPO3_branch.rst
@@ -9,7 +9,7 @@ See :issue:`90007`
Description
===========
-Two of the most "stable" global constants in the TYPO3 Core - `TYPO3_version` and `TYPO3_branch` have been marked as deprecated.
+Two of the most "stable" global constants in the TYPO3 Core - :php:`TYPO3_version` and :php:`TYPO3_branch` have been marked as deprecated.
The change was mainly driven by the necessity to minimize runtime-generated constants in order to optimize performance, also for op-caching.
@@ -20,7 +20,7 @@ the constants for backwards-compatibility reasons.
Impact
======
-No :php:`E_USER_DEPRECATED` error is triggered, however the constants will work during
+No PHP :php:`E_USER_DEPRECATED` error is triggered, however the constants will work during
TYPO3 v10, and be removed with TYPO3 v11.
@@ -40,4 +40,4 @@ the constants, as they will removed.
Check the Extension Scanner in the Upgrade section of TYPO3 to see
if any extensions you use might be affected.
-.. index:: PHP-API, FullyScanned, ext:core
\ No newline at end of file
+.. index:: PHP-API, FullyScanned, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90019-PagePermissionLogicByDataHandler.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90019-PagePermissionLogicByDataHandler.rst
new file mode 100644
index 0000000000000000000000000000000000000000..e0d6c48df0855ab8da82b806a8e22252ba96e3b6
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90019-PagePermissionLogicByDataHandler.rst
@@ -0,0 +1,45 @@
+.. include:: ../../Includes.txt
+
+==========================================================
+Deprecation: #90019 - Page permission logic by DataHandler
+==========================================================
+
+See :issue:`90019`
+
+Description
+===========
+
+A new :php:`PagePermissionAssembler` class builds the page permissions, allowing to thin out certain parts of :php:`DataHandlers` responsibilities.
+
+The following properties and methods within :php:`DataHandler` have been marked as deprecated:
+
+* :php:`TYPO3\CMS\Core\DataHandling\DataHandler->defaultPermissions`
+* :php:`TYPO3\CMS\Core\DataHandling\DataHandler->pMap`
+* :php:`TYPO3\CMS\Core\DataHandling\DataHandler->setTSconfigPermissions()`
+* :php:`TYPO3\CMS\Core\DataHandling\DataHandler->assemblePermissions()`
+
+The following methods should only be called with integers as permission argument:
+
+* :php:`TYPO3\CMS\Core\DataHandling\DataHandler->doesRecordExist()`
+* :php:`TYPO3\CMS\Core\DataHandling\DataHandler->recordInfoWithPermissionCheck()`
+
+
+Impact
+======
+
+Calling the mentioned methods will trigger a PHP :php:`E_USER_DEPRECATED` error and will be removed in TYPO3 v11.0.
+
+
+Affected Installations
+======================
+
+Any TYPO3 installation that enriches page permission handling and directly accesses the methods or properties in :php:`DataHandler`.
+
+
+Migration
+=========
+
+Ensure to use the new :php:`PagePermissionAssembler` PHP class
+which serves as a proper API for creating page permissions.
+
+.. index:: PHP-API, PartiallyScanned, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90249-PackageRelatedSignalSlotsMigratedToPSR-14Events.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90249-PackageRelatedSignalSlotsMigratedToPSR-14Events.rst
new file mode 100644
index 0000000000000000000000000000000000000000..d087f7548cc9836df562d14da1ebf9a68bb356cb
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90249-PackageRelatedSignalSlotsMigratedToPSR-14Events.rst
@@ -0,0 +1,51 @@
+.. include:: ../../Includes.txt
+
+============================================================================
+Deprecation: #90249 - Package related Signal Slots migrated to PSR-14 events
+============================================================================
+
+See :issue:`90249`
+
+Description
+===========
+
+The following Signal Slots have been replaced by new PSR-14 events
+which can be used as 1:1 equivalents:
+
+* :php:`PackageManagement::packagesMayHaveChanged`
+* :php:`TYPO3\CMS\Extensionmanager\Utility\InstallUtility::afterExtensionInstall`
+* :php:`TYPO3\CMS\Extensionmanager\Utility\InstallUtility::afterExtensionUninstall`
+* :php:`TYPO3\CMS\Extensionmanager\Utility\InstallUtility::afterExtensionT3DImport`
+* :php:`TYPO3\CMS\Extensionmanager\Utility\InstallUtility::afterExtensionStaticSqlImport`
+* :php:`TYPO3\CMS\Extensionmanager\Utility\InstallUtility::afterExtensionFileImport`
+* :php:`TYPO3\CMS\Extensionmanager\Service\ExtensionManagementService::willInstallExtensions`
+* :php:`TYPO3\CMS\Extensionmanager\ViewHelper\ProcessAvailableActionsViewHelper::processActions`
+
+
+Impact
+======
+
+Using the mentioned signals will trigger a PHP :php:`E_USER_DEPRECATED` error.
+
+
+Affected Installations
+======================
+
+TYPO3 installations with custom extensions using these signals.
+
+
+Migration
+=========
+
+Use the new PSR-14 alternatives:
+
+* :php:`TYPO3\CMS\Core\Package\Event\PackagesMayHaveChangedEvent`
+* :php:`TYPO3\CMS\Core\Package\Event\AfterPackageActivationEvent`
+* :php:`TYPO3\CMS\Core\Package\Event\AfterPackageDeactivationEvent`
+* :php:`TYPO3\CMS\Core\Package\Event\BeforePackageActivationEvent`
+* :php:`TYPO3\CMS\Extensionmanager\Event\AfterExtensionDatabaseContentHasBeenImportedEvent`
+* :php:`TYPO3\CMS\Extensionmanager\Event\AfterExtensionStaticDatabaseContentHasBeenImportedEvent`
+* :php:`TYPO3\CMS\Extensionmanager\Event\AfterExtensionFilesHaveBeenImportedEvent`
+* :php:`TYPO3\CMS\Extensionmanager\Event\AvailableActionsForExtensionEvent`
+
+.. index:: PHP-API, FullyScanned, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90258-SimplifiedRTEParserAPI.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90258-SimplifiedRTEParserAPI.rst
similarity index 51%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-90258-SimplifiedRTEParserAPI.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90258-SimplifiedRTEParserAPI.rst
index f760b9c5be4a3731f1570ac1ecf1e2386186be06..7ef3958744c69a683d93d79b82e1611a1e21c45e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90258-SimplifiedRTEParserAPI.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90258-SimplifiedRTEParserAPI.rst
@@ -9,17 +9,19 @@ See :issue:`90258`
Description
===========
-The PHP class `RteHtmlParser` which is used to transform RTE-based
-textarea fields from the database to the configured Rich Text Editor, and back, has a new simplified API. For this reason,
-the two methods :php:`TYPO3\CMS\Core\Html\RteHtmlParser->init()` and
-:php:`TYPO3\CMS\Core\Html\RteHtmlParser->RTE_transform()` have been
-deprecated.
+The PHP class :php:`RteHtmlParser` which is used to transform RTE-based
+textarea fields from the database to the configured Rich Text Editor, and back, has a new simplified API.
+
+For this reason, the following two methods have been marked as deprecated:
+
+* :php:`TYPO3\CMS\Core\Html\RteHtmlParser->init()`
+* :php:`TYPO3\CMS\Core\Html\RteHtmlParser->RTE_transform()`
Impact
======
-Calling any of the methods will trigger a PHP deprecation warning.
+Calling any of the methods will trigger a PHP :php:`E_USER_DEPRECATED` error.
Affected Installations
@@ -32,16 +34,16 @@ the methods.
Migration
=========
-The PHP method `init()` can be removed without substitution, as it
+The method :php:`TYPO3\CMS\Core\Html\RteHtmlParser->init()` can be removed without substitution, as it
serves no purpose anymore.
-The PHP method `RTE_transform()` now has two methods as substitute,
+The method :php:`TYPO3\CMS\Core\Html\RteHtmlParser->RTE_transform()` now has two methods as substitute,
depending on the direction which is necessary. This was previously
done in the third method argument ("rte" and "db"):
- :php:`transformTextForRichTextEditor($content, $configuration)`
- :php:`transformTextForPersistence($content, $configuration)`
-The second argument `$configuration` is now the `processing` configuration (`proc`) of the RTE configuration.
+The second argument :php:`$configuration` is now the `processing` configuration (`proc`) of the RTE configuration.
-.. index:: RTE, FullyScanned, ext:core
\ No newline at end of file
+.. index:: RTE, FullyScanned, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90260-ResourceFactorygetInstancePseudo-factory.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90260-ResourceFactorygetInstancePseudo-factory.rst
similarity index 69%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-90260-ResourceFactorygetInstancePseudo-factory.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90260-ResourceFactorygetInstancePseudo-factory.rst
index a49d111fee1dff6df75d102e9a217f132288a2ad..cd3d2df78b4dcd7a4f5e5f642429eb7d5d3e9624 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90260-ResourceFactorygetInstancePseudo-factory.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90260-ResourceFactorygetInstancePseudo-factory.rst
@@ -13,30 +13,30 @@ The method :php:`ResourceFactory::getInstance()` acts as a wrapper
for the constructor which originally was meant as a performance
improvement as pseudo-singleton concept in TYPO3 v4.7.
-However, ResourceFactory was never optimized and now with Dependency
-Injection, ResourceFactory can be used directly.
+However, :php:`ResourceFactory` was never optimized and now with Dependency
+Injection, :php:`ResourceFactory` can be used directly.
-Therefore the method is marked as deprecated.
+Therefore the method has been marked as deprecated.
Impact
======
-Calling :php:`ResourceFactory::getInstance()` will trigger a PHP deprecation warning.
+Calling :php:`ResourceFactory::getInstance()` will trigger a PHP :php:`E_USER_DEPRECATED` error.
Affected Installations
======================
-Any TYPO3 installation with custom PHP code calling this method.
+Any TYPO3 installation with custom PHP code calling the method.
Migration
=========
-Check TYPO3's "Extension Scanner" in the Install Tool if you're affected and replace this with constructor injection via Dependency
+Check TYPO3's "Extension Scanner" in the Install Tool if you're affected and replace with constructor injection via Dependency
Injection if possible, or use :php:`GeneralUtility::makeInstance(ResourceFactory::class)` instead.
The latter can already applied in earlier versions (TYPO3 v7 or higher) to ease optimal migration of this deprecation.
-.. index:: FAL, PHP-API, FullyScanned, ext:core
\ No newline at end of file
+.. index:: FAL, PHP-API, FullyScanned, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90348-PageLayoutViewClass.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90348-PageLayoutViewClass.rst
new file mode 100644
index 0000000000000000000000000000000000000000..8f40d1743a4c026b8533d7aa0a1928ceffa7f206
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90348-PageLayoutViewClass.rst
@@ -0,0 +1,40 @@
+.. include:: ../../Includes.txt
+
+==========================================
+Deprecation: #90348 - PageLayoutView class
+==========================================
+
+See :issue:`90348`
+
+Description
+===========
+
+The :php:`PageLayoutView` class, which is considered internal API, has been marked as deprecated in favor
+of the new Fluid-based alternative which renders the "page" BE module.
+
+
+Impact
+======
+
+Implementations which depend on :php:`PageLayoutView` should prepare to use the alternative implementation (by overlaying and overriding Fluid templates of EXT:backend).
+
+
+Affected Installations
+======================
+
+* Any site which overrides the :php:`PageLayoutView` class. The overridden class will
+ still be instantiated when rendering previews in BE page module - but no methods
+ will be called on the instance **unless** they are called by a third party hook subscriber.
+* Any site which depends on PSR-14 events associated with :php:`PageLayoutView` will only
+ have those events dispatched if the :php:`fluidBasedPageModule` feature flag is :php:`false`.
+ * Affects :php:`\TYPO3\CMS\Backend\View\Event\AfterSectionMarkupGeneratedEvent`.
+ * Affects :php:`\TYPO3\CMS\Backend\View\Event\BeforeSectionMarkupGeneratedEvent`.
+
+
+Migration
+=========
+
+Fluid templates can be extended or replaced to render custom header, footer or preview of
+a given :ts:`CType`, see feature description for feature :issue:`90348`.
+
+.. index:: Backend, Fluid, NotScanned, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90390-DeprecateBrokenLinkRepositorygetNumberOfBrokenLinksInLinkvalidator.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90390-BrokenLinkRepositorygetNumberOfBrokenLinksInLinkvalidator.rst
similarity index 55%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-90390-DeprecateBrokenLinkRepositorygetNumberOfBrokenLinksInLinkvalidator.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90390-BrokenLinkRepositorygetNumberOfBrokenLinksInLinkvalidator.rst
index 0ff9a36f8493f08bcab68675ce643d3cce6394b9..c0d395b157f23a0b7c33f48889c5ada642ca0455 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90390-DeprecateBrokenLinkRepositorygetNumberOfBrokenLinksInLinkvalidator.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90390-BrokenLinkRepositorygetNumberOfBrokenLinksInLinkvalidator.rst
@@ -1,29 +1,27 @@
.. include:: ../../Includes.txt
-===============================================================================================
-Deprecation: #90390 - Deprecate BrokenLinkRepository::getNumberOfBrokenLinks() in linkvalidator
-===============================================================================================
+=====================================================================================
+Deprecation: #90390 - BrokenLinkRepository::getNumberOfBrokenLinks() in linkvalidator
+=====================================================================================
See :issue:`90390`
Description
===========
-The method :php:`BrokenLinkRepository::getNumberOfBrokenLinks()` is deprecated.
+The method :php:`BrokenLinkRepository::getNumberOfBrokenLinks()` has been marked as deprecated.
Impact
======
-If third party extensions use this function, a `E_USER_DEPRECATED`
-is triggered.
+Usage of the method triggers a PHP :php:`E_USER_DEPRECATED` error.
Affected Installations
======================
-This only affects third party extensions which use this function. The
-deprecated function is no longer used in the core.
+Every TYPO3 installation that uses the method.
Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90421-DocumentTemplate.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90421-DocumentTemplate.rst
similarity index 68%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-90421-DocumentTemplate.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90421-DocumentTemplate.rst
index a7f5115e5358432dde68c955364eb421e288957a..0b9d33bc2147db19471ade2abe8e8ae629e9c0de 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90421-DocumentTemplate.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90421-DocumentTemplate.rst
@@ -14,19 +14,20 @@ also available as :php:`$GLOBALS['TBE_TEMPLATE']` until TYPO3 v10.0
served as a basis to render backend modules or HTML-based output
in TYPO3 Backend.
-Since TYPO3 v7, the new API via `ModuleTemplate` can be used instead. The DocumentTemplate class has been marked as deprecated.
+Since TYPO3 v7, the new API via php:`ModuleTemplate` can be used instead. The :php:`DocumentTemplate` class has been marked as deprecated.
Impact
======
-Instantiating the DocumentTemplate class will trigger a PHP deprecation warning.
+Instantiating the :php:`DocumentTemplate` class will trigger a PHP :php:`E_USER_DEPRECATED` error.
Affected Installations
======================
-TYPO3 installations with third-party extensions adding backend modules using the DocumentTemplate API. These can typically be identified by extensions that "worked" but somehow looked ugly since TYPO3 v7 due to CSS and HTML changes.
+TYPO3 installations with third-party extensions adding backend modules using the DocumentTemplate API.
+These can typically be identified by extensions that "worked" but somehow looked ugly since TYPO3 v7 due to CSS and HTML changes.
Migration
@@ -42,4 +43,4 @@ Use ModuleTemplate API instead, which can be built like this in a typical non-Ex
$moduleTemplate->setContent($content);
return new HtmlResponse($moduleTemplate->renderContent());
-.. index:: Backend, PHP-API, FullyScanned, ext:backend
\ No newline at end of file
+.. index:: Backend, PHP-API, FullyScanned, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90522-TSFEPropertiesRegardingImages.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90522-TSFEPropertiesRegardingImages.rst
similarity index 91%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-90522-TSFEPropertiesRegardingImages.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90522-TSFEPropertiesRegardingImages.rst
index b754b05bafd103819a114e09b86380e899295b2e..30ddfb3b9d5a9e9f916e5bf0ded3a5f6d09548be 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90522-TSFEPropertiesRegardingImages.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Deprecation-90522-TSFEPropertiesRegardingImages.rst
@@ -15,7 +15,7 @@ The image related properties :php:`$imagesOnPage` and :php:`$lastImageInfo` of
Impact
======
-Calling these deprecated properties will trigger a deprecation notice.
+Calling these properties will trigger a PHP :php:`E_USER_DEPRECATED` error.
Affected Installations
======================
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-78347-AddStdWrapPropertiesToFilesProcessor.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-78347-AddStdWrapPropertiesToFilesProcessor.rst
similarity index 89%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-78347-AddStdWrapPropertiesToFilesProcessor.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-78347-AddStdWrapPropertiesToFilesProcessor.rst
index 5cf28d2dea9920dd73db878b6de679ca8de612b7..be959cb20ff9b8910f89af13b7290b87d186d6df 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-78347-AddStdWrapPropertiesToFilesProcessor.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-78347-AddStdWrapPropertiesToFilesProcessor.rst
@@ -9,7 +9,7 @@ See :issue:`78347`
Description
===========
-Add stdWrap properties to FLUIDTEMPLATEs FilesProcessor as it is possible in FilesContentObject, too.
+StdWrap properties have been added to FLUIDTEMPLATEs FilesProcessor the same way as in FilesContentObject.
That way you can implement slide-functionality on rootline for file resources.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-78450-IntroducePreviewRendererPattern.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-78450-IntroducePreviewRendererPattern.rst
similarity index 52%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-78450-IntroducePreviewRendererPattern.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-78450-IntroducePreviewRendererPattern.rst
index 8d768c394b1a310a02237f672e8282cbfc46de05..dc6670c246be39f9da15eb5e8a05b25b7097bcf2 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-78450-IntroducePreviewRendererPattern.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-78450-IntroducePreviewRendererPattern.rst
@@ -9,11 +9,11 @@ See :issue:`78450`
Pre-requisites
==============
-The PreviewRenderer usage is only active if the "fluid based page layout module" feature is enabled. This feature
-is enabled by default in TYPO3 versions 10.3 and later.
+The :php:`PreviewRenderer` usage is only active if the "fluid based page layout module" feature is enabled. This feature
+is activated by default in TYPO3 versions 10.3 and later.
The feature toggle can be located in the `Settings` admin module under `Feature Toggles`. Or it can be set in
-PHP using :php:``$GLOBALS['TYPO3_CONF_VARS']['SYS']['features']['fluidBasedPageModule'] = true;``.
+PHP using :php:`$GLOBALS['TYPO3_CONF_VARS']['SYS']['features']['fluidBasedPageModule'] = true;`.
Description
@@ -29,14 +29,14 @@ as the rendering logic (which now renders both the actual preview and has contra
The main differences between the old and the new approach are:
-* The class used to render previews is now defined in TCA and can be defined per-type or for any type.
+* The class used to render previews is now defined in :php:`TCA` and can be defined per-type or for any type.
* The resolver used to find preview renderers is a global implementation overridable in configuration.
-* A single preview renderer will now be used; before, hook subscribers had to toggle passed-by-reference flags.
-* Wrapping is no longer forced to be a `<span>` tag so you are not restricted to inline and inline-block display.
+* A single preview renderer will now be used. Before, hook subscribers had to toggle passed-by-reference flags.
+* Wrapping is no longer forced to be a :html:`<span>` tag so you are not restricted to inline and inline-block display.
* Preview renderers have a public contract which splits up actual preview and wrapping, allowing third party renderers
to subclass the original renderer and for example only change the wrapping tag.
-* Preview rendering can now be done ad-hoc through; the pattern can be used from any context where the old pattern
- could only be used (was only used) in the PageLayoutView for content previews.
+* Preview rendering can now be done ad-hoc. The pattern can be used from any context where the old pattern
+ could only be used (was only used) in the :php:`PageLayoutView` for content previews.
Impact
@@ -44,8 +44,8 @@ Impact
The feature adds two new concepts:
-* `PreviewRendererResolver` which is a global implementation to detect which `PreviewRenderer` a given record needs.
-* `PreviewRenderer` which is the class responsible for generating the preview and the wrapping.
+* :php:`PreviewRendererResolver` which is a global implementation to detect which :php:`PreviewRenderer` a given record needs.
+* :php:`PreviewRenderer` which is the class responsible for generating the preview and the wrapping.
Configuring the implementation
@@ -58,18 +58,18 @@ The PreviewRendererResolver can be overridden by setting:
$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['backend']['previewRendererResolver'] = \TYPO3\CMS\Backend\Preview\StandardPreviewRendererResolver::class;
-(the class shown is the standard implementation TYPO3 provides, inspect this class for further developer information)
+The class shown is the standard implementation TYPO3 provides. Inspect this class for further developer information.
-Once overridden the old resolver will no longer be consulted.
+Once overridden, the old resolver will no longer be consulted.
-And individual preview renderers can be defined using one of the following two approaches:
+Individual preview renderers can be defined by using one of the following two approaches:
.. code-block:: php
$GLOBALS['TCA'][$table]['ctrl']['previewRenderer'] = My\PreviewRenderer::class;
-Which specifies the PreviewRenderer to use for any record in `$table`
+This specifies the PreviewRenderer to be used for any record in :php:`$table`.
Or if your table has a "type" field/attribute:
@@ -77,38 +77,40 @@ Or if your table has a "type" field/attribute:
$GLOBALS['TCA'][$table]['types'][$type]['previewRenderer'] = My\PreviewRenderer::class;
-Which specifies the PreviewRenderer for only records of type `$type` as determined by the type field of your table.
+This specifies the PreviewRenderer only for records of type :php:`$type` as determined by the type field of your table.
-Or finally, if your table and field has a `subtype_value_field` TCA setting (like `tt_content.list_type` for example)
-and you want register a preview renderer that applies only when that value is selected (e.g. when a certain plugin type
+Or finally, if your table and field have a :php:`subtype_value_field` TCA setting (like :php:`tt_content.list_type` for example)
+and you want to register a preview renderer that applies only when that value is selected (e.g. when a certain plugin type
is selected and you can't match it with the "type" of the record alone):
.. code-block:: php
$GLOBALS['TCA'][$table]['types'][$type]['previewRenderer'][$subType] = My\PreviewRenderer::class;
-Where `$type` is for example `list` (indicating a plugin) and `$subType` is the value of the `list_type` field when the
-type of plugin you want to target, is selected as plugin type.
+Where :php:`$type` is for example :php:`list` (indicating a plugin) and :php:`$subType` is the value of the :php:`list_type` field when the
+type of plugin you want to target is selected as plugin type.
-Note: recommended location is in the `ctrl` array in your extension's `Configuration/TCA/$table.php` or
-`Configuration/TCA/Overrides/$table.php` file. The former is used when your extension is the one that creates the table -
-the latter is used when you need to override TCA properties of tables added by the core or other extensions.
+.. note::
+ The recommended location is in the :php:`ctrl` array in your extension's :file:`Configuration/TCA/$table.php` or
+ :file:`Configuration/TCA/Overrides/$table.php` file. The former is used when your extension is the one that creates the table,
+ the latter is used when you need to override TCA properties of tables added by the core or other extensions.
The PreviewRenderer interface
-----------------------------
-`\TYPO3\CMS\Backend\Preview\PreviewRendererResolverInterface` must be implemented by PreviewRendererResolvers and
-contains a single API method, `public function resolveRendererFor($table, array $row, int $pageUid);` which
-unsurprisingly returns a single PreviewRenderer based on the given input.
+:php:`\TYPO3\CMS\Backend\Preview\PreviewRendererResolverInterface` must be implemented by :php:`PreviewRendererResolvers` and
+contains a single API method, :php:`public function resolveRendererFor($table, array $row, int $pageUid);` which
+unsurprisingly returns a single :php:`PreviewRenderer` based on the given input.
-`\TYPO3\CMS\Backend\Preview\PreviewRendererInterface` must be implemented by any PreviewRenderer and contains a few
+:php:`\TYPO3\CMS\Backend\Preview\PreviewRendererInterface` must be implemented by any :php:`PreviewRenderer` and contains some
API methods:
.. code-block:: php
+
/**
* Dedicated method for rendering preview header HTML for
- * the page module only. Receives $item which is an instance
+ * the page module only. Receives $item which is an instance of
* GridColumnItem which has a getter method to return the record.
*
* @param GridColumnItem
@@ -144,15 +146,15 @@ API methods:
*/
public function wrapPageModulePreview($previewHeader, $previewContent, GridColumnItem $item);
-With further methods expected to be added to support generic preview rendering, e.g. usages outside PageLayoutView.
+Further methods are expected to be added to support generic preview rendering, e.g. usages outside PageLayoutView.
Implementing these methods allows you to control the exact composition of the preview.
-This means assuming your PreviewRenderer returns `<h4>Header</h4>` from the header render method and `<p>Body</p>` from
-the preview content rendering method and your wrapping method does `return '<div>' . $previewHeader . $previewContent . '</div>';` then the
-entire output becomes `<div><h4>Header</h4><p>Body</p></div>` when combined.
+This means assuming your :php:`PreviewRenderer` returns :html:`<h4>Header</h4>` from the header render method and :html:`<p>Body</p>` from
+the preview content rendering method and your wrapping method does :php:`return '<div>' . $previewHeader . $previewContent . '</div>';` then the
+entire output becomes :html:`<div><h4>Header</h4><p>Body</p></div>` when combined.
Should you wish to reuse parts of the default preview rendering and only change, for example, the method that renders
-the preview body content, you can subclass ``\TYPO3\CMS\Backend\Preview\StandardContentPreviewRenderer`` in your
-own PreviewRenderer class - and selectively override the methods from the API displayed above.
+the preview body content, you can subclass :php:`\TYPO3\CMS\Backend\Preview\StandardContentPreviewRenderer` in your
+own :php:`PreviewRenderer` class - and selectively override the methods from the API displayed above.
.. index:: Backend, TCA
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79310-AddOptionsAndClipboardToFilelistSearch.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-79310-AddOptionsAndClipboardToFilelistSearch.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79310-AddOptionsAndClipboardToFilelistSearch.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-79310-AddOptionsAndClipboardToFilelistSearch.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-82062-ProgressForReferenceIndexUpdateOnCLI.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-82062-ProgressForReferenceIndexUpdateOnCLI.rst
similarity index 69%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-82062-ProgressForReferenceIndexUpdateOnCLI.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-82062-ProgressForReferenceIndexUpdateOnCLI.rst
index 7f4b573b522c0ddee3be279008f501213a819f9c..4f42e6671ad3599b552bbce592762090f50a291e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-82062-ProgressForReferenceIndexUpdateOnCLI.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-82062-ProgressForReferenceIndexUpdateOnCLI.rst
@@ -17,6 +17,6 @@ status.
Impact
======
-Calling :php:`./typo3/sysext/core/bin/typo3 referenceindex:update -c` shows the new output when running the reference update (`-c` is for checking only).
+Calling `./typo3/sysext/core/bin/typo3 referenceindex:update -c` shows the new output when running the reference update (`-c` is for checking only).
-.. index:: CLI, ext:lowlevel
\ No newline at end of file
+.. index:: CLI, ext:lowlevel
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-83847-RemoveRepairedLinksFromLinkvalidatorListAfterEditing.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-83847-RemoveRepairedLinksFromLinkvalidatorListAfterEditing.rst
similarity index 92%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-83847-RemoveRepairedLinksFromLinkvalidatorListAfterEditing.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-83847-RemoveRepairedLinksFromLinkvalidatorListAfterEditing.rst
index 0f25081322039f4e79aa716577cfc7668735c8e6..bb0c14036a17ca57766fe53ae1a31260fd94932d 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-83847-RemoveRepairedLinksFromLinkvalidatorListAfterEditing.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-83847-RemoveRepairedLinksFromLinkvalidatorListAfterEditing.rst
@@ -12,7 +12,7 @@ Description
In the list of broken links provided by Linkvalidator, it is possible to click
on the edit icon for a broken link in order to edit the record directly.
-If the record was edited, the list of broken links may no longer be correct.
+If the record was edited, the list of broken links may no longer be up to date.
There are now 2 possibilities, depending on how :ref:`actionAfterEditRecord <actionAfterEditRecord>`
is configured:
@@ -25,7 +25,7 @@ recheck (default):
setNeedsRecheck:
The entries in the list are marked as needing a recheck
-Prior to this feature, fixed broken links were not removed which made fixing
+Prior to this feature, fixed broken links were not removed from the list, which made fixing
several links at a time confusing and tedious because you either had to
remember which links were already fixed or switch back and forth between
the *Report* and the *Check Links* tab to recheck for broken links.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-84214-AddCheckIfFieldsAreEditableForLinkvalidator.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-84214-AddCheckIfFieldsAreEditableForLinkvalidator.rst
similarity index 78%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-84214-AddCheckIfFieldsAreEditableForLinkvalidator.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-84214-AddCheckIfFieldsAreEditableForLinkvalidator.rst
index b8386ce16e974949e7e88cd91fce7ae576c19ce7..0944ec393b64393b45ce9f84d97e166935f06746 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-84214-AddCheckIfFieldsAreEditableForLinkvalidator.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-84214-AddCheckIfFieldsAreEditableForLinkvalidator.rst
@@ -18,13 +18,14 @@ Whether the editor has access depends on a number of factors.
We check the following:
-* The current permissions of the page. For editing the page, the editor must have Permission::PAGE_EDIT, for editing content Permission::CONTENT_EDIT must be available
+* The current permissions of the page. For editing the page, the editor must have
+ Permission::PAGE_EDIT, for editing content Permission::CONTENT_EDIT must be available.
* The user has write access to the table. We check if the table
- is in 'tables_modify' for the group(s)
+ is in 'tables_modify' for the group(s).
* The user has write access to the field. We check if the field
is an exclude field. If yes, it must be included in
'non_exclude_fields' for the group(s).
-* The user has write permission for the language of the record
+* The user has write permission for the language of the record.
* For tt_content: The CType is in list of explicitly allowed
values for authMode.
@@ -33,10 +34,10 @@ Impact
* Broken links for fields that are not editable for the current backend
user will no longer be shown.
-* Fields were added to the tx_linkvalidator_link table. "Analyze
+* Fields were added to the :sql:`tx_linkvalidator_link` table. "Analyze
Database Structure" must be executed.
* After an update to the new version, checking of broken links should
- be reinitiated for the entire site. Until this is done, some broken
+ be reinitialized for the entire site. Until this is done, some broken
links may not be displayed for editors in the broken link report.
.. index:: Backend, ext:linkvalidator
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-86614-AddHookBeforeRenderingHrefLang.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-86614-AddHookBeforeRenderingHrefLang.rst
similarity index 98%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-86614-AddHookBeforeRenderingHrefLang.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-86614-AddHookBeforeRenderingHrefLang.rst
index 8366ab2fab193cc294954f1b30246ba48accd383..568104673a2f8e53fb5d1d2f639d4262730d7e88 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-86614-AddHookBeforeRenderingHrefLang.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-86614-AddHookBeforeRenderingHrefLang.rst
@@ -68,4 +68,4 @@ executed after or before the given identifiers.
}
}
-.. index:: ext:seo, PHP-API, NotScanned
+.. index:: ext:seo, PHP-API
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-87072-AddedConfigurationOptionsForLockingAddedConfigurationOptionsForLocking.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-87072-AddedConfigurationOptionsForLockingAddedConfigurationOptionsForLocking.rst
similarity index 78%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-87072-AddedConfigurationOptionsForLockingAddedConfigurationOptionsForLocking.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-87072-AddedConfigurationOptionsForLockingAddedConfigurationOptionsForLocking.rst
index 557eefc0f10364c2a81c92cb9b452208cefbe5ec..261aa17c6026b51e6c7373d6329dbe1a7f38f4a1 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-87072-AddedConfigurationOptionsForLockingAddedConfigurationOptionsForLocking.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-87072-AddedConfigurationOptionsForLockingAddedConfigurationOptionsForLocking.rst
@@ -10,7 +10,7 @@ Description
===========
With change `Feature: #47712 - New Locking API
-<https://docs.typo3.org/typo3cms/extensions/core/latest/Changelog/7.2/Feature-47712-NewLockingAPI.html>`__ a new Locking API was introduced.
+<https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/7.2/Feature-47712-NewLockingAPI.html>`__ a new Locking API was introduced.
This API can be extended. It provides three locking strategies and an interface for adding your own locking strategy in an extension.
However, until now, the default behaviour could not be changed using only the TYPO3 core.
@@ -22,23 +22,19 @@ The introduction of new options makes some of the default properties of the lock
Configuration example
---------------------
-typo3conf/AdditionalConfiguration.php::
+:file:`typo3conf/AdditionalConfiguration.php`:
- <?php
-
- if (!defined('TYPO3_MODE')) {
- die('Access denied.');
- }
+.. code-block:: php
$GLOBALS['TYPO3_CONF_VARS']['SYS']['locking']['strategies'][\TYPO3\CMS\Core\Locking\FileLockStrategy::class]['priority'] = 10;
// The directory specified here must exist und must be a subdirectory of `Environment::getProjectPath()`
$GLOBALS['TYPO3_CONF_VARS']['SYS']['locking']['strategies'][\TYPO3\CMS\Core\Locking\FileLockStrategy::class]['lockFileDir'] = 'mylockdir';
-This sets the priority of FileLockStrategy to 10, thus making it the locking strategy with the least priority, which
+This sets the priority of FileLockStrategy to 10, thus making it the locking strategy with the lowest priority, which
will be chosen last by the LockFactory.
-The directory for storing the locks is changed to `mylockdir`.
+The directory for storing the locks is changed to :file:`mylockdir`.
Impact
======
@@ -48,9 +44,9 @@ For administrators
Nothing changes by default. The default values are used for the Locking API, same as before this change.
-If AdditionalConfiguration.php is used to change Global Configuration settings for Locking API, and not used with care,
+If :file:`AdditionalConfiguration.php` is used to change Global Configuration settings for Locking API, and not used with care,
it can seriously compromise the stability of the system. As usual, when overriding Global Configuration with
-LocalConfiguration.php or AdditionalConfiguration.php, great caution must be used.
+:file:`LocalConfiguration.php` or :file:`AdditionalConfiguration.php`, great caution must be exercised.
Specifically, do the following:
@@ -62,7 +58,9 @@ For developers
--------------
If a locking strategy is added by an extension, the priority and possibly directory for storing locks should be made
-configurable as well::
+configurable as well.
+
+.. code-block:: php
public static function getPriority()
{
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-59452-MultipleTasksInSchedulerCommand.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-87451-SchedulerRunCommandAcceptsMultipleTaskOptions.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-59452-MultipleTasksInSchedulerCommand.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-87451-SchedulerRunCommandAcceptsMultipleTaskOptions.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88147-AddPossibilityToConfigureThePathToSitemapXslFile.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-88147-AddPossibilityToConfigureThePathToSitemapXslFile.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-88147-AddPossibilityToConfigureThePathToSitemapXslFile.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-88147-AddPossibilityToConfigureThePathToSitemapXslFile.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88818-IntroduceEventsToModifyCKEditorConfiguration.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-88818-IntroduceEventsToModifyCKEditorConfiguration.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-88818-IntroduceEventsToModifyCKEditorConfiguration.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-88818-IntroduceEventsToModifyCKEditorConfiguration.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88901-RenderAllFieldsInElementInformationController.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-88901-RenderAllFieldsInElementInformationController.rst
similarity index 79%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-88901-RenderAllFieldsInElementInformationController.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-88901-RenderAllFieldsInElementInformationController.rst
index f15e913c4f0caad97c688455be5457b8079d2687..72303fc2614201b4fe70b9ffc40048c397f3bc57 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-88901-RenderAllFieldsInElementInformationController.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-88901-RenderAllFieldsInElementInformationController.rst
@@ -16,8 +16,8 @@ the selected type.
Impact
======
-The TCA configuration `showRecordFieldList` inside the section `interface` is
-not evaluated anymore and all occurences have been removed.
+The TCA configuration :php:`showRecordFieldList` inside the section :php:`interface` is
+not evaluated anymore and all occurrences have been removed.
A migration wizard is available that removes the option from your TCA and adds
a deprecation message to the deprecation log where code adaption has to take place.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88921-NewEventInThePageLayoutViewClassToEnrichContentIntoTheColumnsInTheBackendLayout.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-88921-NewEventInThePageLayoutViewClassToEnrichContentIntoTheColumnsInTheBackendLayout.rst
similarity index 92%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-88921-NewEventInThePageLayoutViewClassToEnrichContentIntoTheColumnsInTheBackendLayout.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-88921-NewEventInThePageLayoutViewClassToEnrichContentIntoTheColumnsInTheBackendLayout.rst
index 178a926c7aa722dd94e516b93e12e924e9a36bbe..80350383283faac901486b8d5900713e23dafb6a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-88921-NewEventInThePageLayoutViewClassToEnrichContentIntoTheColumnsInTheBackendLayout.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-88921-NewEventInThePageLayoutViewClassToEnrichContentIntoTheColumnsInTheBackendLayout.rst
@@ -9,7 +9,7 @@ See :issue:`88921`
Description
===========
-Two new PSR-14 events are added in the PageLayoutView class.
+Two new PSR-14 events have been added to the :php:`PageLayoutView` class.
Those events can be used to add content into any column of a BackendLayout.
You can use this for example to show some content in a column without a ``colPos`` assigned.
@@ -21,7 +21,7 @@ You can use business logic to show content in specific columns.
E.g. for displaying content only in columns without any ``colPos``
in the BackendLayout configuration.
-Example Service.yaml to register the event listener in your own extension:
+Example how to register the event listener in your own extension:
:file:`EXT:my_extension/Configuration/Services.yaml`
@@ -74,6 +74,6 @@ executed before or after the given identifiers.
}
With the :php:`$event->setStopRendering()` method,
-you can make sure listeners that no other listeners are triggered after the current listener.
+you can make sure that no other listeners are triggered after the current listener.
.. index:: ext:backend, PHP-API
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88962-Re-implementOldPIDupinRootlineTypoScriptCondition.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-88962-Re-implementOldPIDupinRootlineTypoScriptCondition.rst
similarity index 76%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-88962-Re-implementOldPIDupinRootlineTypoScriptCondition.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-88962-Re-implementOldPIDupinRootlineTypoScriptCondition.rst
index 3c8d73a1555462bdb570a8d63673f8db348b6bcf..800985f85de0e3221fdef348bafb405d4d127fd8 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-88962-Re-implementOldPIDupinRootlineTypoScriptCondition.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-88962-Re-implementOldPIDupinRootlineTypoScriptCondition.rst
@@ -9,17 +9,17 @@ See :issue:`88962`
Description
===========
-The `PIDupinRootline` condition in TypoScript has been reimplemented within the Symfony
+The :ts:`PIDupinRootline` condition in TypoScript has been reimplemented within the Symfony
expression language.
-A new property `tree.rootLineParentIds` has been added to the `tree` object which
+A new property :ts:`tree.rootLineParentIds` has been added to the :ts:`tree` object which
is available in the Symfony expression language to provide checks for all parent
page IDs of the current rootline.
Impact
======
-When using the classic `PIDupinRootline` condition, you can easily switch to the
+When using the classic :ts:`PIDupinRootline` condition, you can easily switch to the
condition with the new expression:
Old TypoScript condition syntax:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-89032-RenderFieldControlForSelectSingleElement.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89032-RenderFieldControlForSelectSingleElement.rst
similarity index 97%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-89032-RenderFieldControlForSelectSingleElement.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-89032-RenderFieldControlForSelectSingleElement.rst
index 673080642642caf2ea9703a4b32adacf4174e92d..8627f6e1edfe41757fc3ffca1507bc03cd14b4c3 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-89032-RenderFieldControlForSelectSingleElement.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89032-RenderFieldControlForSelectSingleElement.rst
@@ -20,12 +20,11 @@ to add nodes and wizards.
For example, add a link popup button to a select called "field_name" of the pages table:
-.. code-block::
+.. code-block:: php
$GLOBALS['TCA']['pages']['columns']['field_name']['config']['fieldControl']['linkPopup'] = [
'renderType' => 'linkPopup',
];
-
.. index:: Backend, TCA, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-89139-AddDependencyInjectionSupportForConsoleCommands.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89139-AddDependencyInjectionSupportForConsoleCommands.rst
similarity index 60%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-89139-AddDependencyInjectionSupportForConsoleCommands.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-89139-AddDependencyInjectionSupportForConsoleCommands.rst
index a4b27e81a28c13e4836951acef364cc05f26a202..8d6ded29818fcbb9abc703cb43dc48ed1493a5ce 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-89139-AddDependencyInjectionSupportForConsoleCommands.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89139-AddDependencyInjectionSupportForConsoleCommands.rst
@@ -12,35 +12,37 @@ Description
Support for dependency injection in console commands has been added.
Command dependencies can now be injected via constructor or other injection techniques.
-Therefore a new dependency injection tag `console.command` has been added.
-Commands tagged with `console.command` are lazy loaded. That means they will only be
+Therefore, a new dependency injection tag :yaml:`console.command` has been added.
+Commands tagged with :yaml:`console.command` are lazy loaded. That means they will only be
instantiated when they are actually executed, when the `help` subcommand is executed,
or when available schedulable commands are iterated.
-The legacy command definition format :php:`Configuration/Commands.php` has been deprecated.
+The legacy command definition format :file:`Configuration/Commands.php` has been marked as deprecated.
Impact
======
It is recommended to configure dependency injection tags for all commands, as the legacy command
-definition format :php:`Configuration/Commands.php` has been deprecated.
+definition format :file:`Configuration/Commands.php` will be removed in TYPO3 v11.
-Commands that have been configured via `console.command` tag override legacy commands from
-:php:`Configuration/Commands.php` without throwing a deprecation error for those commands.
+Commands that have been configured via :yaml:`console.command` tag override legacy commands from
+:file:`Configuration/Commands.php` without triggering a PHP :php:`E_USER_DEPRECATED` error for those commands.
Backwards compatibility with older TYPO3 version can be achieved by specifying both variants,
-legacy configuration in :php:`Configuration/Commands.php` and new configuration via
-`console.command` tag.
+legacy configuration in :file:`Configuration/Commands.php` and new configuration via
+:yaml:`console.command` tag.
Usage
=====
-Add the `console.command` tag to command classes.
-Use the tag attribute `command` to specify the command name.
-The optional tag attribute `schedulable` may be set to false
+Add the :yaml:`console.command` tag to command classes.
+Use the tag attribute :yaml:`command` to specify the command name.
+The optional tag attribute :yaml:`schedulable` may be set to false
to exclude the command from the TYPO3 scheduler.
+:file:`your_extension/Configuration/Services.yaml`
+
.. code-block:: yaml
services:
@@ -56,7 +58,7 @@ to exclude the command from the TYPO3 scheduler.
schedulable: false
Command aliases are to be configured as separate tags.
-The optonal tag attribute `alias` should be set to true for alias commands.
+The optional tag attribute :yaml:`alias` should be set to true for alias commands.
.. code-block:: yaml
diff --git a/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89551-AddFluidAdditionalAttributesToTheFormElement.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89551-AddFluidAdditionalAttributesToTheFormElement.rst
new file mode 100644
index 0000000000000000000000000000000000000000..e2023da984e26245f65c6c5b6fd3eef19139a8e5
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89551-AddFluidAdditionalAttributesToTheFormElement.rst
@@ -0,0 +1,34 @@
+.. include:: ../../Includes.txt
+
+===================================================================
+Feature: #89551 - Add fluidAdditionalAttributes to the form element
+===================================================================
+
+See :issue:`89551`
+
+Description
+===========
+
+Allows to configure :yaml:`fluidAdditionalAttributes` within a form element:
+
+.. code-block:: yaml
+
+ TYPO3:
+ CMS:
+ Form:
+ prototypes:
+ standard:
+ formElementsDefinition:
+ Form:
+ renderingOptions:
+ fluidAdditionalAttributes:
+ novalidate: 'novalidate'
+
+
+Impact
+======
+
+For projects using their own Form template, the following attribute can be set on viewhelper :html:`formvh:form` as attribute:
+:html:`additionalAttributes="{formvh:translateElementProperty(element: form, property: 'fluidAdditionalAttributes')}"`
+
+.. index:: Fluid, ext:form
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-89644-AddOptionalArgumentFieldsToEditRecordViewHelpers.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89644-AddOptionalArgumentFieldsToEditRecordViewHelpers.rst
similarity index 71%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-89644-AddOptionalArgumentFieldsToEditRecordViewHelpers.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-89644-AddOptionalArgumentFieldsToEditRecordViewHelpers.rst
index 915834188f4ef66f0cbceef76dee3a6ba015be5e..b11336bf1d3c3c06acf0138bf71c6a8da018b1eb 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-89644-AddOptionalArgumentFieldsToEditRecordViewHelpers.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89644-AddOptionalArgumentFieldsToEditRecordViewHelpers.rst
@@ -9,7 +9,7 @@ See :issue:`89644`
Description
===========
-An optional argument "fields" is added to the uri.editRecord and link.editRecord ViewHelper.
+An optional argument "fields" is added to the :html:`uri.editRecord` and :html:`link.editRecord` ViewHelper.
This can contain the names of one or more database fields (comma separated).
If the argument "fields" is set, FormEngine creates a form to edit only these fields.
@@ -18,11 +18,11 @@ If the argument "fields" is set, FormEngine creates a form to edit only these fi
Impact
======
-This ViewHelper passes the value given in the `fields` argument to the backend route
-'/record/edit` as `columnsOnly` argument.
+This ViewHelper passes the value given in the :html:`fields` argument to the backend route
+`/record/edit` as :html:`columnsOnly` argument.
-The functionality for `columnsOnly` already existed for the backend route
-`/record/edit` before this patch.
+The functionality for :html:`columnsOnly` has always been there for the backend route
+`/record/edit` even before this patch.
Example
=======
@@ -45,5 +45,4 @@ Output:
</a>
-
.. index:: Fluid, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-89650-AllowLineBreaksInTCADescriptions.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89650-AllowLineBreaksInTCADescriptions.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-89650-AllowLineBreaksInTCADescriptions.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-89650-AllowLineBreaksInTCADescriptions.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-89738-ApiForAjaxRequests.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89738-ApiForAjaxRequests.rst
similarity index 95%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-89738-ApiForAjaxRequests.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-89738-ApiForAjaxRequests.rst
index 2b7743ed23fda0b7757f363e3bbe5065c1a8e042..64264edad8d63b471bbc9de39a71f220d1fe6788 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-89738-ApiForAjaxRequests.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89738-ApiForAjaxRequests.rst
@@ -19,7 +19,7 @@ To send a request, a new instance of `AjaxRequest` must be created which receive
* :js:`url` (string) - The endpoint to send the request to
-For compatibility reasons the :js:`Promise` prototype is extended to have basic support for jQuery's `$.Deferred()`.
+For compatibility reasons the :js:`Promise` prototype is extended to have basic support for jQuery's :js:`$.Deferred()`.
In all erroneous cases, the internal promise is rejected with an instance of `ResponseError` containing the original
`response object`_.
@@ -44,7 +44,7 @@ This method receives the following arguments:
* :js:`init` (object) - Optional: additional `request configuration`_ for the request object used by :js:`fetch()`
-The method returns a promise resolved to a `AjaxResponse`.
+The method returns a promise resolved to an `AjaxResponse`.
Example:
@@ -73,7 +73,7 @@ This method receives the following arguments:
* :js:`data` (object) - Request body sent to the endpoint, get's converted to :js:`FormData`
* :js:`init` (object) - Optional: additional `request configuration`_ for the request object used by :js:`fetch()`
-The method returns a promise resolved to a `AjaxResponse`.
+The method returns a promise resolved to an `AjaxResponse`.
Example:
@@ -108,7 +108,7 @@ This method receives the following arguments:
* :js:`data` (object) - Request body sent to the endpoint, get's converted to :js:`FormData`
* :js:`init` (object) - Optional: additional `request configuration`_ for the request object used by :js:`fetch()`
-The method returns a promise resolved to a `AjaxResponse`.
+The method returns a promise resolved to an `AjaxResponse`.
Example:
@@ -137,7 +137,7 @@ This method receives the following arguments:
* :js:`data` (object) - Request body sent to the endpoint, get's converted to :js:`FormData`
* :js:`init` (object) - Optional: additional `request configuration`_ for the request object used by :js:`fetch()`
-The method returns a promise resolved to a `AjaxResponse`.
+The method returns a promise resolved to an `AjaxResponse`.
Example:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-89870-NewPSR-14EventsForExtbase-relatedSignals.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89870-NewPSR-14EventsForExtbase-relatedSignals.rst
similarity index 99%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-89870-NewPSR-14EventsForExtbase-relatedSignals.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-89870-NewPSR-14EventsForExtbase-relatedSignals.rst
index ecac644c7a1b30f0bac7f77974ee79897c42daa6..25d85d6d03a58f6c8eb467a21f37540d3e18a921 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-89870-NewPSR-14EventsForExtbase-relatedSignals.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89870-NewPSR-14EventsForExtbase-relatedSignals.rst
@@ -30,6 +30,7 @@ Impact
Existing signals are replaced and should not be used anymore, as PSR-14 event classes exactly specify what can be modified or listened to.
The following signals should not be used anymore then:
+
- :php:`TYPO3\CMS\Extbase\Mvc\Dispatcher::afterRequestDispatch`
- :php:`TYPO3\CMS\Extbase\Mvc\Controller\ActionController::beforeCallActionMethod`
- :php:`TYPO3\CMS\Extbase\Persistence\Generic\Mapper\DataMapper::afterMappingSingleRow`
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-89894-SeparateSystemExtensionsFrom3rd-partyExtensionsVisually.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89894-SeparateSystemExtensionsFrom3rd-partyExtensionsVisually.rst
similarity index 56%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-89894-SeparateSystemExtensionsFrom3rd-partyExtensionsVisually.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-89894-SeparateSystemExtensionsFrom3rd-partyExtensionsVisually.rst
index c605b4bdb465d20a53ffdd1eb50a676ef7000640..625cc373d2432a3b5366378ebd1aaea79974edb3 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-89894-SeparateSystemExtensionsFrom3rd-partyExtensionsVisually.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89894-SeparateSystemExtensionsFrom3rd-partyExtensionsVisually.rst
@@ -9,7 +9,10 @@ See :issue:`89894`
Description
===========
-The Extension Manager in TYPO3 allows backend users to list, activate, deactivate, configure, and possibly add/remove extensions from the system. When using the Extension Manager, backend users work with either core extensions (system extensions) or 3rd-party extensions, depending on their task.
+The Extension Manager in TYPO3 allows backend users to list, activate, deactivate, configure
+and possibly add/remove extensions from the system. When using the Extension Manager,
+backend users work with either core extensions (system extensions) or 3rd-party extensions,
+depending on their task.
The extension list shown in the Extension Manager can now be filtered by certain extension types (system and 3rd-party extensions).
@@ -17,6 +20,8 @@ The extension list shown in the Extension Manager can now be filtered by certain
Impact
======
-A limited list of extensions, either system or 3rd-party extensions, makes it easier for backend users to find the extension they intend to work with and/or to get a quick overview which extensions are currently installed (e.g. 3rd-party extensions). This improves the usability of the backend for integrators/administrators.
+A limited list of extensions, either system or 3rd-party extensions, makes it easier for backend users
+to find the extension they intend to work with and/or to get a quick overview which extensions are
+currently installed (e.g. 3rd-party extensions). This improves the usability of the backend for integrators/administrators.
.. index:: Backend, ext:extensionmanager
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-89929-GalicianFlag.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89929-GalicianFlag.rst
similarity index 75%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-89929-GalicianFlag.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-89929-GalicianFlag.rst
index 58d8456fd7fa3ddce992c679efc1ded1931a5f84..747cdc816e359a085083e5d52866b6886321248b 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-89929-GalicianFlag.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89929-GalicianFlag.rst
@@ -15,7 +15,7 @@ When adding a new language to a site or the system (`sys_language`) the Galician
Impact
======
-A previous error, where the flag for Greelandic was available (ISO Code "kl") under the "GL" shortcut, was resolved with this feature,
+A previous error, where the flag for Greenlandic was available (ISO Code "kl") under the "GL" shortcut, was resolved with this feature,
as both flags now represent the proper ISO code.
.. index:: Backend, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-89978-IntroduceStatusReportForInsecureExceptionHandlerSettings.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89978-IntroduceStatusReportForInsecureExceptionHandlerSettings.rst
similarity index 61%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-89978-IntroduceStatusReportForInsecureExceptionHandlerSettings.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-89978-IntroduceStatusReportForInsecureExceptionHandlerSettings.rst
index 5fcb9070ccc82cd75733f0c14b91dc7a56f958d7..e375b7ca5082edc7c3a925fc87d505d0f1b2d1aa 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-89978-IntroduceStatusReportForInsecureExceptionHandlerSettings.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-89978-IntroduceStatusReportForInsecureExceptionHandlerSettings.rst
@@ -9,7 +9,9 @@ See :issue:`89978`
Description
===========
-When using a debug exception handler in production (either by configuring it explicitly or by using the wrong application context) stack traces may disclose information. To avoid such setups a new status report has been introduced, that warns administrators if a debug exception handler is configured.
+When using a debug exception handler in production (either by configuring it explicitly
+or by using the wrong application context) stack traces may disclose information.
+To avoid such setups a new status report has been introduced that warns administrators if a debug exception handler is configured.
Impact
@@ -17,11 +19,12 @@ Impact
To mitigate the information disclosure, a new status report has
been introduced:
+
- if display errors is set to 1 (-> uses DebugExceptionHandler setting)
- and context is Production an Error is displayed
+ and context is Production, an Error is displayed
- if display errors is set to 1 (-> uses DebugExceptionHandler setting)
- and context is Development a Warning is displayed
+ and context is Development, a Warning is displayed
- if the production exception handler setting is configured to use the
- DebugExceptionHandler an Error is displayed
+ DebugExceptionHandler, an Error is displayed
-.. index:: Backend, LocalConfiguration, ext:reports
\ No newline at end of file
+.. index:: Backend, LocalConfiguration, ext:reports
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90026-ExposeInternalTypoLinkPartsInTypolinkViewHelper.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90026-ExposeInternalTypoLinkPartsInTypolinkViewHelper.rst
similarity index 81%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90026-ExposeInternalTypoLinkPartsInTypolinkViewHelper.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90026-ExposeInternalTypoLinkPartsInTypolinkViewHelper.rst
index f3bba8b751ecf5087d03796f5ff56635dbafea7f..ed06b31b6fc3c16219e19f79df18c4d2872498b0 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90026-ExposeInternalTypoLinkPartsInTypolinkViewHelper.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90026-ExposeInternalTypoLinkPartsInTypolinkViewHelper.rst
@@ -11,9 +11,9 @@ Description
Parameters being generated internally by TypoLink using
:html:`<f:link.typolink parts-as="typoLinkParts">` view helper are exposed as
-variable and can be used in Fluid templates again.
+variable and can be used in Fluid templates.
-View helper attribute `parts-as` (default `typoLinkParts`) allows to define
+View helper attribute :html:`parts-as` (default :html:`typoLinkParts`) allows to define the
variable name to be used containing the following internal parts:
* url
@@ -30,10 +30,10 @@ in `TypoScript reference`_
Impact
======
-Multiple instructions for attribute `parameter` (e.g. persisted to entity
+Multiple instructions for attribute :html:`parameter` (e.g. persisted to entity
record) can be used individually.
-.. code-block: html
+.. code-block:: html
<f:link.typolink parameter="123 _top news title" parts-as="parts">
{parts.url}
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90042-SpecialPageIconsCustomizableByDoktype.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90042-SpecialPageIconsCustomizableByDoktype.rst
similarity index 91%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90042-SpecialPageIconsCustomizableByDoktype.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90042-SpecialPageIconsCustomizableByDoktype.rst
index 30f0ad996a79584db76684431e2d9248255e639e..b8c32062c041ba36e8274c85a286f47904cf313f 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90042-SpecialPageIconsCustomizableByDoktype.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90042-SpecialPageIconsCustomizableByDoktype.rst
@@ -32,7 +32,7 @@ Provide custom icons in TCA like so:
],
]
-Icons you don't provide here will automatically fallback to the variant for regular page doktype.
+Icons you don't provide will automatically fall back to the variant for regular page doktypes.
.. note::
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90052-AddYamlConfigurationToConfigurationModule.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90052-AddYamlConfigurationToConfigurationModule.rst
similarity index 76%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90052-AddYamlConfigurationToConfigurationModule.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90052-AddYamlConfigurationToConfigurationModule.rst
index 284ebfc37ec2371585f4f404c730ec324bfcbc73..18ace5c799e7ee0013f36e6712309863b3c45a2d 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90052-AddYamlConfigurationToConfigurationModule.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90052-AddYamlConfigurationToConfigurationModule.rst
@@ -10,8 +10,8 @@ Description
===========
If the Form system extension is installed, a new entry
-:guilabel:`Form: YAML Configuration` is available in the menu of the
-:guilabel:`SYSTEM > Configuration` module of the lowlevel system extension.
+``Form: YAML Configuration`` is available in the menu of the
+``SYSTEM > Configuration`` module of the lowlevel system extension.
When selected, the parsed YAML configuration of the form setup is displayed.
.. index:: Backend, ext:lowlevel, ext:form
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90068-ImplementBetterFileDumpController.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90068-ImplementBetterFileDumpController.rst
similarity index 64%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90068-ImplementBetterFileDumpController.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90068-ImplementBetterFileDumpController.rst
index 0fb440d6dafcd41883bd55a557ef4cf832e7fff3..ec7d6007c175d6b43860c4da03abed540855cdee 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90068-ImplementBetterFileDumpController.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90068-ImplementBetterFileDumpController.rst
@@ -14,21 +14,21 @@ can adopt image sizes to records of sys_file.
Following URI-Parameters are now possible:
-+ `t` (*Type*): Can be one of `f` (sys_file), `r` (sys_file_reference) or `p` (sys_file_processedfile)
-+ `f` (*File*): Use it for an UID of table sys_file
-+ `r` (*Reference*): Use it for an UID of table sys_file_reference
-+ `p` (*Processed*): Use it for an UID of table sys_file_processedfile
-+ `s` (*Size*): Use it for an UID of table sys_file_processedfile
-+ `cv` (*CropVariant*): In case of sys_file_reference, you can assign it a cropping variant
-
-You have to choose one of these parameters: `f`, `r` and `p`. It is not possible
++ :php:`t` (*Type*): Can be one of :php:`f` (`sys_file`), :php:`r` (`sys_file_reference`) or :php:`p` (`sys_file_processedfile`)
++ :php:`f` (*File*): Use it for a UID of table :sql:`sys_file`
++ :php:`r` (*Reference*): Use it for a UID of table :sql:`sys_file_reference`
++ :php:`p` (*Processed*): Use it for a UID of table :sql:`sys_file_processedfile`
++ :php:`s` (*Size*): Use it for a UID of table :sql:`sys_file_processedfile`
++ :php:`cv` (*CropVariant*): In case of `sys_file_reference`, you can assign it a cropping variant
+
+You have to choose one of these parameters: :php:`f`, :php:`r` or :php:`p`. It is not possible
to use them multiple times in one request.
-The Parameter `s` has following syntax: width:height:minW:minH:maxW:maxH. You
-can leave this Parameter empty to load file in original size. Parameter `width`
-and `height` can consist of trailing `c` or `m` identicator like known from TS.
+The Parameter :php:`s` has following syntax: width:height:minW:minH:maxW:maxH. You
+can leave this Parameter empty to load the file in original size. Parameter :php:`width`
+and :php:`height` can feature the trailing :ts:`c` or :ts:`m` indicator like known from TS.
-See following example how to create an URI using the FileDumpController for
+See the following example on how to create a URI using the :php:`FileDumpController` for
a sys_file record with a fixed image size:
.. code-block:: php
@@ -41,7 +41,7 @@ a sys_file record with a fixed image size:
$publicUrl .= '?' . http_build_query($queryParameterArray, '', '&', PHP_QUERY_RFC3986);
-In this example crop variant `default` and an image size of 320:280 will be
+In this example crop variant :php:`default` and an image size of 320:280 will be
applied to a sys_file_reference record:
.. code-block:: php
@@ -55,8 +55,8 @@ applied to a sys_file_reference record:
$publicUrl .= '?' . http_build_query($queryParameterArray, '', '&', PHP_QUERY_RFC3986);
-This example shows the usage how to create an URI to load an image of
-sys_file_processfiles:
+This example shows the usage how to create a URI to load an image of
+sys_file_processedfile:
.. code-block:: php
@@ -68,13 +68,14 @@ sys_file_processfiles:
There are some restriction while using the new URI-Parameters:
+
+ You can't assign any size parameter to processed files, as they are already resized.
-+ You can't apply CropVariants to sys_file and sys_file_processedfile records.
++ You can't apply CropVariants to `sys_file` and `sys_file_processedfile` records.
Impact
======
-No impact, as this class was extended only. It's full backwards compatible
+No impact, as this class was extended only. It's fully backwards compatible.
.. index:: FAL, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90114-MakeTranslationOfFilelistOptional.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90114-MakeTranslationOfFilelistOptional.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90114-MakeTranslationOfFilelistOptional.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90114-MakeTranslationOfFilelistOptional.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90136-ShowApplicationContextInTheEnvironmentModule.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90136-ShowApplicationContextInTheEnvironmentModule.rst
similarity index 84%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90136-ShowApplicationContextInTheEnvironmentModule.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90136-ShowApplicationContextInTheEnvironmentModule.rst
index 6c8847faa88e28bfec12635624a1d19acab2e644..51dc108743690402c47883a010e592dc7218875d 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90136-ShowApplicationContextInTheEnvironmentModule.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90136-ShowApplicationContextInTheEnvironmentModule.rst
@@ -16,7 +16,7 @@ application context the TYPO3 instance is running with.
Impact
======
-You can now look up the application context from inside the admin tool without
+Administrators can now look up the application context from inside the admin tool without
having to log into the TYPO3 backend.
.. index:: ext:install
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90168-IntroduceModalActions.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90168-IntroduceModalActions.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90168-IntroduceModalActions.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90168-IntroduceModalActions.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90203-MakeWorkspaceAvailableInTypoScriptConditions.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90203-MakeWorkspaceAvailableInTypoScriptConditions.rst
similarity index 81%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90203-MakeWorkspaceAvailableInTypoScriptConditions.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90203-MakeWorkspaceAvailableInTypoScriptConditions.rst
index 49a207eaa2f83d7b6cbdc1d567b8ea4c7616f00d..9c1b1adae6915cac39a53db2a804e056bdd365a8 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90203-MakeWorkspaceAvailableInTypoScriptConditions.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90203-MakeWorkspaceAvailableInTypoScriptConditions.rst
@@ -9,10 +9,10 @@ See :issue:`90203`
Description
===========
-A new TypoScript expression language variable `workspace` has been added.
+A new TypoScript expression language variable :ts:`workspace` has been added.
It can be used to match a given expression against common workspace parameters.
-Currently, the parameters `workspaceId`, `isLive` and `isOffline` are supported.
+Currently, the parameters :ts:`workspaceId`, :ts:`isLive` and :ts:`isOffline` are supported.
Examples
--------
@@ -43,4 +43,4 @@ Impact
The new feature allows matching against several workspace parameters within TypoScript.
-.. index:: TypoScript
\ No newline at end of file
+.. index:: TypoScript
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90213-SupportBitAndInTypoScriptStdWrapIf.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90213-SupportBitAndInTypoScriptStdWrapIf.rst
similarity index 75%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90213-SupportBitAndInTypoScriptStdWrapIf.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90213-SupportBitAndInTypoScriptStdWrapIf.rst
index 24a857ec05644d87ee9f02ad33209e0c92656495..d37dd40e0f1f16d4f6ed66ff448910b532f49dd0 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90213-SupportBitAndInTypoScriptStdWrapIf.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90213-SupportBitAndInTypoScriptStdWrapIf.rst
@@ -1,8 +1,8 @@
.. include:: ../../Includes.txt
-==========================================================
-Feature: #90213 - Support bit and in TypoScript stdWrap_if
-==========================================================
+============================================================
+Feature: #90213 - Support `bit and` in TypoScript stdWrap_if
+============================================================
See :issue:`90213`
@@ -35,4 +35,4 @@ An example usage could look like this:
}
}
-.. index:: ext:frontend, TypoScript, NotScanned
+.. index:: ext:frontend, TypoScript
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90234-IntroduceCacheHashConfigurationAndMatchingIndicators.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90234-IntroduceCacheHashConfigurationAndMatchingIndicators.rst
similarity index 65%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90234-IntroduceCacheHashConfigurationAndMatchingIndicators.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90234-IntroduceCacheHashConfigurationAndMatchingIndicators.rst
index 0edb135daababd55c0761d97f3a9602f473030c4..78e252db9182799698678b840dfce4847545372c 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90234-IntroduceCacheHashConfigurationAndMatchingIndicators.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90234-IntroduceCacheHashConfigurationAndMatchingIndicators.rst
@@ -9,8 +9,8 @@ See :issue:`90234`
Description
===========
-Settings for `$GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']` are modelled
-in class `CacheHashConfiguration` which takes care of validating configuration.
+Settings for :php:`$GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']` are modelled
+in class :php:`CacheHashConfiguration` which takes care of validating configuration.
It also determines whether corresponding aspects apply to a given URL
parameter.
@@ -18,18 +18,19 @@ Besides exact matches (*equals*) it is possible to apply partial matches at
the beginning of a parameter (*startsWith*) or inline occurrences (*contains*).
URL parameter names are prefixed with the following indicators:
-+ `=` (*equals*): exact match, default behavior if not given
-+ `^` (*startsWith*): matching the beginning of a parameter name
-+ `~` (*contains*): matching any inline occurrence in a parameter name
++ :php:`=` (*equals*): exact match, default behavior if not given
++ :php:`^` (*startsWith*): matching the beginning of a parameter name
++ :php:`~` (*contains*): matching any inline occurrence in a parameter name
These indicators can be used for all previously existing sub-properties
-`cachedParametersWhiteList`, `excludedParameters`, `excludedParametersIfEmpty`
-and `requireCacheHashPresenceParameters`.
+:php:`cachedParametersWhiteList`, :php:`excludedParameters`, :php:`excludedParametersIfEmpty`
+and :php:`requireCacheHashPresenceParameters`.
Example (excerpt of `LocalConfiguration.php`)
---------------------------------------------
.. code-block:: php
+
$GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash'] = [
'excludedParameters' => [
'utm_source',
@@ -47,7 +48,7 @@ Impact
======
Configuration related to *cHash* URL parameter supports partial matches which
-overcomes the previous necessity to explicitly name all parameter names to be
+overcomes the previous necessity to explicitly state all parameter names to be
excluded.
For instance instead of having exclude items like
@@ -62,8 +63,8 @@ For instance instead of having exclude items like
...
],
-partial matches allow to simply configuration and consider all items having
-`tx_my[data]` (or `tx_my[data][` to be more specific) as prefix like
+partial matches allow to simplify the configuration and consider all items having
+:php:`tx_my[data]` (or :php:`tx_my[data][` to be more specific) as prefix like
.. code-block:: php
@@ -72,7 +73,7 @@ partial matches allow to simply configuration and consider all items having
...
],
-Previous configuration for the `cHash` section is still supported - there is
+The present configuration for the :php:`cHash` section is still supported - there is
no syntactical requirement to adjust those changes.
.. index:: Frontend, LocalConfiguration, ext:frontend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90249-NewPSR-14EventsForExistingPackage-relatedSignalSlots.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90249-NewPSR-14EventsForExistingPackage-relatedSignalSlots.rst
similarity index 96%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90249-NewPSR-14EventsForExistingPackage-relatedSignalSlots.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90249-NewPSR-14EventsForExistingPackage-relatedSignalSlots.rst
index c9ef71eb3e38120a28e1fb1cb853b1e205059a89..96e9f746edb3493f0626d68bace23268eb075514 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90249-NewPSR-14EventsForExistingPackage-relatedSignalSlots.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90249-NewPSR-14EventsForExistingPackage-relatedSignalSlots.rst
@@ -9,7 +9,7 @@ See :issue:`90249`
Description
===========
-PSR-14-based event dispatching allows for TYPO3 Extensions or PHP packages to
+PSR-14-based event dispatching allows for TYPO3 extensions or PHP packages to
extend TYPO3 Core functionality in an exchangeable way.
The following new PSR-14 events have been introduced:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90262-AddArgon2idToPasswordHashAlgorithms.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90262-AddArgon2idToPasswordHashAlgorithms.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90262-AddArgon2idToPasswordHashAlgorithms.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90262-AddArgon2idToPasswordHashAlgorithms.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90265-ShowDispatchedEventsInAdminPanel.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90265-ShowDispatchedEventsInAdminPanel.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90265-ShowDispatchedEventsInAdminPanel.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90265-ShowDispatchedEventsInAdminPanel.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90266-Fluid-basedTemplatedEmails.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90266-Fluid-basedTemplatedEmails.rst
similarity index 80%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90266-Fluid-basedTemplatedEmails.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90266-Fluid-basedTemplatedEmails.rst
index b0fb32ddd42d3d206a324c450e6080439f93eb13..fe66c4f9afa4d4cf3674f5112dfd96583199fd6e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90266-Fluid-basedTemplatedEmails.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90266-Fluid-basedTemplatedEmails.rst
@@ -1,7 +1,7 @@
.. include:: ../../Includes.txt
==============================================
-Feature: #90266 - Fluid-based templated emails
+Feature: #90266 - Fluid-based email templating
==============================================
See :issue:`90266`
@@ -15,32 +15,32 @@ emails out-of-the-box. The email contents are built with Fluid Templating Engine
TYPO3's backend functionality already ships with a default layout
for templated emails, which can be tested out in TYPO3's install tool test email functionality.
-It is also possible to set a default mode for sending out emails via :php:`$GLOBALS['TYPO3_CONF_VARS']['MAIL']['format']` which can be `both`, `plain` or `html`.
+It is also possible to set a default mode for sending out emails via :php:`$GLOBALS['TYPO3_CONF_VARS']['MAIL']['format']`
+which can be :php:`both`, :php:`plain` or :php:`html`.
This option can however overridden by Extension authors in their use cases.
All Fluid-based template paths can be configured via
+:file:`LocalConfiguration.php`:
+
* :php:`$GLOBALS['TYPO3_CONF_VARS']['MAIL']['layoutRootPaths']`
* :php:`$GLOBALS['TYPO3_CONF_VARS']['MAIL']['partialRootPaths']`
* :php:`$GLOBALS['TYPO3_CONF_VARS']['MAIL']['templateRootPaths']`
-where TYPO3 reserves all array keys below `100` for internal purposes. If you want to provide custom templates or layouts,
-set this in your LocalConfiguration.php / AdditionalConfiguration.php file:
+where TYPO3 reserves all array keys below :php:`100` for internal purposes. If you want to provide custom templates or layouts,
+set this in your :file:`LocalConfiguration.php` / :file:`AdditionalConfiguration.php` file:
* :php:`$GLOBALS['TYPO3_CONF_VARS']['MAIL']['templateRootPaths'][700] = 'EXT:my_site_extension/Resources/Private/Templates/Email';`
* :php:`$GLOBALS['TYPO3_CONF_VARS']['MAIL']['layoutRootPaths'][700] = 'EXT:my_site_extension/Resources/Private/Layouts';`
-In addition, it is possible to define a section within the Fluid email,
-which - if defined - takes precedence over the :php:`subject()` method.
-
-In addition, it is possible to define a section within the Fluid email,
+In addition, it is possible to define a section within the Fluid template,
which - if set - takes precedence over the :php:`subject()` method.
Impact
======
-TYPO3 now sends out templated emails for system emails in both plaintext and HTML formats.
+TYPO3 now sends out templated messages for system emails in both plaintext and HTML format.
It is possible to use the same API in your custom extension like this:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90267-CustomPlaceholderProcessingInSiteConfig.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90267-CustomPlaceholderProcessingInSiteConfig.rst
similarity index 84%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90267-CustomPlaceholderProcessingInSiteConfig.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90267-CustomPlaceholderProcessingInSiteConfig.rst
index bde8a0e35011d2a26d2edb8eded0dfa3a4a09bf2..061f3d6fc1c7bc5ff94f5f601bbd7eed077856ad 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90267-CustomPlaceholderProcessingInSiteConfig.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90267-CustomPlaceholderProcessingInSiteConfig.rst
@@ -17,6 +17,8 @@ Impact
It is now possible to register a new placeholder processor:
+:file:`LocalConfiguration.php`:
+
.. code-block:: php
$GLOBALS['TYPO3_CONF_VARS']['SYS']['yamlLoader']['placeholderProcessors'][\Vendor\MyExtension\PlaceholderProcessor\CustomPlaceholderProcessor::class] = [];
@@ -35,10 +37,10 @@ There are some options available to sort or disable placeholder processors if ne
'disabled' => false
];
-New placeholder processors must implement the `\TYPO3\CMS\Core\Configuration\Processor\Placeholder\PlaceholderProcessorInterface`
+New placeholder processors must implement the :php:`\TYPO3\CMS\Core\Configuration\Processor\Placeholder\PlaceholderProcessorInterface`
Placeholders look mostly like functions.
-So an implementation may look like the following
+So an implementation may look like the following:
.. code-block:: php
@@ -63,7 +65,7 @@ So an implementation may look like the following
}
-This may be used like the following in the site config
+This may be used like the following in the site configuration:
.. code-block:: yaml
@@ -71,7 +73,7 @@ This may be used like the following in the site config
anotherVariable: 'inline::%example(anotherValue)%::placeholder'
If a new processor returns a string or number, it may also be used inline as above.
-If it returns an array, it can not be used inline since the whole content will be replaced with the new value.
+If it returns an array, it cannot be used inline since the whole content will be replaced with the new value.
.. index:: Backend, PHP-API, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90298-ImproveUserInfoInBeuserModule.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90298-ImproveUserInfoInBeuserModule.rst
similarity index 83%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90298-ImproveUserInfoInBeuserModule.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90298-ImproveUserInfoInBeuserModule.rst
index 09b0b1bcf9cdb822fec15323395fbc15045c4fe2..e0f50c8923d222415599f6ff0ce65f0e4f13eae3 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90298-ImproveUserInfoInBeuserModule.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90298-ImproveUserInfoInBeuserModule.rst
@@ -13,7 +13,8 @@ The *Backend users* module has been improved by showing more details of TYPO3
Administrators and Editors:
- All assigned groups, including subgroups, are now evaluated
-- All data which can be set in the backend user or a assigned group are now shown including allowed page types, read & write access to tables
+- All data which can be set in the backend user or an assigned group are now shown including allowed page types
+- Read & write access to tables
- A new "detail view" for a TYPO3 Backend user has been added
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90333-Dashboard.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90333-Dashboard.rst
similarity index 82%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90333-Dashboard.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90333-Dashboard.rst
index 63845db80b4cd22a888009fe3b4101a45b1e9997..ff47ba2e6e8caf6f857154be06d9ed4b7bd9343d 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90333-Dashboard.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90333-Dashboard.rst
@@ -9,7 +9,7 @@ See :issue:`90333`
Description
===========
-A dashboard is introduced into TYPO3 to show the most important information to
+A dashboard is introduced into TYPO3 to show relevant information to
the current logged in user.
Every user with access to this backend module can now have one or more personal
@@ -26,8 +26,10 @@ information.
You can find the new dashboard in the toolbar in the top of your window.
+
Available widgets
^^^^^^^^^^^^^^^^^
+
The following widgets are shipped by core extensions now:
* TYPO3 news: A widget showing the latest 5 news items from typo3.org (EXT:dashboard)
@@ -40,21 +42,24 @@ The following widgets are shipped by core extensions now:
* Type of backend users: A widget to show the different types of backend users (EXT:dashboard)
* Failed Logins: This widget will show you the number of failed logins during the last 24 hours (EXT:dashboard)
+
Creating your own widget
^^^^^^^^^^^^^^^^^^^^^^^^
+
Besides the widgets shipped with TYPO3 core, you can also write your own widget. To
do so, you can extend one of the WidgetAbstracts available in EXT:dashboard.
-* `AbstractWidget`: a basic abstract that can be used as the start of simple widgets
-* `AbstractRssWidget`: with this abstract it is easy to create a widget showing a RSS feed
-* `AbstractListWidget`: this abstract will give you an easy start to show a list of items
-* `AbstractCtaButtonWidget`: when you want to show a Call-To-Action button, this is the right abstract
-* `AbstractChartWidget`: the base of all chart widgets
-* `AbstractBarChartWidget`: when you want to show a widget with a bar-chart you can extend this class
-* `AbstractDoughnutChartWidget`: this abstract gives you the possibility to create a doughnut-chart widget
-* `AbstractNumberWithIconWidget`: this abstract will give you the possibility to show a title, number and an icon
+* :php:`AbstractWidget`: a basic abstract that can be used as the start of simple widgets
+* :php:`AbstractRssWidget`: with this abstract it is easy to create a widget showing a RSS feed
+* :php:`AbstractListWidget`: this abstract will give you an easy start to show a list of items
+* :php:`AbstractCtaButtonWidget`: when you want to show a Call-To-Action button, this is the right abstract
+* :php:`AbstractChartWidget`: the base of all chart widgets
+* :php:`AbstractBarChartWidget`: when you want to show a widget with a bar-chart you can extend this class
+* :php:`AbstractDoughnutChartWidget`: this abstract gives you the possibility to create a doughnut-chart widget
+* :php:`AbstractNumberWithIconWidget`: this abstract will give you the possibility to show a title, number and an icon
-By extending one of those abstracts, and provide it with the right data, you are able to
+
+By extending one of those abstracts, and providing it with the needed data, you are able to
have a new widget quite fast. The only thing that is left is to register the widget.
Tag you widget in :file:`EXT:your_extension/Configuration/Services.yaml`:
@@ -69,23 +74,25 @@ Tag you widget in :file:`EXT:your_extension/Configuration/Services.yaml`:
identifier: widget-identifier-1
widgetGroups: 'general'
- # Variant 2, custom service name, allows multiple widget identifier
+ # Variant 2, custom service name, allows multiple widget identifiers
# to share the same class
widget.identifier:
class: Vendor\Extension\Widgets\MySecondWidget
arguments: ['widget-identifier-1']
tags:
- name: dashboard.widget
- # If ommited, the identifier would be the service name, thus 'widget.identifier'
+ # If omitted, the identifier would be the service name, thus 'widget.identifier'
identifier: widget-identifier-2
widgetGroups: 'general, typo3'
Every widget needs a unique identifier, the implementing class and at least one
-associated widget groups. Multiple widget groups are separated by comma.
+associated widget group. Multiple widget groups are separated by comma.
+
Configuring Widget Groups
^^^^^^^^^^^^^^^^^^^^^^^^^
+
Every widget is attached to one or more widget groups. Those groups are shown in the
modal when adding a new widget to your dashboard. In this way you can group the available
widgets to get a clear overview for your users. By default the following widget groups are
@@ -111,9 +118,11 @@ First you have the identifier as the key. This identifier is used to map widgets
group. You only have one property and that is the title. You can add a simple text, or a
translation string like in the example above.
+
Defining Dashboard Presets
^^^^^^^^^^^^^^^^^^^^^^^^^^
-As the last major feature, you have the possibility to create dashboard presets. Those
+
+You have the possibility to create dashboard presets. Those
presets are used when a user is creating a new dashboard. He can choose one of the available presets.
In a preset you can define which widgets and in which order those widgets will be added to the dashboard when created.
@@ -137,15 +146,17 @@ In that file you specify the information of the presets.
],
];
-You start again with the identifier which should be unique. Every preset needs a title, description, iconIdentifier, some widgets and a flag if the
+You start again with the dashboard preset identifier which should be unique. Every preset needs a title, description, iconIdentifier, some widgets and a flag if the
preset should be shown in the wizard to create a new dashboard. This last setting is to make it possible to not show it as a preset, but it can be used to
create this dashboard preset by default for new users.
+
Automatically create a dashboard for new users
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
If you have a new user in your backend, you might want to kickstart that user and provide a
basic dashboard. You can do this by defining which dashboard presets should be created by default
-when a user is new or when a user deletes all his dashboards.
+when a user gets created or when a user deletes all his dashboards.
You can define which dashboards will be created automatically by using the following TSconfig setting:
@@ -155,17 +166,20 @@ You can define which dashboards will be created automatically by using the follo
You can add the identifiers of multiple presets in a comma separated list.
+
Permissions
^^^^^^^^^^^
+
As widgets might contain sensitive information, it is also possible to define the permissions
of the widgets on a group base. In the backend group settings you have the possibility to allow
specific widgets. Only those widgets will be available for users in that group. Admin users
have access to all widgets by default.
+
Impact
======
This is a new backend module and will not replace any old features. If the dashboard
-extension is installed, it will be the default startup extension for new users.
+extension is installed, it will be the default startup page in TYPO3 Backend.
.. index:: Backend, Dashboard, ext:dashboard
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90348-NewFluid-basedReplacementForPageLayoutView.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90348-NewFluid-basedReplacementForPageLayoutView.rst
similarity index 55%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90348-NewFluid-basedReplacementForPageLayoutView.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90348-NewFluid-basedReplacementForPageLayoutView.rst
index a756f18c7049f293f7e7d6ecf2969e419ffeb284..b096f2c6528bdaaaf9477d9f46ae0f1b3c070997 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90348-NewFluid-basedReplacementForPageLayoutView.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90348-NewFluid-basedReplacementForPageLayoutView.rst
@@ -1,58 +1,67 @@
.. include:: ../../Includes.txt
-================================================================
-Feature: #90348 - New Fluid-based replacement for PageLayoutView
-================================================================
+============================================================
+Feature: #90348 - Fluid-based replacement for PageLayoutView
+============================================================
See :issue:`90348`
Description
===========
-A completely rewritten replacement for PageLayoutView has been added. This replacement allows third parties to override and extend any part of the "page" module's output by overriding Fluid templates.
+A completely rewritten replacement for PageLayoutView has been added. This replacement allows third parties
+to override and extend any part of the "page" module's output by overriding Fluid templates.
Although it is visually identical to the old :php:`PageLayoutView`'s output, the new alternative has a number of benefits:
-* The grid defined in a BackendLayout is now represented as objects which are assigned to Fluid templates and can be iterated to render rows, columns and records.
-* Custom BackendLayout implementations can now manipulate every part of the configuration that determines how the page module is rendered - or completely replace the logic that draws the "columns" and "languages" views of the page BE module.
-* Custom BackendLayout implementations can also provide custom classes for LanguageColumn, Grid, GridRow, GridColumn and GridColumnItem instances that are assigned to and used by Fluid templates to render the page layout.
-* Headers, footers and previews for content types can be created in Fluid in a way that groups each of these component templates by the content type (CType) value of content records.
+* The grid defined in a BackendLayout is now represented as objects which are assigned to Fluid templates and can be iterated over
+ to render rows, columns and records.
+* Custom BackendLayout implementations can now manipulate every part of the configuration that determines
+ how the page module is rendered - or completely replace the logic that draws the "columns" and "languages" views of the page BE module.
+* Custom BackendLayout implementations can also provide custom classes for LanguageColumn, Grid, GridRow, GridColumn and GridColumnItem instances
+ that are assigned to and used by Fluid templates to render the page layout.
+* Headers, footers and previews for content types can be created in Fluid in a way that groups
+ each of these component templates by the content type (CType) value of content records.
* Any part of the page layout can now be rendered elsewhere by creating instances of any of the "grid" objects and assigning them to Fluid templates.
* The "grid" structure of BackendLayouts can be manipulated as objects, adding and removing rows and columns on-the-fly.
-The new Fluid-based implementation is enabled by the global setting :php:`$GLOBALS['TYPO3_CONF_VARS']['SYS']['features']['fluidBasedPageModule']` which can be changed from the install tool or from extensions. The setting is enabled by default, meaning that the Fluid-based implementation is used as default method in this and future TYPO3 versions.
-The feature flag can be managed either by setting it through code (for example, in :php:`ext_localconf.php` of an extension) or you can set it through the "Settings" admin module's' "Feature Toggles" view.
+The new Fluid-based implementation is enabled by the global setting :php:`$GLOBALS['TYPO3_CONF_VARS']['SYS']['features']['fluidBasedPageModule']`
+which can be changed from the install tool or from extensions. The setting is enabled by default, meaning that the Fluid-based implementation is used
+as default method in this and future TYPO3 versions.
+The feature flag can be managed either by setting it through code (for example, in :file:`ext_localconf.php` of an extension) or you can set it through
+the "Settings" admin module's' "Feature Toggles" view.
New Fluid templates:
-* `EXT:backend/Resources/Private/Templates/PageLayout/PageLayout.html`
-* `EXT:backend/Resources/Private/Templates/PageLayout/UnusedRecords.html`
-* `EXT:backend/Resources/Private/Partials/PageLayout/Grid.html`
-* `EXT:backend/Resources/Private/Partials/PageLayout/Grid/Column.html`
-* `EXT:backend/Resources/Private/Partials/PageLayout/Record.html`
-* `EXT:backend/Resources/Private/Partials/PageLayout/Record/Header.html`
-* `EXT:backend/Resources/Private/Partials/PageLayout/Record/Footer.html`
+* :file:`EXT:backend/Resources/Private/Templates/PageLayout/PageLayout.html`
+* :file:`EXT:backend/Resources/Private/Templates/PageLayout/UnusedRecords.html`
+* :file:`EXT:backend/Resources/Private/Partials/PageLayout/Grid.html`
+* :file:`EXT:backend/Resources/Private/Partials/PageLayout/Grid/Column.html`
+* :file:`EXT:backend/Resources/Private/Partials/PageLayout/Record.html`
+* :file:`EXT:backend/Resources/Private/Partials/PageLayout/Record/Header.html`
+* :file:`EXT:backend/Resources/Private/Partials/PageLayout/Record/Footer.html`
-These Fluid templates can be overridden or extended by TS:
+These Fluid templates can be overridden or extended by TS, depending on which type or types of templates you wish to override:
* :typoscript:`module.tx_backend.view.templateRootPaths.100 = EXT:myext/Resources/Private/Templates/`
* :typoscript:`module.tx_backend.view.partialRootPaths.100 = EXT:myext/Resources/Private/Partials/`
-Depending on which type or types of templates you wish to override.
In addition, custom header/footer/preview templates can be added by extending the :typoscript:`partialRootPaths` and placing for example a template file in:
-* `EXT:myext/Resources/Private/Partials/PageLayout/Record/my_contenttype/Header`
-* `EXT:myext/Resources/Private/Partials/PageLayout/Record/my_contenttype/Footer`
-* `EXT:myext/Resources/Private/Partials/PageLayout/Record/my_contenttype/Preview`
+* :file:`EXT:myext/Resources/Private/Partials/PageLayout/Record/my_contenttype/Header`
+* :file:`EXT:myext/Resources/Private/Partials/PageLayout/Record/my_contenttype/Footer`
+* :file:`EXT:myext/Resources/Private/Partials/PageLayout/Record/my_contenttype/Preview`
-If no such templates exist the default partials (listed above) are used. Note that the folder name `my_contenttype` should use the CType value associated with the content type for which you wish to provide a custom header, footer or preview template.
+If no such templates exist the default partials (listed above) are used. Note that the folder name :file:`my_contenttype`
+should use the CType value associated with the content type for which you wish to provide a custom header, footer or preview template.
Within these last three types of templates the following variables are available:
* :html:`{item}` which represents a single record.
* :html:`{backendLayout}` which represents the :php:`BackendLayout` instance that defined the grid which was rendered.
-* :html:`{grid}` which represents the :php:`Grid` instance that was produced by the :php:`BackendLayout` (also accessible through :html:`{backendLayout.grid}`, provided as extracted variable for easier and more performance-efficient access)
+* :html:`{grid}` which represents the :php:`Grid` instance that was produced by the :php:`BackendLayout`
+ (also accessible through :html:`{backendLayout.grid}`, provided as extracted variable for easier and more performance-efficient access)
Properties on :html:`{item}` include:
@@ -77,7 +86,7 @@ Properties on :html:`{backendLayout}` include:
Impact
======
-* A new setting :php:`$GLOBALS['TYPO3_CONF_VARS']['BE']['fluidPageModule']` is introduced, enabled by default, which allows switching to the legacy :php:`PageLayoutView`.
+* A new setting :php:`$GLOBALS['TYPO3_CONF_VARS']['BE']['fluidPageModule']` has been introduced, enabled by default, which allows switching to the legacy :php:`PageLayoutView`.
* By default, a new set of objects and extended methods on :php:`BackendLayout` now provide a completely Fluid-based implementation of the "page" BE module.
.. index:: Backend, Fluid, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90370-UseEguliasEmailValidatorForEmailValidation.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90370-UseEguliasEmailValidatorForEmailValidation.rst
similarity index 81%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90370-UseEguliasEmailValidatorForEmailValidation.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90370-UseEguliasEmailValidatorForEmailValidation.rst
index c09f2f5e112e55dc610cbe4a3300bc7cdded616c..3ad0fdc93ef9fb0da9d674b24018d267cf1e1f33 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90370-UseEguliasEmailValidatorForEmailValidation.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90370-UseEguliasEmailValidatorForEmailValidation.rst
@@ -9,7 +9,7 @@ See :issue:`90370`
Description
===========
-:php:`\TYPO3\CMS\Core\Utility\GeneralUtility::validEmail` uses now the package `Egulias\EmailValidator` and the `RFCValidation` for validating the provided email address.
+:php:`\TYPO3\CMS\Core\Utility\GeneralUtility::validEmail` now uses the package `Egulias\EmailValidator` and the `RFCValidation` for validating the provided email address.
This allows to follow the RFC more closely.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90411-HTML-basedWorkspaceNotificationEmailsOnStageChange.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90411-HTML-basedWorkspaceNotificationEmailsOnStageChange.rst
similarity index 88%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90411-HTML-basedWorkspaceNotificationEmailsOnStageChange.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90411-HTML-basedWorkspaceNotificationEmailsOnStageChange.rst
index 0be1aa3393c5fa53c8e9668d9efb61b29cd3fe3a..ff0771b7250c72db290b41a471f583d19cde32cb 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90411-HTML-basedWorkspaceNotificationEmailsOnStageChange.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90411-HTML-basedWorkspaceNotificationEmailsOnStageChange.rst
@@ -10,14 +10,14 @@ Description
===========
When inside workspaces, it is possible to notify affected (or all)
-users belonging to that workspace to send out an email when
+users belonging to that workspace by sending out an email when
items have been moved to the next stage in the workflow process.
These emails have been limited in the past due to marker-based templating and plain-text only.
The emails have been reworked and migrated to Fluid-based templated
emails, allowing for administrators to customize the contents of
-these emails.
+those emails.
The following TSconfig options have been added:
@@ -31,7 +31,7 @@ The following TSconfig options have been added:
# path where to look for templates / layouts / partials
tx_workspaces.emails.layoutRootPaths.100 = EXT:myproject/...
tx_workspaces.emails.partialRootPaths.100 = EXT:myproject/...
- tx_workspaces.emails.templateRootPaths.100 = EXT:myproject/...
+ tx_workspaces.emails.templateRootPaths.100 = EXT:myproject/...
tx_workspaces.emails.format = html/text/both
The template name is always called `StageChangeNotification`.
@@ -48,6 +48,6 @@ Impact
======
Stage Change Notification emails are now sent as HTML+text by
-default with the email template given in `EXT:workspaces/Resources/Private/Templates/Emails/StageChangeNotification`.
+default with the email template given in :file:`EXT:workspaces/Resources/Private/Templates/Emails/StageChangeNotification`.
-.. index:: TSConfig, ext:workspaces
\ No newline at end of file
+.. index:: TSConfig, ext:workspaces
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90416-SpecificTargetFileExtensionInImage-relatedViewHelpers.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90416-SpecificTargetFileExtensionInImage-relatedViewHelpers.rst
similarity index 89%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90416-SpecificTargetFileExtensionInImage-relatedViewHelpers.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90416-SpecificTargetFileExtensionInImage-relatedViewHelpers.rst
index 3764b3d240c52df2bc536850ac32d51ba0deb43a..bd24ac095d58bb4b4cb830459eeb2616bc79f072 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90416-SpecificTargetFileExtensionInImage-relatedViewHelpers.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90416-SpecificTargetFileExtensionInImage-relatedViewHelpers.rst
@@ -1,7 +1,7 @@
.. include:: ../../Includes.txt
=============================================================================
-Feature: #90416 - Specific target file extension in Image-related ViewHelpers
+Feature: #90416 - Specific target file extension in image-related ViewHelpers
=============================================================================
See :issue:`90416`
@@ -9,10 +9,11 @@ See :issue:`90416`
Description
===========
-TYPO3 Core's shipped Fluid ViewHelpers now allow to optionally
+TYPO3 core's shipped Fluid ViewHelpers now allow to optionally
specify a target file extension via the new attribute `fileExtension`.
This affects the following ViewHelpers:
+
- :html:`<f:image>`
- :html:`<f:media>`
- :html:`<f:uri.image>`
@@ -40,4 +41,4 @@ Example:
<f:image image="{fileObject}" treatIdAsReference="true" alt="{fileObject.alternative}">
<picture>
-.. index:: Fluid, ext:fluid
\ No newline at end of file
+.. index:: Fluid, ext:fluid
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90425-AddSeoFieldsToInfoModule.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90425-AddSeoFieldsToInfoModule.rst
similarity index 72%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90425-AddSeoFieldsToInfoModule.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90425-AddSeoFieldsToInfoModule.rst
index 8317a061a9d3a185097bcbe2b56ef0adbefe4d58..5c896615c6d66e0119a23d974f7a76e657396265 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90425-AddSeoFieldsToInfoModule.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90425-AddSeoFieldsToInfoModule.rst
@@ -1,7 +1,7 @@
.. include:: ../../Includes.txt
===============================================
-Feature: #90425 - Add seo fields to info module
+Feature: #90425 - Add SEO fields to info module
===============================================
See :issue:`90425`
@@ -9,8 +9,8 @@ See :issue:`90425`
Description
===========
-Two more options are added to the Info module (sub-module: "Pagetree Overview")
-- "SEO" and "Social Media" to get a quick overview of the relevant data.
+Two more options are added to the Info module (sub-module: "Pagetree Overview"):
+"SEO" and "Social Media" to get a quick overview of the relevant data.
Impact
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90426-Browser-nativeLazyLoadingForImages.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90426-Browser-nativeLazyLoadingForImages.rst
similarity index 61%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90426-Browser-nativeLazyLoadingForImages.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90426-Browser-nativeLazyLoadingForImages.rst
index 66b21a7a849bcb38fd56a0c0cac5516285425b9c..bbdcb2529a15f9b0baa11488c44bc5895ad689aa 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90426-Browser-nativeLazyLoadingForImages.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90426-Browser-nativeLazyLoadingForImages.rst
@@ -9,11 +9,11 @@ See :issue:`90426`
Description
===========
-TYPO3 now supports the browser-native `loading` HTML attribute in :html:`<img>` tags.
+TYPO3 now supports the browser-native :html:`loading` HTML attribute in :html:`<img>` tags.
It is set to "lazy" by default for all images within Content Elements rendered
with Fluid Styled Content. Supported browsers then choose to load these
-images at a later point when the image is within the browsers' Viewport.
+images at a later point when the image is within the browsers' viewport.
The configuration option is available via TypoScript constants and
can be easily adjusted via the TypoScript Constant Editor in the Template module.
@@ -25,15 +25,15 @@ this property will just be skipped for unsupported browsers.
Impact
======
-TYPO3 Frontend now renders images in content elements with the "loading=lazy"
+TYPO3 Frontend now renders images in content elements with the :html:`"loading=lazy"`
attribute by default when using TYPO3's templates from Fluid Styled Content.
-Using the TypoScript constant `styles.content.image.lazyLoading`,
-the behavior can be modified generally to be either set to `eager`,
-`auto` or to an empty value, removing the property directly.
+Using the TypoScript constant :ts:`styles.content.image.lazyLoading`,
+the behavior can be modified generally to be either set to :html:`eager`,
+:html:`auto` or to an empty value, removing the property directly.
The Fluid ImageViewHelper has the possibility to set this option
-via `<f:image src="{fileObject}" treatIdAsReference="true" loading="lazy">`
+via :html:`<f:image src="{fileObject}" treatIdAsReference="true" loading="lazy">`
to hint the browser on how the prioritization of image loading should be used.
-.. index:: Frontend, ext:fluid_styled_content
\ No newline at end of file
+.. index:: Frontend, ext:fluid_styled_content
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90461-QuickCreateContentElementsViaNewContentElementWizard.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90461-QuickCreateContentElementsViaNewContentElementWizard.rst
similarity index 87%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90461-QuickCreateContentElementsViaNewContentElementWizard.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90461-QuickCreateContentElementsViaNewContentElementWizard.rst
index 9e268e564fed087aa7b29499f5129f8a88678c35..b93992eb163710308efaaccef98cd80c06b59953 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90461-QuickCreateContentElementsViaNewContentElementWizard.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90461-QuickCreateContentElementsViaNewContentElementWizard.rst
@@ -23,7 +23,7 @@ The functionality is disabled by default, but explicitly enabled for the Content
Impact
======
-This definition can be put into PageTSconfig (e.g. EXT:my_extension/Configuration/Page/main.tsconfig) with the new flag "saveAndClose" enabled.
+This definition can be put into PageTSconfig (e.g. :file:`EXT:my_extension/Configuration/Page/main.tsconfig`) with the new flag "saveAndClose" enabled.
.. code-block:: typoscript
@@ -42,4 +42,4 @@ This definition can be put into PageTSconfig (e.g. EXT:my_extension/Configuratio
}
}
-.. index:: Backend, TSConfig, ext:backend
\ No newline at end of file
+.. index:: Backend, TSConfig, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90471-JavaScriptEventAPI.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90471-JavaScriptEventAPI.rst
similarity index 98%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90471-JavaScriptEventAPI.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90471-JavaScriptEventAPI.rst
index c602abc092f3697bc9aa37cf6d8640e5b40d08c3..5eec08ea8aebfaf0607928df3b991b45d7fc856f 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90471-JavaScriptEventAPI.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90471-JavaScriptEventAPI.rst
@@ -57,13 +57,13 @@ Example:
});
The event listener is now called every time the element matching the selector
-`a[data-action="toggle"]` within :js:`document` is clicked.
+:js:`a[data-action="toggle"]` within :js:`document` is clicked.
Release an event
^^^^^^^^^^^^^^^^
-Since each event is an object instance, it's sufficient to call `release()` to
+Since each event is an object instance, it's sufficient to call :js:`release()` to
detach the event listener.
Example:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-90522-IntroduceAssetCollector.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90522-IntroduceAssetCollector.rst
similarity index 85%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-90522-IntroduceAssetCollector.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Feature-90522-IntroduceAssetCollector.rst
index 116724adf6d0535464c60d86b28c02fea5f4f954..71d1969895bd53e9564fd896f9ed1e0dcb05d85a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-90522-IntroduceAssetCollector.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Feature-90522-IntroduceAssetCollector.rst
@@ -10,12 +10,12 @@ Description
===========
AssetCollector is a concept to allow custom CSS/JS code, inline or external, to be added multiple
-times in e.g. a Fluid template (via <f:script> or <f:css> ViewHelpers) but only rendered once
+times in e.g. a Fluid template (via :html:`<f:script>` or :html:`<f:css>` ViewHelpers) but only rendered once
in the output.
It supports best practices for optimizing page performance by having a "priority" flag to either
-move the asset to the <head> section (useful for CSS in above-the-fold concepts) or to the
-bottom of the <body> tag.
+move the asset to the :html:`<head>` section (useful for CSS in above-the-fold concepts) or to the
+bottom of the :html:`<body>` tag.
AssetCollector helps to work with content elements as components, effectively reducing the amount
of CSS to be loaded. It also incorporates the HTTP/2 power where it is not relevant to have all
@@ -24,7 +24,7 @@ files compressed and concatenated in one file (although this could be added late
AssetCollector is implemented as singleton and should slowly replace the various existing options
in TypoScript.
-AssetCollector also collects information about "imagesOnPage" effectively taking off pressure from
+AssetCollector also collects information about "imagesOnPage", effectively taking off pressure from
PageRenderer and TSFE to store common data in FE - as this is now handled in AssetCollector,
which can be used in cached and non-cached components.
@@ -68,12 +68,17 @@ There are also two new ViewHelpers, the :html:`<f:asset.css>` and the - :html:`<
Examples
--------
- // Add a JavaScript file to the collector with script attribute data-foo="bar"
+Add a JavaScript file to the collector with script attribute data-foo="bar"
+
+.. code-block:: php
+
GeneralUtility::makeInstance(AssetCollector::class)
->addJavaScript('my_ext_foo', 'EXT:my_ext/Resources/Public/JavaScript/foo.js', ['data-foo' => 'bar']]);
- // Add a JavaScript file to the collector with script attribute data-foo="bar" and priority
- // which means rendering before other script tags
+Add a JavaScript file to the collector with script attribute :html:`data-foo="bar"` and priority which means rendering before other script tags
+
+.. code-block:: php
+
GeneralUtility::makeInstance(AssetCollector::class)
->addJavaScript('my_ext_foo', 'EXT:my_ext/Resources/Public/JavaScript/foo.js', ['data-foo' => 'bar'], ['priority' => true]]);
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-89672-TransOrigPointerFieldIsNotLongerAllowedToBeExcluded.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Important-89672-TransOrigPointerFieldIsNotLongerAllowedToBeExcluded.rst
similarity index 85%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-89672-TransOrigPointerFieldIsNotLongerAllowedToBeExcluded.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Important-89672-TransOrigPointerFieldIsNotLongerAllowedToBeExcluded.rst
index 92eed1182a20853fe2f256eaed0cbaf4d9189f9c..188655597a3297a7cb7945ec75f898d4d6305c65 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-89672-TransOrigPointerFieldIsNotLongerAllowedToBeExcluded.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Important-89672-TransOrigPointerFieldIsNotLongerAllowedToBeExcluded.rst
@@ -12,8 +12,8 @@ Description
The configured :php:`$GLOBALS['TCA'][$table]['ctrl']['transOrigPointerField']`
can now not longer be excluded as this leads to inconsistent data stored in the
database. This happens when a non-admin user creates a localization by not having
-the permission to edit the `transOrigPointerField`. Usually this is the
-`l10n_parent` or `l18n_parent` field.
+the permission to edit the :php:`transOrigPointerField`. Usually this is the
+:php:`l10n_parent` or :php:`l18n_parent` field.
A migration wizard is available that removes the option from your TCA and adds a
deprecation message to the deprecation log where code adaption has to take place.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-89720-OnlyTypoScriptFilesLoadedOnDirectoryImport.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Important-89720-OnlyTypoScriptFilesLoadedOnDirectoryImport.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-89720-OnlyTypoScriptFilesLoadedOnDirectoryImport.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Important-89720-OnlyTypoScriptFilesLoadedOnDirectoryImport.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-89869-ChangeLockIpDefaultToDisabled.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Important-89869-ChangeLockIpDefaultToDisabled.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-89869-ChangeLockIpDefaultToDisabled.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Important-89869-ChangeLockIpDefaultToDisabled.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-89992-UseNewTranslationServer.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Important-89992-UseNewTranslationServer.rst
similarity index 67%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-89992-UseNewTranslationServer.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Important-89992-UseNewTranslationServer.rst
index 22c43f2a6c32a1f3c41b91806e7d21aeefa7eaa0..bee9a3e84a770ef54de8c022b0fa9154fca72b11 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-89992-UseNewTranslationServer.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Important-89992-UseNewTranslationServer.rst
@@ -9,7 +9,7 @@ See :issue:`89992`
Description
===========
-The work on the new tranlation server has been finalized so that it is used by default.
+The work on the new translation server has been finalized so that it is used by default.
The SaaS solution Crowdin is being used to make it as simple as possible for everyone to improve the
localization of TYPO3 core and all extensions which are taking part.
@@ -17,13 +17,14 @@ localization of TYPO3 core and all extensions which are taking part.
If you are interested in improving the localization, register at https://crowdin.com/ and suggest translations at
the official TYPO3 Project, which can be found at https://crowdin.com/project/typo3-cms.
-The documentation about the integration is part of the official TYPO3 documentation and is available at https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/Internationalization/TranslationServer/Crowdin.html.
+The documentation about the integration is part of the official TYPO3 documentation and
+is available at https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/Internationalization/TranslationServer/Crowdin.html.
It also covers how to make your extension as extension developer available at Crowdin.
Impact
======
-The feature switch `betaTranslationServer`, introduced with :issue:`89526`,
-has been removed again and is not evaluated anymore.
+The feature switch :php:`betaTranslationServer`, introduced with :issue:`89526`,
+has been removed and is not evaluated anymore.
.. index:: Backend, Frontend, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-90020-LegacyBasicFileUtilityAndExtendedFileUtilityClassesMarkedAsInternal.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Important-90020-LegacyBasicFileUtilityAndExtendedFileUtilityClassesMarkedAsInternal.rst
similarity index 59%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-90020-LegacyBasicFileUtilityAndExtendedFileUtilityClassesMarkedAsInternal.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Important-90020-LegacyBasicFileUtilityAndExtendedFileUtilityClassesMarkedAsInternal.rst
index 9a4165268a6594d11b16555d3b05cb351f30ae1d..b270c0b0644fefc1c652492ef04964cdfe81c976 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-90020-LegacyBasicFileUtilityAndExtendedFileUtilityClassesMarkedAsInternal.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Important-90020-LegacyBasicFileUtilityAndExtendedFileUtilityClassesMarkedAsInternal.rst
@@ -9,8 +9,10 @@ See :issue:`90020`
Description
===========
-The two classes used to handle File permission and File upload logic - BasicFileUtility and ExtendedFileUtility - have been marked as internal, as TYPO3 Core now fully relies on the File Abstraction Layer, which was introduced in TYPO3 v6.0.
+The two classes used to handle File permission and File upload logic - BasicFileUtility and ExtendedFileUtility -
+have been marked as internal, as TYPO3 Core now fully relies on the File Abstraction Layer, which was introduced in TYPO3 v6.0.
-The remaining parts are partially in use and will be phased out, for the time being all extension authors should rely in ResourceStorage, and ResourceFactory for managing assets.
+The remaining parts are partially in use and will be phased out, for the time being all
+extension authors should rely on :php:`ResourceStorage` and :php:`ResourceFactory` for managing assets.
-.. index:: FAL, ext:core
\ No newline at end of file
+.. index:: FAL, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-90236-RespectExtensionStateExcludeFromUpdatesDuringLanguageUpdates.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Important-90236-RespectExtensionStateExcludeFromUpdatesDuringLanguageUpdates.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-90236-RespectExtensionStateExcludeFromUpdatesDuringLanguageUpdates.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Important-90236-RespectExtensionStateExcludeFromUpdatesDuringLanguageUpdates.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-90371-TypoScriptOptionConfigcontent_from_pid_allowOutsideDomainRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Important-90371-TypoScriptOptionConfigcontent_from_pid_allowOutsideDomainRemoved.rst
similarity index 58%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-90371-TypoScriptOptionConfigcontent_from_pid_allowOutsideDomainRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.3/Important-90371-TypoScriptOptionConfigcontent_from_pid_allowOutsideDomainRemoved.rst
index 6a652eb150a39ce07347c91c0fa75b89a77e436f..0b5d61a9dcfd2cd0c6bc2be0be0546760a48a4a2 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-90371-TypoScriptOptionConfigcontent_from_pid_allowOutsideDomainRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Important-90371-TypoScriptOptionConfigcontent_from_pid_allowOutsideDomainRemoved.rst
@@ -9,11 +9,12 @@ See :issue:`90371`
Description
===========
-TYPO3's Site Handling - introduced in TYPO3 v9 - allows for defining
-multiple sites within one installation, whereas before all configuration was based on domain records. The TypoScript option `config.content_from_pid_allowOutsideDomain` was used to limit
-the page property option "Show content from this page instead" (pages.content_from_pid) to be evaluated outside of the current page
-tree which was ineffective since the usage of Site Handling.
+TYPO3's Site Handling - introduced in TYPO3 v9 - allows defining
+multiple sites within one installation, whereas before all configuration was based on domain records.
+The TypoScript option :ts:`config.content_from_pid_allowOutsideDomain` was used to limit
+the page property option "Show content from this page instead" (:ts:`pages.content_from_pid`) to be
+evaluated outside of the current page tree which was ineffective since the usage of Site Handling.
The option serves no purpose anymore and has been removed.
-.. index:: Frontend, TypoScript, ext:frontend
\ No newline at end of file
+.. index:: Frontend, TypoScript, ext:frontend
diff --git a/typo3/sysext/core/Documentation/Changelog/10.3/Index.rst b/typo3/sysext/core/Documentation/Changelog/10.3/Index.rst
new file mode 100644
index 0000000000000000000000000000000000000000..791d0c6e6b40680dacadc3cbce889d1b9036df4b
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/10.3/Index.rst
@@ -0,0 +1,51 @@
+.. include:: ../../Includes.txt
+
+10.3 Changes
+=============
+
+**Table of contents**
+
+.. contents::
+ :local:
+ :depth: 1
+
+
+Breaking Changes
+^^^^^^^^^^^^^^^^
+
+None since TYPO3 v10.0 release.
+
+.. attention::
+
+ After TYPO3 v10.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 v10.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-90019-ExtractionOfDataHandlerPagePermissionLogic.rst b/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90019-ExtractionOfDataHandlerPagePermissionLogic.rst
deleted file mode 100644
index f73fe7147b94bae46dfe14254f3f0ad2923aaece..0000000000000000000000000000000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90019-ExtractionOfDataHandlerPagePermissionLogic.rst
+++ /dev/null
@@ -1,45 +0,0 @@
-.. include:: ../../Includes.txt
-
-=====================================================================
-Deprecation: #90019 - Extraction of DataHandler page permission logic
-=====================================================================
-
-See :issue:`90019`
-
-Description
-===========
-
-A new PagePermissionAssembler class builds the page permissions, allowing to thin out certain parts of DataHandlers responsibilities.
-
-The following properties and methods within :php:`DataHandler` are now deprecated:
-- :php:`TYPO3\CMS\Core\DataHandling\DataHandler->defaultPermissions`
-- :php:`TYPO3\CMS\Core\DataHandling\DataHandler->pMap`
-- :php:`TYPO3\CMS\Core\DataHandling\DataHandler->setTSconfigPermissions()`
-- :php:`TYPO3\CMS\Core\DataHandling\DataHandler->assemblePermissions()`
-
-The methods
-- :php:`TYPO3\CMS\Core\DataHandling\DataHandler->doesRecordExist()`
-- :php:`TYPO3\CMS\Core\DataHandling\DataHandler->recordInfoWithPermissionCheck()`
-
-should only be called with integers as permission argument.
-
-
-Impact
-======
-
-Calling the mentioned methods will trigger a PHP deprecation warning but will continue to work until TYPO3 v11.0.
-
-
-Affected Installations
-======================
-
-Any TYPO3 installations that enrich page permission handling and directly access the methods or properties in DataHandler.
-
-
-Migration
-=========
-
-Ensure to use the new :php:`PagePermissionAssembler` PHP class
-which serves as a proper API for creating page records.
-
-.. index:: PHP-API, PartiallyScanned, ext:core
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90249-PackageRelatedSignalSlotsMigratedToPSR-14Events.rst b/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90249-PackageRelatedSignalSlotsMigratedToPSR-14Events.rst
deleted file mode 100644
index 6faac192a2436e7af14fdadd1cf2568cc278c08d..0000000000000000000000000000000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90249-PackageRelatedSignalSlotsMigratedToPSR-14Events.rst
+++ /dev/null
@@ -1,50 +0,0 @@
-.. include:: ../../Includes.txt
-
-============================================================================
-Deprecation: #90249 - Package related Signal Slots migrated to PSR-14 events
-============================================================================
-
-See :issue:`90249`
-
-Description
-===========
-
-The following Signal Slots have been replaced by new PSR-14 events
-which can be used as 1:1 equivalents:
-
-- :php:`PackageManagement::packagesMayHaveChanged`
-- :php:`TYPO3\CMS\Extensionmanager\Utility\InstallUtility::afterExtensionInstall`
-- :php:`TYPO3\CMS\Extensionmanager\Utility\InstallUtility::afterExtensionUninstall`
-- :php:`TYPO3\CMS\Extensionmanager\Utility\InstallUtility::afterExtensionT3DImport`
-- :php:`TYPO3\CMS\Extensionmanager\Utility\InstallUtility::afterExtensionStaticSqlImport`
-- :php:`TYPO3\CMS\Extensionmanager\Utility\InstallUtility::afterExtensionFileImport`
-- :php:`TYPO3\CMS\Extensionmanager\Service\ExtensionManagementService::willInstallExtensions`
-- :php:`TYPO3\CMS\Extensionmanager\ViewHelper\ProcessAvailableActionsViewHelper::processActions`
-
-Impact
-======
-
-Using the mentioned signals will trigger a deprecation warning.
-
-
-Affected Installations
-======================
-
-TYPO3 installations with custom extensions using these signals.
-
-
-Migration
-=========
-
-Use the new PSR-14 alternatives:
-
-- :php:`TYPO3\CMS\Core\Package\Event\PackagesMayHaveChangedEvent`
-- :php:`TYPO3\CMS\Core\Package\Event\AfterPackageActivationEvent`
-- :php:`TYPO3\CMS\Core\Package\Event\AfterPackageDeactivationEvent`
-- :php:`TYPO3\CMS\Core\Package\Event\BeforePackageActivationEvent`
-- :php:`TYPO3\CMS\Extensionmanager\Event\AfterExtensionDatabaseContentHasBeenImportedEvent`
-- :php:`TYPO3\CMS\Extensionmanager\Event\AfterExtensionStaticDatabaseContentHasBeenImportedEvent`
-- :php:`TYPO3\CMS\Extensionmanager\Event\AfterExtensionFilesHaveBeenImportedEvent`
-- :php:`TYPO3\CMS\Extensionmanager\Event\AvailableActionsForExtensionEvent`
-
-.. index:: PHP-API, FullyScanned, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90348-PageLayoutViewClassInternalIsDeprecated.rst b/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90348-PageLayoutViewClassInternalIsDeprecated.rst
deleted file mode 100644
index b3453af73054351f928e2e4958186ebca9724d6e..0000000000000000000000000000000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90348-PageLayoutViewClassInternalIsDeprecated.rst
+++ /dev/null
@@ -1,34 +0,0 @@
-.. include:: ../../Includes.txt
-
-===================================================================
-Deprecation: #90348 - PageLayoutView class (internal) is deprecated
-===================================================================
-
-See :issue:`90348`
-
-Description
-===========
-
-The :php:`PageLayoutView` class, which is considered internal API, has been deprecated in favor of the new Fluid-based alternative which renders the "page" BE module.
-
-
-Impact
-======
-
-Implementations which depend on :php:`PageLayoutView` should prepare to use the alternative implementation (by overlaying and overriding Fluid templates of EXT:backend).
-
-
-Affected Installations
-======================
-
-* Any site which overrides the ``PageLayoutView`` class. The overridden class will still be instanced when rendering previews in BE page module - but no methods will be called on the instance **unless** they are called by a third party hook subscriber.
-* Any site which depends on PSR-14 events associated with ``PageLayoutView`` will only have those events dispatched if the ``fluidBasedPageModule`` feature flag is ``false``.
- * Affects ``\TYPO3\CMS\Backend\View\Event\AfterSectionMarkupGeneratedEvent``.
- * Affects ``\TYPO3\CMS\Backend\View\Event\BeforeSectionMarkupGeneratedEvent``.
-
-Migration
-=========
-
-Fluid templates can be extended or replaced to render custom header, footer or preview of a given :php:`CType`, see feature description for feature 90348.
-
-.. index:: Backend, Fluid, NotScanned, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-89551-AddFluidAdditionalAttributesToTheFormElement.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-89551-AddFluidAdditionalAttributesToTheFormElement.rst
deleted file mode 100644
index b442a88372b0b6387205eaac7b09ea1de84fcba8..0000000000000000000000000000000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-89551-AddFluidAdditionalAttributesToTheFormElement.rst
+++ /dev/null
@@ -1,31 +0,0 @@
-.. include:: ../../Includes.txt
-
-===================================================================
-Feature: #89551 - Add fluidAdditionalAttributes to the form element
-===================================================================
-
-See :issue:`89551`
-
-Description
-===========
-
-Allows to configure fluidAdditionalAttributes within form element:
-`TYPO3:
- CMS:
- Form:
- prototypes:
- standard:
- formElementsDefinition:
- Form:
- renderingOptions:
- fluidAdditionalAttributes:
- novalidate: 'novalidate'
-
-
-Impact
-======
-
-For projects using it's own Form template, the following attribute can be set on viewhelper formvh:form as attribute:
-`additionalAttributes="{formvh:translateElementProperty(element: form, property: 'fluidAdditionalAttributes')}"`
-
-.. index:: Fluid, ext:form
diff --git a/typo3/sysext/install/Configuration/ExtensionScanner/Php/MethodCallMatcher.php b/typo3/sysext/install/Configuration/ExtensionScanner/Php/MethodCallMatcher.php
index 1f0cf4973a1a3f28e3249d3ba73bcbca3aa7700a..cf8af3f0d4bfb25d8a65d7d7789177557dc7816e 100644
--- a/typo3/sysext/install/Configuration/ExtensionScanner/Php/MethodCallMatcher.php
+++ b/typo3/sysext/install/Configuration/ExtensionScanner/Php/MethodCallMatcher.php
@@ -4382,14 +4382,14 @@ return [
'numberOfMandatoryArguments' => 2,
'maximumNumberOfArguments' => 2,
'restFiles' => [
- 'Deprecation-90019-ExtractionOfDataHandlerPagePermissionLogic.rst',
+ 'Deprecation-90019-PagePermissionLogicByDataHandler.rst',
],
],
'TYPO3\CMS\Core\DataHandling\DataHandler->assemblePermissions' => [
'numberOfMandatoryArguments' => 1,
'maximumNumberOfArguments' => 1,
'restFiles' => [
- 'Deprecation-90019-ExtractionOfDataHandlerPagePermissionLogic.rst',
+ 'Deprecation-90019-PagePermissionLogicByDataHandler.rst',
],
],
'TYPO3\CMS\Core\Utility\File\BasicFileUtility->setFileExtensionPermissions' => [
@@ -4425,7 +4425,7 @@ return [
'maximumNumberOfArguments' => 0,
'restFiles' => [
'Feature-89139-AddDependencyInjectionSupportForConsoleCommands.rst',
- 'Deprecation-89139-ConsoleCommandsConfigurationMigratedToSymfonyServiceTags.rst',
+ 'Deprecation-89139-ConsoleCommandsConfigurationFormatCommandsPhp.rst',
],
],
];
diff --git a/typo3/sysext/install/Configuration/ExtensionScanner/Php/PropertyPublicMatcher.php b/typo3/sysext/install/Configuration/ExtensionScanner/Php/PropertyPublicMatcher.php
index eccc021f0717a1ed09018ea6cea1c39441024f21..6b688c67d1f3330893d97f4da00ff6bb249a85a1 100644
--- a/typo3/sysext/install/Configuration/ExtensionScanner/Php/PropertyPublicMatcher.php
+++ b/typo3/sysext/install/Configuration/ExtensionScanner/Php/PropertyPublicMatcher.php
@@ -648,12 +648,12 @@ return [
],
'TYPO3\CMS\Core\DataHandling\DataHandler->defaultPermissions' => [
'restFiles' => [
- 'Deprecation-90019-ExtractionOfDataHandlerPagePermissionLogic.rst',
+ 'Deprecation-90019-PagePermissionLogicByDataHandler.rst',
],
],
'TYPO3\CMS\Core\DataHandling\DataHandler->pMap' => [
'restFiles' => [
- 'Deprecation-90019-ExtractionOfDataHandlerPagePermissionLogic.rst',
+ 'Deprecation-90019-PagePermissionLogicByDataHandler.rst',
],
],
];