From 85ea10b2b9fd90206b81e5e60d07f47cf20d2243 Mon Sep 17 00:00:00 2001
From: Sybille Peters <sypets@gmx.de>
Date: Sun, 22 Mar 2020 07:46:31 +0100
Subject: [PATCH] [DOCS] Fix formatting in .rst files
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Lists must always be preceeded and followed by a newline. Otherwise
they will not get rendered correctly.
Resolves: #90805
Releases: master, 9.5, 8.7
Change-Id: I558e486ef556be41bb27873af8d0d67a448064f4
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63837
Tested-by: TYPO3com <noreply@typo3.com>
Tested-by: Daniel Haupt <mail@danielhaupt.de>
Tested-by: Björn Jacob <bjoern.jacob@tritum.de>
Tested-by: Daniel Goerz <daniel.goerz@posteo.de>
Reviewed-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Reviewed-by: Daniel Haupt <mail@danielhaupt.de>
Reviewed-by: Björn Jacob <bjoern.jacob@tritum.de>
Reviewed-by: Daniel Goerz <daniel.goerz@posteo.de>
---
.../Breaking-87193-DeprecatedFunctionalityRemoved.rst | 1 +
...king-87305-UseConstructorInjectionInDataMapper.rst | 1 +
...77-FALSignalSlotHandlingMigratedToPSR-14Events.rst | 2 ++
.../7.0/Deprecation-60574-ClientRelatedConditions.rst | 1 +
.../Feature-63207-SplitActionButtonsIntoGroups.rst | 1 +
...re-22175-SupportIecSiUnitsInFileSizeFormatting.rst | 1 +
.../7.4/Feature-67293-DependencyOrderingService.rst | 1 +
...oFormMailPostProcessorAndIntroduceReplyToEmail.rst | 1 +
...ndTStemplateSoftReferencesFunctionalityRemoved.rst | 1 +
...622-RemovalOfFluidStyledContentMenuViewHelpers.rst | 1 +
...9-IntroduceTranslationSourceFieldForTt_content.rst | 1 +
...re-79263-SchedulerCLIAvailableAsSymfonyCommand.rst | 1 +
...5361-EXTrte_ckeditor-Re-addTheSoftHyphenButton.rst | 2 ++
.../Deprecation-83252-Link-tagSyntaxProcesssing.rst | 4 +++-
...ortant-81201-TCAPopulatedAvailableAtAnyRequest.rst | 7 ++++---
...precation-85125-UsagesOfCharsetConverterInCore.rst | 4 +++-
...ture-85389-ContextAPIForConsistentDataHandling.rst | 5 +++--
...ure-86066-CLICommandsForListingAndShowingSites.rst | 1 +
.../Feature-86331-NativeURLSupportForMountPoints.rst | 11 ++++++-----
.../Deprecation-90625-ExtbaseSignalSlotDispatcher.rst | 8 ++++----
.../Feature-89513-PasswordResetForBackendUsers.rst | 5 +++++
21 files changed, 44 insertions(+), 16 deletions(-)
diff --git a/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87193-DeprecatedFunctionalityRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87193-DeprecatedFunctionalityRemoved.rst
index 8ab41efc9524..885d80de510d 100644
--- a/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87193-DeprecatedFunctionalityRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87193-DeprecatedFunctionalityRemoved.rst
@@ -1416,6 +1416,7 @@ The following hooks don't pass the class reference anymore:
The following signals have been removed:
+
* :php:`TYPO3\CMS\Extensionmanager\Service\ExtensionManagementService` signal `hasInstalledExtensions`
* :php:`TYPO3\CMS\Extensionmanager\Utility\InstallUtility` signal `tablesDefinitionIsBeingBuilt`
diff --git a/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87305-UseConstructorInjectionInDataMapper.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87305-UseConstructorInjectionInDataMapper.rst
index de5bb71222cd..24e9bd2059ff 100644
--- a/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87305-UseConstructorInjectionInDataMapper.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87305-UseConstructorInjectionInDataMapper.rst
@@ -16,6 +16,7 @@ Impact
======
The method signature of the constructor changed. This means:
+
- The amount of constructor arguments increased
- The order of arguments possibly changed
diff --git a/typo3/sysext/core/Documentation/Changelog/10.2/Deprecation-89577-FALSignalSlotHandlingMigratedToPSR-14Events.rst b/typo3/sysext/core/Documentation/Changelog/10.2/Deprecation-89577-FALSignalSlotHandlingMigratedToPSR-14Events.rst
index 0b99493ddd76..0681322b59f2 100644
--- a/typo3/sysext/core/Documentation/Changelog/10.2/Deprecation-89577-FALSignalSlotHandlingMigratedToPSR-14Events.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.2/Deprecation-89577-FALSignalSlotHandlingMigratedToPSR-14Events.rst
@@ -15,9 +15,11 @@ For this reason, all FAL-related Signals have been migrated to PSR-14 event list
first listener to be executed when an Event is fired.
The following interface has been deprecated and will be removed in TYPO3 v11:
+
- :php:`\TYPO3\CMS\Core\Resource\ResourceFactoryInterface`
The following constants have been deprecated and will be removed in TYPO3 v11:
+
- :php:`\TYPO3\CMS\Core\Resource\ResourceFactoryInterface::SIGNAL_PreProcessStorage`
- :php:`\TYPO3\CMS\Core\Resource\ResourceFactoryInterface::SIGNAL_PostProcessStorage`
- :php:`\TYPO3\CMS\Core\Resource\ResourceStorageInterface::SIGNAL_PostFileAdd`
diff --git a/typo3/sysext/core/Documentation/Changelog/7.0/Deprecation-60574-ClientRelatedConditions.rst b/typo3/sysext/core/Documentation/Changelog/7.0/Deprecation-60574-ClientRelatedConditions.rst
index 2484e60175b1..fa63dec61d1a 100644
--- a/typo3/sysext/core/Documentation/Changelog/7.0/Deprecation-60574-ClientRelatedConditions.rst
+++ b/typo3/sysext/core/Documentation/Changelog/7.0/Deprecation-60574-ClientRelatedConditions.rst
@@ -35,6 +35,7 @@ Installations using TypoScript conditions for browser, version, system or userag
Migration
=========
+
* Most usual conditions for specific browsers can nowadays be turned into conditional CSS includes
* Use libraries such as modernizr for browser support
* If conditions for specific clients or devices are still needed, they
diff --git a/typo3/sysext/core/Documentation/Changelog/7.1/Feature-63207-SplitActionButtonsIntoGroups.rst b/typo3/sysext/core/Documentation/Changelog/7.1/Feature-63207-SplitActionButtonsIntoGroups.rst
index a513a29d234d..840eddbc3343 100644
--- a/typo3/sysext/core/Documentation/Changelog/7.1/Feature-63207-SplitActionButtonsIntoGroups.rst
+++ b/typo3/sysext/core/Documentation/Changelog/7.1/Feature-63207-SplitActionButtonsIntoGroups.rst
@@ -12,6 +12,7 @@ Description
The action buttons in Web>List for pages and content elements have been split into two groups to organize
the actions as primary and secondary actions. Primary actions are common RUD actions:
+
- Show
- Edit
- Hide
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-22175-SupportIecSiUnitsInFileSizeFormatting.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-22175-SupportIecSiUnitsInFileSizeFormatting.rst
index 332aa523d2b8..998c0f2f47d6 100644
--- a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-22175-SupportIecSiUnitsInFileSizeFormatting.rst
+++ b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-22175-SupportIecSiUnitsInFileSizeFormatting.rst
@@ -11,6 +11,7 @@ Description
===========
Size formatting supports two keywords additionally to the list of labels:
+
- iec: uses the Ki, Mi, etc prefixes and binary base (power of two, 1024)
- si: uses the k, M, etc prefixes and decimal base (power of ten, 1000)
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67293-DependencyOrderingService.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67293-DependencyOrderingService.rst
index 237999acb88b..b7e9a84abc0e 100644
--- a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67293-DependencyOrderingService.rst
+++ b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67293-DependencyOrderingService.rst
@@ -14,6 +14,7 @@ In many cases it is necessary to establish a sorted list of items from a set of
The ordered list is then used to execute actions in the given order.
Some examples from the Core are:
+
- Hook execution order
- Extension loading order
- Listing of menu items
diff --git a/typo3/sysext/core/Documentation/Changelog/7.6/Feature-68771-AddContentObjectFunctionalityToFormMailPostProcessorAndIntroduceReplyToEmail.rst b/typo3/sysext/core/Documentation/Changelog/7.6/Feature-68771-AddContentObjectFunctionalityToFormMailPostProcessorAndIntroduceReplyToEmail.rst
index ce8d5e195093..5c989aafc771 100644
--- a/typo3/sysext/core/Documentation/Changelog/7.6/Feature-68771-AddContentObjectFunctionalityToFormMailPostProcessorAndIntroduceReplyToEmail.rst
+++ b/typo3/sysext/core/Documentation/Changelog/7.6/Feature-68771-AddContentObjectFunctionalityToFormMailPostProcessorAndIntroduceReplyToEmail.rst
@@ -12,6 +12,7 @@ Description
If the form configuration is defined by TypoScript the following items for the MailPostProcessor
in ext:form have contentObject functionality now:
+
- subject
- senderEmail
- senderName
diff --git a/typo3/sysext/core/Documentation/Changelog/8.3/Breaking-77156-TSconfigAndTStemplateSoftReferencesFunctionalityRemoved.rst b/typo3/sysext/core/Documentation/Changelog/8.3/Breaking-77156-TSconfigAndTStemplateSoftReferencesFunctionalityRemoved.rst
index 72ec09efb8ae..bb7249d7f84c 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.3/Breaking-77156-TSconfigAndTStemplateSoftReferencesFunctionalityRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.3/Breaking-77156-TSconfigAndTStemplateSoftReferencesFunctionalityRemoved.rst
@@ -21,6 +21,7 @@ anymore that are not based on the File Abstraction Layer.
The public PHP property :php:`SoftReferenceIndex::$fileAdminDir` has been removed.
The following PHP methods has been removed without substitution:
+
- :php:`SoftReferenceIndex::findRef_TStemplate()`
- :php:`SoftReferenceIndex::findRef_TSconfig()`
- :php:`SoftReferenceIndex::fileadminReferences()`
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-RemovalOfFluidStyledContentMenuViewHelpers.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-RemovalOfFluidStyledContentMenuViewHelpers.rst
index 6778ccaea3d1..1fa4912018ad 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-RemovalOfFluidStyledContentMenuViewHelpers.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-RemovalOfFluidStyledContentMenuViewHelpers.rst
@@ -17,6 +17,7 @@ Menu ViewHelpers have been moved to the `compatibility7` extension, and are
replaced in the core menu content elements.
List of removed ViewHelpers:
+
- menu.categories
- menu.directory
- menu.keywords
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78169-IntroduceTranslationSourceFieldForTt_content.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78169-IntroduceTranslationSourceFieldForTt_content.rst
index 3457f34aa9a2..2423fe37f51e 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78169-IntroduceTranslationSourceFieldForTt_content.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78169-IntroduceTranslationSourceFieldForTt_content.rst
@@ -51,6 +51,7 @@ Impact
======
Introduction of the new field is a base step for further refactorings, e.g.
+
- it opens a way to implement features like "reconnecting" free-mode translations back to the "connected mode"
- replace usage of the `t3_origuid` with the `l10n_source` where `t3_origuid` is misused for language handling purposes (e.g. in LocalizationRepository)
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79263-SchedulerCLIAvailableAsSymfonyCommand.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79263-SchedulerCLIAvailableAsSymfonyCommand.rst
index ccccb73ba542..1ed5079fcd18 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79263-SchedulerCLIAvailableAsSymfonyCommand.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79263-SchedulerCLIAvailableAsSymfonyCommand.rst
@@ -13,6 +13,7 @@ Calling the scheduler to process a task is now callable via CLI through `typo3/c
`typo3/sysext/core/bin/typo3 scheduler:run`.
The following aliases for the scheduler options are now available:
+
* `--task=13` or `--task 13` as synonym to `-i 13` to run a specific task
* `--force` as synonym to `-f` to force to run a specific task in combination with `--task` or `-i`
* `--stop` as synonym to `-s` to stop a specific task in combination with `--task` or `-i`
diff --git a/typo3/sysext/core/Documentation/Changelog/8.7.x/Important-85361-EXTrte_ckeditor-Re-addTheSoftHyphenButton.rst b/typo3/sysext/core/Documentation/Changelog/8.7.x/Important-85361-EXTrte_ckeditor-Re-addTheSoftHyphenButton.rst
index 0e64f3aba275..7368e6869e64 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.7.x/Important-85361-EXTrte_ckeditor-Re-addTheSoftHyphenButton.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.7.x/Important-85361-EXTrte_ckeditor-Re-addTheSoftHyphenButton.rst
@@ -49,10 +49,12 @@ The button with the buttonName `softHyphen` of the plugin is assigned to a toolb
use the toolbarGroup or the buttonName to display the button at the desired location in the toolbar.
Please take look into the supplied RTE presets to see working examples:
+
- :file:`EXT:rte_ckeditor/Configuration/RTE/Default.yaml`
- :file:`EXT:rte_ckeditor/Configuration/RTE/Full.yaml`
More information can be found in the official CKEditor 4 documentation (toolbar concepts):
+
- https://docs.ckeditor.com/ckeditor4/latest/guide/dev_toolbarconcepts.html
.. index:: RTE, ext:rte_ckeditor
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-83252-Link-tagSyntaxProcesssing.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-83252-Link-tagSyntaxProcesssing.rst
index 8952499d51cd..486b6fc021a4 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-83252-Link-tagSyntaxProcesssing.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-83252-Link-tagSyntaxProcesssing.rst
@@ -13,10 +13,12 @@ The old-fashioned way of storing links as <link>-tags in the database was migrat
is still in place.
Using the following hooks is not encouraged:
+
- :php:`$TYPO3_CONF_VARS['SC_OPTIONS']['t3lib/class.t3lib_parsehtml_proc.php']['modifyParams_LinksRte_PostProc']`
- :php:`$TYPO3_CONF_VARS['SC_OPTIONS']['t3lib/class.t3lib_parsehtml_proc.php']['modifyParams_LinksDb_PostProc']`
The following public methods in RteHtmlParser have been marked as deprecated:
+
- :php:`TYPO3\CMS\Core\Html\RteHtmlParser->TS_links_rte()`
- :php:`TYPO3\CMS\Core\Html\RteHtmlParser->transformStyledATags()`
@@ -44,4 +46,4 @@ Migration
Migrate all content to proper anchor-tags, so the hooks are not necessary anymore.
-.. index:: PHP-API, RTE, FullyScanned
\ No newline at end of file
+.. index:: PHP-API, RTE, FullyScanned
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Important-81201-TCAPopulatedAvailableAtAnyRequest.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Important-81201-TCAPopulatedAvailableAtAnyRequest.rst
index d62fdb7b8a92..5e831e7a24ff 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Important-81201-TCAPopulatedAvailableAtAnyRequest.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Important-81201-TCAPopulatedAvailableAtAnyRequest.rst
@@ -17,12 +17,13 @@ This is possible since TYPO3 v8, because TCA compiling is now completely separat
:php:`TypoScriptFrontendController`) in the frontend.
This leads to the following changes in behaviour:
+
- TCA compilation is done earlier in the request process. It is handled after :file:`ext_localconf.php` is
-evaluated, but before any further hooks are executed.
+ evaluated, but before any further hooks are executed.
- The full TCA is available even when evaluating any RequestHandler.
- The global variable $TCA is now available at the very beginning of an eID request, it is not
-necessary to load TCA via :php:`EidUtility::loadTCA()` anymore.
+ necessary to load TCA via :php:`EidUtility::loadTCA()` anymore.
Side Note: This does not affect the install tool as it does a custom set-up of the TYPO3 Bootstrap.
-.. index:: PHP-API, TCA
\ No newline at end of file
+.. index:: PHP-API, TCA
diff --git a/typo3/sysext/core/Documentation/Changelog/9.3/Deprecation-85125-UsagesOfCharsetConverterInCore.rst b/typo3/sysext/core/Documentation/Changelog/9.3/Deprecation-85125-UsagesOfCharsetConverterInCore.rst
index bd6699dc4f73..a21440136389 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.3/Deprecation-85125-UsagesOfCharsetConverterInCore.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.3/Deprecation-85125-UsagesOfCharsetConverterInCore.rst
@@ -10,9 +10,11 @@ Description
===========
The following method has been marked as deprecated:
+
- :php:`TYPO3\CMS\Core\Resource\Driver\AbstractHierarchicalFilesystemDriver->getCharsetConversion()`
The following public properties have been deprecated:
+
- :php:`TYPO3\CMS\IndexedSearch\Lexer->csObj`
- :php:`TYPO3\CMS\IndexedSearch\Indexer->csObj`
@@ -36,4 +38,4 @@ Migration
Check the extension scanner if the site is affected and instantiate CharsetConverter directly in the
callers' code.
-.. index:: PHP-API, FullyScanned
\ No newline at end of file
+.. index:: PHP-API, FullyScanned
diff --git a/typo3/sysext/core/Documentation/Changelog/9.4/Feature-85389-ContextAPIForConsistentDataHandling.rst b/typo3/sysext/core/Documentation/Changelog/9.4/Feature-85389-ContextAPIForConsistentDataHandling.rst
index 6024dc12e850..70411af4f805 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.4/Feature-85389-ContextAPIForConsistentDataHandling.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.4/Feature-85389-ContextAPIForConsistentDataHandling.rst
@@ -106,11 +106,12 @@ However, if custom DB queries need to be made, it is strongly recommended to clo
As a rule of thumb:
+
- If new code is written that depends on external factors for querying data, ensure that a context object
-can be handed in via e.g. the constructor.
+ can be handed in via e.g. the constructor.
- If you are sure, that the consuming class is NOT altering the context object, the main context object can be used
- If the consuming class, e.g. ContentObjectRenderer is altering the context object, it is recommended to hand in a clone
-of a context.
+ of a context.
Further development
===================
diff --git a/typo3/sysext/core/Documentation/Changelog/9.4/Feature-86066-CLICommandsForListingAndShowingSites.rst b/typo3/sysext/core/Documentation/Changelog/9.4/Feature-86066-CLICommandsForListingAndShowingSites.rst
index 90c71fa4d4d7..217a3c8584a4 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.4/Feature-86066-CLICommandsForListingAndShowingSites.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.4/Feature-86066-CLICommandsForListingAndShowingSites.rst
@@ -10,6 +10,7 @@ Description
===========
Two new CLI commands have been added:
+
- :shell:`site:list`
- :shell:`site:show`
diff --git a/typo3/sysext/core/Documentation/Changelog/9.5.x/Feature-86331-NativeURLSupportForMountPoints.rst b/typo3/sysext/core/Documentation/Changelog/9.5.x/Feature-86331-NativeURLSupportForMountPoints.rst
index 38357ac5626f..f69334890bbc 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.5.x/Feature-86331-NativeURLSupportForMountPoints.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.5.x/Feature-86331-NativeURLSupportForMountPoints.rst
@@ -12,8 +12,9 @@ Description
MountPoints allow TYPO3 editors to mount a page (and its subpages) from a different area of the site in the current page tree.
The definitions are as follows:
+
- MountPoint Page: A page with doktype=7 - a page pointing to a different page ("web mount")
-that should act as replacement for this page and possible descendants.
+ that should act as replacement for this page and possible descendants.
- Mounted Page a.k.a. "Mount Target": A regular page containing content and subpages.
The idea behind it is to manage content only once and "link" / "mount" to a tree to be used
@@ -57,12 +58,12 @@ Impact
Limitations:
1. Multi-language support
-Please be aware that multi-language setups are supported in general, but this would only fit if both sites support the same language IDs.
+ Please be aware that multi-language setups are supported in general, but this would only fit if both sites support the same language IDs.
2. Slug uniqueness when using Multi-Site setups cannot be ensured
-If a MountPoint Page has the slug "/more", mounting a page with "/imprint" subpage, but the MountPoint Page
-has a regular sibling page with "/more/imprint" a collision cannot be detected, whereas the non-mounted page
-would always work and a subpage of a Mounted Page would never be reached.
+ If a MountPoint Page has the slug "/more", mounting a page with "/imprint" subpage, but the MountPoint Page
+ has a regular sibling page with "/more/imprint" a collision cannot be detected, whereas the non-mounted page
+ would always work and a subpage of a Mounted Page would never be reached.
For the sake of completeness, please consider the TYPO3 documentation on the following TypoScript properties related to mount points:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90625-ExtbaseSignalSlotDispatcher.rst b/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90625-ExtbaseSignalSlotDispatcher.rst
index 91e030fc54b0..a88af0a09ba7 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90625-ExtbaseSignalSlotDispatcher.rst
+++ b/typo3/sysext/core/Documentation/Changelog/master/Deprecation-90625-ExtbaseSignalSlotDispatcher.rst
@@ -21,12 +21,12 @@ Since March 2019, a new standards recommendation in PHP - PSR-14 - was put into
in TYPO3 v10.0. TYPO3's PSR-14 implementation has several advantages over SignalSlot:
* All Events ("Signals" in Extbase world) are actual PHP objects that clearly define what can
-be read or modified.
+ be read or modified.
* All Events are registered at compile-time (inside the Service Container), so the Listeners
-("Slots" in Extbase world) are defined in one place and are always available. Previously the
-registration of the slots was done in :php:`ext_localconf.php`.
+ ("Slots" in Extbase world) are defined in one place and are always available. Previously the
+ registration of the slots was done in :php:`ext_localconf.php`.
* Events can be used across other PHP projects as well, and the EventDispatcher can be the same
-instance, as it is a standards recommendation.
+ instance, as it is a standards recommendation.
In TYPO3 v10, all Extbase signals provided by TYPO3 Core have been migrated to PSR-14 events.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-89513-PasswordResetForBackendUsers.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-89513-PasswordResetForBackendUsers.rst
index 6893e4b67e91..4bbee002094a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-89513-PasswordResetForBackendUsers.rst
+++ b/typo3/sysext/core/Documentation/Changelog/master/Feature-89513-PasswordResetForBackendUsers.rst
@@ -15,6 +15,7 @@ Login form.
The reset link is only shown if there is at least one user that matches the
following criteria:
+
* The user has a password entered previously (used to indicate that no third-party login was used)
* The user has a valid email added to his user record
* The user is neither deleted nor disabled
@@ -28,6 +29,7 @@ The link is valid for 2 hours, and a token is added to the link.
If the password was provided correctly, it is updated for the user and can log-in.
Some notes on security:
+
+ When having multiple users with the same email address
+ No information disclosure is built-in, so if the email address is not in the system, it is not known to the outside
+ Rate limiting is activated for allowing three emails to be sent within 30 minutes per email address
@@ -54,6 +56,8 @@ need to send a password over the wire in plaintext (e.g. email) to a user.
The administrator can use the CLI command:
+.. code-block:: bash
+
./typo3/sysext/core/bin/typo3 backend:resetpassword https://www.example.com/typo3/ editor@example.com
Alternatively it is possible for administrators to use the "Backend users" module
@@ -73,6 +77,7 @@ In addition, the email can be styled completely for HTML and plain-text only
versions through the Fluid-based templated email feature.
Further improvements on the horizon:
+
* Trigger a password-reset via CLI or the Backend users module
* Trigger a password-set email on creation of a new user, so the admin has no
involvement in needing to know or share the password
--
GitLab