From ed744d551a5390e906dabba41f4ddd79175cac67 Mon Sep 17 00:00:00 2001
From: Mathias Schreiber <mathias.schreiber@typo3.com>
Date: Sun, 12 Feb 2017 16:22:10 +0100
Subject: [PATCH] [DOCS] 8.6 Documentation
Update and proofread 8.6 docs
Resolves:
Change-Id: Ie6cf569ad331f97637cc01901e689db22abeae05
Reviewed-on: https://review.typo3.org/51641
Reviewed-by: Susanne Moog <susanne.moog@typo3.org>
Tested-by: Susanne Moog <susanne.moog@typo3.org>
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Benni Mack <benni@typo3.org>
Tested-by: Benni Mack <benni@typo3.org>
---
...nPropertiesAndMethodsDroppedAndChanged.rst | 6 +-
...moveSelectKeyFromContentElementPreview.rst | 0
...ing-78192-RefactorClickMenuContextMenu.rst | 34 ++---
...77-InheritanceOfFlashMessageViewHelper.rst | 2 +-
...7-RemoveFlashMessageGetMessageAsMarkup.rst | 0
...moveExtJsCodeFromFormEngineResultArray.rst | 2 +-
...moveMethodsHookAndPropertyInFormEngine.rst | 4 +-
...-RemoveOptionalFluidTyposcriptTemplate.rst | 2 +-
...-79025-ExtractTestingFrameworkForTYPO3.rst | 0
...Breaking-79100-FeloginRemoveDefaultCss.rst | 0
...wlevelVersionsCommandParametersChanged.rst | 0
...dLegacyCliRelatedConstantsAndVariables.rst | 0
...-79196-ToolbarItemEventHandlingChanged.rst | 4 +-
...g-79201-ExtFormSplitTyposcriptIncludes.rst | 2 +-
...ng-79227-RemovedExtDirectStateProvider.rst | 0
...oveExtJSPagetreeIndicatorFunctionality.rst | 0
.../Breaking-79242-RemoveL10n_modeNoCopy.rst | 8 +-
...g-79243-RemoveL10n_modeMergeIfNotBlank.rst | 6 +-
...RemoveSys_language_softMergeIfNotBlank.rst | 4 +-
.../Breaking-79259-RemoveExtt3skin.rst | 0
...263-SchedulerCLIControllerClassRemoved.rst | 0
...ProcessingOptionDisableUnifyLineBreaks.rst | 7 +-
...-79273-RemovedRteHtmlParserProcOptions.rst | 2 +-
...TEProctransformBoldAndItalicTagsOption.rst | 4 +-
...agesurlSchemeToCompatibility7Extension.rst | 0
...iCode-VCParameterIsNotEvaluatedAnyMore.rst | 8 +-
...oduleFunctionQuickEditToCompatibility7.rst | 2 +-
...ng-79464-ExtFormRefactorFluidRendering.rst | 133 ++++++++++++++++++
...-RemovedSessionLockingBasedOnUseragent.rst | 0
...dContentTableContentElementAdjustments.rst | 4 +-
...79622-DedicatedContentElementsForMenus.rst | 2 +-
...entElementChangedForFluidStyledContent.rst | 2 +-
...ultLayoutsForFluidStyledContentChanged.rst | 0
...ingThumbnailConfigurationForTt_content.rst | 4 +-
...valOfFluidStyledContentMenuViewHelpers.rst | 10 +-
...aceAfterAdjustmentsForCSSStyledContent.rst | 24 ++--
...fCSSStyledContentAndFluidStyledContent.rst | 4 +-
...91-PageRepositoryShouldFieldBeOverlaid.rst | 0
...precation-70316-FrontendBasketWithRecs.rst | 6 +-
...934-DeprecateTt_contentFieldSelect_key.rst | 0
...-LegacyPreparedStatementsWithinExtbase.rst | 0
...477-RefactoringOfFlashMessageRendering.rst | 2 +-
.../Deprecation-78899-FormEngineMethods.rst | 16 +--
...78899-TCACtrlFieldRequestUpdateDropped.rst | 0
...-79258-MethodsInLocalizationRepository.rst | 0
...CommandLineControllerAndCleanerCommand.rst | 2 +-
...ion-79316-DeprecateArrayUtilityinArray.rst | 0
...stractUserAuthenticationveriCodeMethod.rst | 4 +-
...-MethodsRelatedToRichtextConfiguration.rst | 2 +-
...extConfigurationInDefaultExtrasDropped.rst | 0
...DeprecateMembersInPageLayoutController.rst | 0
.../Deprecation-79440-TcaChanges.rst | 4 +-
...angeVisibilityInternalCacheDatahandler.rst | 20 +--
...60-DeprecateClientUtilitygetDeviceType.rst | 0
...on-79622-DeprecationOfCSSStyledContent.rst | 8 +-
...lerProvidePageBrowserToChooseStartPage.rst | 2 +-
...re-28171-ImprovedLinkFieldInFormEngine.rst | 4 +-
...RunManuallyExecutedTasksOnNextCron-run.rst | 2 +-
...endTheWidgetIdentifierWithCustomString.rst | 8 +-
...ailableAtPastingPositionAndUseModalNow.rst | 6 +-
...chronizedFieldValuesInLocalizedRecords.rst | 6 +-
...-ImplementFoldingOfSchedulerTaskGroups.rst | 0
...2-PageModuleNoticeContentIsAlsoShownOn.rst | 21 +++
...70316-IntroduceSessionStorageFramework.rst | 2 +-
.../Feature-72749-CLISupportForT3DImport.rst | 2 +-
...roppingVariantsInImageManipulationTool.rst | 4 +-
...uceTranslationSourceFieldForTt_content.rst | 12 +-
...ure-78192-RefactorClickMenuContextMenu.rst | 16 +--
...477-RefactoringOfFlashMessageRendering.rst | 0
.../Feature-78899-TCAMaxitemsOptional.rst | 2 +
...kInTypolinkForModificationOfPageParams.rst | 0
...ngOfTemplatePathsInBackendTemplateView.rst | 0
...-AddHookToAddCustomTypoScriptTemplates.rst | 65 +++++++++
.../Feature-79196-AllowReloadOfTopbar.rst | 2 +-
...216-AddYAMLConfigurationForCKEditorRTE.rst | 29 ++--
.../Feature-79225-PluginPreviewWithFluid.rst | 2 +-
...ButtonToDeleteSimilarErrorsFromSys_log.rst | 0
...ture-79240-SingleCliUserForCliCommands.rst | 0
...rmExtendExtensionLocationFunctionality.rst | 11 +-
...ToCreateTRIMExpressionWithDoctrineDBAL.rst | 0
...-SchedulerCLIAvailableAsSymfonyCommand.rst | 0
...arameterToFlinktypolinkAndFuritypolink.rst | 8 +-
...CARichtextConfigurationInConfigSection.rst | 4 +-
...ignalToExcludeTablesFromReferenceIndex.rst | 4 +-
...ature-79402-VariableViewHelperForFluid.rst | 2 -
...tSectionsInFluidTemplateWithController.rst | 8 +-
...etSectionsInFluidTemplateContentObject.rst | 8 +-
...79420-HideFilesFromListOfDocumentation.rst | 0
...tionToDisableValidationOfStoredRecords.rst | 2 +-
...ature-79440-FormEngineElementExpansion.rst | 10 +-
...Tform-AddElementSelectorForTextEditors.rst | 2 +-
...rm-AddFormSettingsButtonToModuleHeader.rst | 2 +-
...wListOfFailedInputElementsInFormEngine.rst | 2 +-
...0-EXTform-ExtendSaveToDatabaseFinisher.rst | 26 +++-
...EXTform-AddInspectorMultiselectEditors.rst | 0
...erPositionSupportForFluidStyledContent.rst | 4 +-
...ewContentElementsForFluidStyledContent.rst | 2 +-
...-NewDefaultLayoutForFluidStyledContent.rst | 10 +-
...eAndSpaceAfterClassForCssStyledContent.rst | 24 ++--
...ndSpaceAfterClassForFluidStyledContent.rst | 24 ++--
...22-TextmediaSupportForCSSStyledContent.rst | 4 +-
...ature-79626-IntegrateRecordLinkHandler.rst | 8 +-
...00-NewDataHandlerCommandCopyToLanguage.rst | 21 +++
...portant-78899-DisplayCondStrictParsing.rst | 4 +-
...nnectPersistentToRedisFromCacheBackend.rst | 6 +-
...ersioningPreview_where_hid_delProperty.rst | 0
...1-UseGlobalsDollarInsteadOfTYPO3jQuery.rst | 2 +-
.../Documentation/Changelog/8.6/Index.rst | 51 +++++++
...ng-79464-ExtFormRefactorFluidRendering.rst | 133 ------------------
...2-PageModuleNoticeContentIsAlsoShownOn.rst | 23 ---
...-AddHookToAddCustomTypoScriptTemplates.rst | 65 ---------
...00-NewDataHandlerCommandCopyToLanguage.rst | 21 ---
typo3/sysext/core/Documentation/Index.rst | 1 +
113 files changed, 547 insertions(+), 474 deletions(-)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-70316-AbstractUserAuthenticationPropertiesAndMethodsDroppedAndChanged.rst (92%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-77934-RemoveSelectKeyFromContentElementPreview.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-78192-RefactorClickMenuContextMenu.rst (65%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-78477-InheritanceOfFlashMessageViewHelper.rst (90%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-78477-RemoveFlashMessageGetMessageAsMarkup.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-78899-RemoveExtJsCodeFromFormEngineResultArray.rst (91%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-78899-RemoveMethodsHookAndPropertyInFormEngine.rst (89%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-78988-RemoveOptionalFluidTyposcriptTemplate.rst (98%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79025-ExtractTestingFrameworkForTYPO3.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79100-FeloginRemoveDefaultCss.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79109-LowlevelVersionsCommandParametersChanged.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79120-RemovedLegacyCliRelatedConstantsAndVariables.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79196-ToolbarItemEventHandlingChanged.rst (87%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79201-ExtFormSplitTyposcriptIncludes.rst (86%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79227-RemovedExtDirectStateProvider.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79228-RemoveExtJSPagetreeIndicatorFunctionality.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79242-RemoveL10n_modeNoCopy.rst (57%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79243-RemoveL10n_modeMergeIfNotBlank.rst (88%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79243-RemoveSys_language_softMergeIfNotBlank.rst (84%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79259-RemoveExtt3skin.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79263-SchedulerCLIControllerClassRemoved.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79270-RemovedRTEProcessingOptionDisableUnifyLineBreaks.rst (73%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79273-RemovedRteHtmlParserProcOptions.rst (96%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79300-RemovedRTEProctransformBoldAndItalicTagsOption.rst (91%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79302-MovedPagesurlSchemeToCompatibility7Extension.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79327-TheVeriCode-VCParameterIsNotEvaluatedAnyMore.rst (71%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79364-MovePageModuleFunctionQuickEditToCompatibility7.rst (90%)
create mode 100644 typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79464-ExtFormRefactorFluidRendering.rst
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79513-RemovedSessionLockingBasedOnUseragent.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79622-CSSStyledContentTableContentElementAdjustments.rst (95%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79622-DedicatedContentElementsForMenus.rst (98%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79622-DefaultContentElementChangedForFluidStyledContent.rst (96%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79622-DefaultLayoutsForFluidStyledContentChanged.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79622-DroppingThumbnailConfigurationForTt_content.rst (86%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79622-RemovalOfFluidStyledContentMenuViewHelpers.rst (86%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79622-SpaceBeforeAndSpaceAfterAdjustmentsForCSSStyledContent.rst (76%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Breaking-79622-StreamliningStructureOfCSSStyledContentAndFluidStyledContent.rst (95%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-51291-PageRepositoryShouldFieldBeOverlaid.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-70316-FrontendBasketWithRecs.rst (67%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-77934-DeprecateTt_contentFieldSelect_key.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-78225-LegacyPreparedStatementsWithinExtbase.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-78477-RefactoringOfFlashMessageRendering.rst (92%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-78899-FormEngineMethods.rst (77%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-78899-TCACtrlFieldRequestUpdateDropped.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-79258-MethodsInLocalizationRepository.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-79265-CommandLineControllerAndCleanerCommand.rst (98%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-79316-DeprecateArrayUtilityinArray.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-79327-DeprecateAbstractUserAuthenticationveriCodeMethod.rst (74%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-79341-MethodsRelatedToRichtextConfiguration.rst (89%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-79341-TCARichtextConfigurationInDefaultExtrasDropped.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-79364-DeprecateMembersInPageLayoutController.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-79440-TcaChanges.rst (99%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-79441-ChangeVisibilityInternalCacheDatahandler.rst (64%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-79560-DeprecateClientUtilitygetDeviceType.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Deprecation-79622-DeprecationOfCSSStyledContent.rst (78%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-12211-UsabilitySchedulerProvidePageBrowserToChooseStartPage.rst (91%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-28171-ImprovedLinkFieldInFormEngine.rst (86%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-45537-RunManuallyExecutedTasksOnNextCron-run.rst (85%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-47006-ExtendTheWidgetIdentifierWithCustomString.rst (68%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-47135-PasteIconsAvailableAtPastingPositionAndUseModalNow.rst (64%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-51291-SynchronizedFieldValuesInLocalizedRecords.rst (91%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-67243-ImplementFoldingOfSchedulerTaskGroups.rst (100%)
create mode 100644 typo3/sysext/core/Documentation/Changelog/8.6/Feature-69572-PageModuleNoticeContentIsAlsoShownOn.rst
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-70316-IntroduceSessionStorageFramework.rst (98%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-72749-CLISupportForT3DImport.rst (88%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-75880-ImplementMultipleCroppingVariantsInImageManipulationTool.rst (96%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-78169-IntroduceTranslationSourceFieldForTt_content.rst (77%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-78192-RefactorClickMenuContextMenu.rst (80%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-78477-RefactoringOfFlashMessageRendering.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-78899-TCAMaxitemsOptional.rst (99%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79121-ImplementHookInTypolinkForModificationOfPageParams.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79124-AllowOverwritingOfTemplatePathsInBackendTemplateView.rst (100%)
create mode 100644 typo3/sysext/core/Documentation/Changelog/8.6/Feature-79140-AddHookToAddCustomTypoScriptTemplates.rst
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79196-AllowReloadOfTopbar.rst (96%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79216-AddYAMLConfigurationForCKEditorRTE.rst (56%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79225-PluginPreviewWithFluid.rst (94%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79235-AddButtonToDeleteSimilarErrorsFromSys_log.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79240-SingleCliUserForCliCommands.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79250-ExtFormExtendExtensionLocationFunctionality.rst (89%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79262-AddPossibilityToCreateTRIMExpressionWithDoctrineDBAL.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79263-SchedulerCLIAvailableAsSymfonyCommand.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79337-AddUseCacheHashParameterToFlinktypolinkAndFuritypolink.rst (56%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79341-TCARichtextConfigurationInConfigSection.rst (66%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79387-AddSignalToExcludeTablesFromReferenceIndex.rst (92%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79402-VariableViewHelperForFluid.rst (97%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79409-AutorenderAssetSectionsInFluidTemplateWithController.rst (88%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79413-AutorenderAssetSectionsInFluidTemplateContentObject.rst (81%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79420-HideFilesFromListOfDocumentation.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79438-OptionToDisableValidationOfStoredRecords.rst (98%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79440-FormEngineElementExpansion.rst (94%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79442-EXTform-AddElementSelectorForTextEditors.rst (90%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79467-EXTform-AddFormSettingsButtonToModuleHeader.rst (69%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79521-ShowListOfFailedInputElementsInFormEngine.rst (91%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79530-EXTform-ExtendSaveToDatabaseFinisher.rst (83%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79531-EXTform-AddInspectorMultiselectEditors.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79622-HeaderPositionSupportForFluidStyledContent.rst (94%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79622-NewContentElementsForFluidStyledContent.rst (93%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79622-NewDefaultLayoutForFluidStyledContent.rst (94%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79622-SpaceBeforeAndSpaceAfterClassForCssStyledContent.rst (75%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79622-SpaceBeforeAndSpaceAfterClassForFluidStyledContent.rst (75%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79622-TextmediaSupportForCSSStyledContent.rst (86%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Feature-79626-IntegrateRecordLinkHandler.rst (76%)
create mode 100644 typo3/sysext/core/Documentation/Changelog/8.6/Important-75400-NewDataHandlerCommandCopyToLanguage.rst
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Important-78899-DisplayCondStrictParsing.rst (70%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Important-79005-ConnectPersistentToRedisFromCacheBackend.rst (72%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Important-79119-RemovedPageRepository-versioningPreview_where_hid_delProperty.rst (100%)
rename typo3/sysext/core/Documentation/Changelog/{master => 8.6}/Important-79221-UseGlobalsDollarInsteadOfTYPO3jQuery.rst (81%)
create mode 100644 typo3/sysext/core/Documentation/Changelog/8.6/Index.rst
delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Breaking-79464-ExtFormRefactorFluidRendering.rst
delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Feature-69572-PageModuleNoticeContentIsAlsoShownOn.rst
delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Feature-79140-AddHookToAddCustomTypoScriptTemplates.rst
delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Important-75400-NewDataHandlerCommandCopyToLanguage.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-70316-AbstractUserAuthenticationPropertiesAndMethodsDroppedAndChanged.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-70316-AbstractUserAuthenticationPropertiesAndMethodsDroppedAndChanged.rst
similarity index 92%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-70316-AbstractUserAuthenticationPropertiesAndMethodsDroppedAndChanged.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-70316-AbstractUserAuthenticationPropertiesAndMethodsDroppedAndChanged.rst
index b5e8a26b897b..f857a8fbb9ef 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-70316-AbstractUserAuthenticationPropertiesAndMethodsDroppedAndChanged.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-70316-AbstractUserAuthenticationPropertiesAndMethodsDroppedAndChanged.rst
@@ -21,7 +21,7 @@ Impact
======
Accessing one of these properties will raise a PHP warning.
-Calling the method :php:`fetchSessionData` will cause a PHP fatal error.
+Calling the method :php:`fetchSessionData()` will cause a PHP fatal error.
Affected Installations
@@ -40,8 +40,8 @@ Use configuration from :php:`DatabaseSessionBackend` located in
Session data can be manipulated with the following methods in :php:`AbstractUserAuthentication`
- * :php:`getSessionData`
- * :php:`setSessionData`
+ * :php:`getSessionData()`
+ * :php:`setSessionData()`
Calls to :php:`FrontendUserAuthentication::fetchSessionData()` can safely be removed.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-77934-RemoveSelectKeyFromContentElementPreview.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-77934-RemoveSelectKeyFromContentElementPreview.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-77934-RemoveSelectKeyFromContentElementPreview.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-77934-RemoveSelectKeyFromContentElementPreview.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-78192-RefactorClickMenuContextMenu.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78192-RefactorClickMenuContextMenu.rst
similarity index 65%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-78192-RefactorClickMenuContextMenu.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78192-RefactorClickMenuContextMenu.rst
index d5881c90cda7..cde7ecf6ceaf 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-78192-RefactorClickMenuContextMenu.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78192-RefactorClickMenuContextMenu.rst
@@ -9,7 +9,7 @@ See :issue:`78192`
Description
===========
-Due to the refactoring and unification of the click/context menu handling in the TYPO3 Backend, a few breaking changes have been introduced.
+Due to the refactoring and unification of the click/context-menu handling in the TYPO3 Backend, a few breaking changes have been introduced.
Classes removed
---------------
@@ -28,11 +28,11 @@ ExtJS component removed
-----------------------
- The :js:`TYPO3.Components.PageTree.ContextMenu` component defined in contextmenu.js has been removed.
-- The `contextMenuProvider` property as well as `enableContextMenu` and `openContextMenu` methods of the :js:`TYPO3.Components.PageTree.Tree` component has been removed.
+- The `contextMenuProvider` property as well as `enableContextMenu` and `openContextMenu` methods of the :js:`TYPO3.Components.PageTree.Tree` component have been removed.
Migration
^^^^^^^^^
-Migrate your code to require js module for custom click menu actions.
+Migrate your code to a requireJS module for custom click-menu actions.
ClickMenu requireJS component removed
-------------------------------------
@@ -48,11 +48,11 @@ Use the new requireJS component: `TYPO3/CMS/Backend/ContextMenu`.
Page TSConfig change
--------------------
-The page tree context menu configuration in Page TSConfig was removed (except for the `disableItems` part).
+The pagetree context-menu configuration in Page TSConfig has been removed (except for the `disableItems` part).
The list of available menu items is now provided by `ItemProviders` e.g. :php:`\TYPO3\CMS\Backend\ContextMenu\ItemProviders\PageProvider`.
-The TSConfig options for disabling Clickmenu items has been streamlined.
-Also some items names has been changed (e.g. `new_wizard` is now called `newWizard`, `db_list` is now `openListModule`). Refer to the provider class for correct naming.
+The TSConfig options for disabling click-menu items has been streamlined.
+Also some items names have changed (e.g. `new_wizard` is now called `newWizard`, `db_list` is now `openListModule`). Refer to the provider class for correct naming.
Migration
^^^^^^^^^
@@ -78,8 +78,8 @@ The following two hooks have been removed:
Migration
^^^^^^^^^
-Use new ItemsProvider API for adding or modifying click menu items.
-See existing usage of thi API in the core :php:`TYPO3\CMS\Filelist\ContextMenu\ItemProviders\FileProvider` or :php:`\TYPO3\CMS\Beuser\ContextMenu\ItemProvider`.
+Use the new ItemsProvider API to add or modify click-menu items.
+See existing usage of the API in the core :php:`TYPO3\CMS\Filelist\ContextMenu\ItemProviders\FileProvider` or :php:`\TYPO3\CMS\Beuser\ContextMenu\ItemProvider`.
Legacy Tree
@@ -91,17 +91,17 @@ Support for drag & drop menu for LegacyTree.js of pages has been dropped.
Changed markup (data attributes) for click menu
-----------------------------------------------
-- `data-listFrame` has been replaced with optional attribute `data-context` attribute. Context is set to "tree" for click menu triggered from trees.
-- for files `data-table` now contains real table name "sys_file" while before it contained combined identifier e.g. `1:/fileadmin/file.jpg`.
-the `data-uid` attribute contains now the combined identifier of the file (before it was empty).
-Thus `data-uid` attribute value is not always an int.
-- the class which triggers context menu has changed from :js:`t3-js-clickmenutrigger` to :js:`t3js-contextmenutrigger`
+- `data-listFrame` has been replaced with the optional attribute `data-context` attribute. Context is set to "tree" for click-menus triggered from trees.
+- for files, `data-table` now contains the real table name "sys_file" while before it contained the combined identifier e.g. `1:/fileadmin/file.jpg`.
+ the `data-uid` attribute now contains the combined identifier of the file (before it was empty).
+ Thus the `data-uid` attribute value is not always an int.
+- the class which triggers the context-menu has changed from :js:`t3-js-clickmenutrigger` to :js:`t3js-contextmenutrigger`
Migration
^^^^^^^^^
-To trigger click menu for files, use correct class as well as table and uid in data attributes. Replace `data-listFrame="0"` with `data-context="tree"`, `data-listFrame="1"` can be removed (it's a default context now).
+To trigger click-menus for files, use the correct class-attribute as well as the table and uid data attributes. Replace `data-listFrame="0"` with `data-context="tree"`, `data-listFrame="1"` can be removed (it's a default context now).
Impact
@@ -110,17 +110,17 @@ Impact
Instantiating the PHP class will result in a fatal PHP error.
Accessing removed JavaScript properties will result in a JavaScript error.
-Removed hooks will not influence menu rendering process.
+Removed hooks will not influence the menu rendering process.
Affected Installations
======================
-Any installation using removed PHP classes, JS components or hooks.
+Any installation using the removed PHP classes, JS components or hooks.
Migration
=========
-Adapt code to new click menu API.
+Adapt your code to the new click menu API.
.. index:: Backend, JavaScript, PHP-API, TSConfig
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-78477-InheritanceOfFlashMessageViewHelper.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78477-InheritanceOfFlashMessageViewHelper.rst
similarity index 90%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-78477-InheritanceOfFlashMessageViewHelper.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78477-InheritanceOfFlashMessageViewHelper.rst
index bc6daf62b733..800ed6758750 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-78477-InheritanceOfFlashMessageViewHelper.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78477-InheritanceOfFlashMessageViewHelper.rst
@@ -9,7 +9,7 @@ See :issue:`78477`
Description
===========
-The :php:`FlashMessageViewHelper` was refactored and no longer inherits from the :php:`TagBasedViewHelper`.
+The :php:`FlashMessageViewHelper` has been refactored and no longer inherits from the :php:`TagBasedViewHelper`.
Impact
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-78477-RemoveFlashMessageGetMessageAsMarkup.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78477-RemoveFlashMessageGetMessageAsMarkup.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-78477-RemoveFlashMessageGetMessageAsMarkup.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78477-RemoveFlashMessageGetMessageAsMarkup.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-78899-RemoveExtJsCodeFromFormEngineResultArray.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78899-RemoveExtJsCodeFromFormEngineResultArray.rst
similarity index 91%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-78899-RemoveExtJsCodeFromFormEngineResultArray.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78899-RemoveExtJsCodeFromFormEngineResultArray.rst
index 5acfe116b51c..982d2ef11dd2 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-78899-RemoveExtJsCodeFromFormEngineResultArray.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78899-RemoveExtJsCodeFromFormEngineResultArray.rst
@@ -9,7 +9,7 @@ See :issue:`78899`
Description
===========
-The key :php:`extJSCODE` in the array returned by FormEngines :php:`Container` and :php:`Element` (initialized
+The key :php:`extJSCODE` in the array returned by FormEngine's :php:`Container` and :php:`Element` (initialized
in :php:`AbstractNode->initializeResultArray()`) has been removed.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-78899-RemoveMethodsHookAndPropertyInFormEngine.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78899-RemoveMethodsHookAndPropertyInFormEngine.rst
similarity index 89%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-78899-RemoveMethodsHookAndPropertyInFormEngine.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78899-RemoveMethodsHookAndPropertyInFormEngine.rst
index c5ab6c01f0e4..84723f7ba0a7 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-78899-RemoveMethodsHookAndPropertyInFormEngine.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78899-RemoveMethodsHookAndPropertyInFormEngine.rst
@@ -46,7 +46,7 @@ Migration
=========
The methods have been partially moved to the :php:`TcaGroup` data provider and merged to the two
-FormEngine elements :php:`GroupEleement` and :php:`SelectMulitpleSideBySideElement`. Those can be
-changed and extended via the FormEngine internal :php:`NodeFactory` and data provider resolvers.
+FormEngine elements :php:`GroupElement` and :php:`SelectMultipleSideBySideElement`. Those can be
+changed and extended via FormEngine's internal :php:`NodeFactory` and data provider resolvers.
.. index:: Backend, PHP-API
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-78988-RemoveOptionalFluidTyposcriptTemplate.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78988-RemoveOptionalFluidTyposcriptTemplate.rst
similarity index 98%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-78988-RemoveOptionalFluidTyposcriptTemplate.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78988-RemoveOptionalFluidTyposcriptTemplate.rst
index 30a829d10c15..a598bad34a3d 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-78988-RemoveOptionalFluidTyposcriptTemplate.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78988-RemoveOptionalFluidTyposcriptTemplate.rst
@@ -26,7 +26,7 @@ Including the files manually has many benefits:
Impact
======
-The jQuery JavaScript and CSS files are not included anymore so the AJAX handling in the front-end
+The jQuery JavaScript and CSS files are not included anymore so the AJAX handling in the frontend
will not work anymore when the site relies on these files.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79025-ExtractTestingFrameworkForTYPO3.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79025-ExtractTestingFrameworkForTYPO3.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79025-ExtractTestingFrameworkForTYPO3.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79025-ExtractTestingFrameworkForTYPO3.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79100-FeloginRemoveDefaultCss.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79100-FeloginRemoveDefaultCss.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79100-FeloginRemoveDefaultCss.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79100-FeloginRemoveDefaultCss.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79109-LowlevelVersionsCommandParametersChanged.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79109-LowlevelVersionsCommandParametersChanged.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79109-LowlevelVersionsCommandParametersChanged.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79109-LowlevelVersionsCommandParametersChanged.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79120-RemovedLegacyCliRelatedConstantsAndVariables.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79120-RemovedLegacyCliRelatedConstantsAndVariables.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79120-RemovedLegacyCliRelatedConstantsAndVariables.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79120-RemovedLegacyCliRelatedConstantsAndVariables.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79196-ToolbarItemEventHandlingChanged.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79196-ToolbarItemEventHandlingChanged.rst
similarity index 87%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79196-ToolbarItemEventHandlingChanged.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79196-ToolbarItemEventHandlingChanged.rst
index 96215609c757..fa3194c93bbd 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79196-ToolbarItemEventHandlingChanged.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79196-ToolbarItemEventHandlingChanged.rst
@@ -16,13 +16,13 @@ that the event information gets lost, as the whole topbar is rendered from scrat
Impact
======
-After reloading the topbar, not migrated events will not get triggered anymore.
+After reloading the topbar, non-migrated events will not get triggered anymore.
Affected Installations
======================
-All installations with old-fashioned toolbar item registrations are affected.
+All installations with old-fashioned toolbar item registrations.
Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79201-ExtFormSplitTyposcriptIncludes.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79201-ExtFormSplitTyposcriptIncludes.rst
similarity index 86%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79201-ExtFormSplitTyposcriptIncludes.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79201-ExtFormSplitTyposcriptIncludes.rst
index 84da622a0813..8d8cc665f7d9 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79201-ExtFormSplitTyposcriptIncludes.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79201-ExtFormSplitTyposcriptIncludes.rst
@@ -10,7 +10,7 @@ Description
===========
The frontend specific TypoScript setup for EXT:form isn't loaded automatically anymore and must be added manually through
-static includes. With this change a TYPO3 integrator could easier decide at which place the extension Typoscript is included.
+static includes. With this change a TYPO3 integrator can easier decide where the extension Typoscript is included.
Impact
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79227-RemovedExtDirectStateProvider.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79227-RemovedExtDirectStateProvider.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79227-RemovedExtDirectStateProvider.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79227-RemovedExtDirectStateProvider.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79228-RemoveExtJSPagetreeIndicatorFunctionality.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79228-RemoveExtJSPagetreeIndicatorFunctionality.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79228-RemoveExtJSPagetreeIndicatorFunctionality.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79228-RemoveExtJSPagetreeIndicatorFunctionality.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79242-RemoveL10n_modeNoCopy.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79242-RemoveL10n_modeNoCopy.rst
similarity index 57%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79242-RemoveL10n_modeNoCopy.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79242-RemoveL10n_modeNoCopy.rst
index 13097539bcc5..efd40d590bd9 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79242-RemoveL10n_modeNoCopy.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79242-RemoveL10n_modeNoCopy.rst
@@ -9,15 +9,15 @@ See :issue:`79242`
Description
===========
-The setting noCopy is removed from the list of possible values of the TCA column
-property l10n_mode without any replacement.
+The setting `noCopy` has been removed without replacement from the list of possible values of the TCA column
+property `l10n_mode`.
Impact
======
-Previously noCopy prevented that values of the parent language record are copied
-to a particular localization when this was created. Now, this value is duplicated once during the creation of the localized record and has to be cleaned manually if required.
+Previously `noCopy` prevented that values of the parent language record were copied
+to a particular localization when that was created. Now, this value is duplicated during the creation of the localized record and has to be cleared manually if required.
Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79243-RemoveL10n_modeMergeIfNotBlank.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79243-RemoveL10n_modeMergeIfNotBlank.rst
similarity index 88%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79243-RemoveL10n_modeMergeIfNotBlank.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79243-RemoveL10n_modeMergeIfNotBlank.rst
index 6fa374d7c2ce..56c7d2589646 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79243-RemoveL10n_modeMergeIfNotBlank.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79243-RemoveL10n_modeMergeIfNotBlank.rst
@@ -9,8 +9,8 @@ See :issue:`79243`
Description
===========
-The setting `mergeIfNotBlank` is removed from the list of possible values of
-the TCA column property `l10n_mode` without any replacement.
+The setting `mergeIfNotBlank` has been removed without replacement from the list of possible values of
+the TCA column property `l10n_mode`.
Impact
@@ -19,7 +19,7 @@ Impact
Previously values of a localization having a dependent parent record were taken
from the parent record if `l10n_mode` for the particular field was set to
`mergeIfNotBlank` and the value in the localization was empty. Now, this value
-is duplicated once during the creation of the localized record and has to be
+is duplicated during the creation of the localized record and has to be
modified manually if required.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79243-RemoveSys_language_softMergeIfNotBlank.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79243-RemoveSys_language_softMergeIfNotBlank.rst
similarity index 84%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79243-RemoveSys_language_softMergeIfNotBlank.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79243-RemoveSys_language_softMergeIfNotBlank.rst
index dc991a0e2d93..bb62b7a9f8d3 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79243-RemoveSys_language_softMergeIfNotBlank.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79243-RemoveSys_language_softMergeIfNotBlank.rst
@@ -9,9 +9,9 @@ See :issue:`79243`
Description
===========
-The TypoScript setting `config.sys_language_softMergeIfNotBlank` is removed
+The TypoScript setting `config.sys_language_softMergeIfNotBlank` has been removed
without any replacement. This is a result of removing the TCA setting
-`mergeIfNotBlank` is removed from the list of possible values for `l10n_mode`.
+`mergeIfNotBlank` from the list of possible values for `l10n_mode`.
Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79259-RemoveExtt3skin.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79259-RemoveExtt3skin.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79259-RemoveExtt3skin.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79259-RemoveExtt3skin.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79263-SchedulerCLIControllerClassRemoved.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79263-SchedulerCLIControllerClassRemoved.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79263-SchedulerCLIControllerClassRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79263-SchedulerCLIControllerClassRemoved.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79270-RemovedRTEProcessingOptionDisableUnifyLineBreaks.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79270-RemovedRTEProcessingOptionDisableUnifyLineBreaks.rst
similarity index 73%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79270-RemovedRTEProcessingOptionDisableUnifyLineBreaks.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79270-RemovedRTEProcessingOptionDisableUnifyLineBreaks.rst
index df702cebe319..b4b9a6e6a980 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79270-RemovedRTEProcessingOptionDisableUnifyLineBreaks.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79270-RemovedRTEProcessingOptionDisableUnifyLineBreaks.rst
@@ -13,10 +13,9 @@ The RTE option that could be set via PageTSconfig `RTE.default.proc.disableUnify
The option was never set by default.
-If activated, it allowed that either line feeds (LFs) and carriage returns (CRs) are left as is. If the option was not set,
-then all line breaks are converted to CRLFs after processing (Windows-syntax) to have a unified style of line breaks
-in the database and have no problems when editors from both Windows and Unix systems do not need to have
-any unexpected behaviour.
+If activated, it allowed that both line feeds (LFs) and carriage returns (CRs) were left as is. If the option was not set,
+all line breaks were converted to CRLFs after processing (Windows-syntax) to have a unified style of line breaks
+in the database.
The option was only there for historic reasons in TYPO3 v3 and TYPO3 v4 to allow to simulate old behaviour
when no RTE was available.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79273-RemovedRteHtmlParserProcOptions.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79273-RemovedRteHtmlParserProcOptions.rst
similarity index 96%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79273-RemovedRteHtmlParserProcOptions.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79273-RemovedRteHtmlParserProcOptions.rst
index 8d26dfee1c83..f907e1fd136b 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79273-RemovedRteHtmlParserProcOptions.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79273-RemovedRteHtmlParserProcOptions.rst
@@ -19,7 +19,7 @@ The following TSconfig options for processing content of RTE fields have been re
Impact
======
-Setting any of these options have no effect anymore.
+Setting any of these options has no effect anymore.
Content coming from the database towards the RTE will now always keep unknown tags (but HSC'ed), and never have any
double-encoded characters - this was a default since a decade already.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79300-RemovedRTEProctransformBoldAndItalicTagsOption.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79300-RemovedRTEProctransformBoldAndItalicTagsOption.rst
similarity index 91%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79300-RemovedRTEProctransformBoldAndItalicTagsOption.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79300-RemovedRTEProctransformBoldAndItalicTagsOption.rst
index d88a25e2409c..cd452ac77991 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79300-RemovedRTEProctransformBoldAndItalicTagsOption.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79300-RemovedRTEProctransformBoldAndItalicTagsOption.rst
@@ -59,7 +59,7 @@ This code does the same as having `proc.transformBoldAndItalicTags=1`:
}
}
-If having the option explicitly turned off (allowing strong, b, em, and i tags) is wanted the configuration should look like this:
+If having the option explicitly turned off (allowing strong, b, em, and i tags) is what is wanted the configuration should look like this:
.. code-block:: typoscript
@@ -80,7 +80,7 @@ If having the option explicitly turned off (allowing strong, b, em, and i tags)
}
}
-Please note that this migration is necessary if custom RTE options are in place, as the default RTE HTMLArea configuration does that
+Please note that this migration is only necessary if custom RTE options are in place, as the default RTE HTMLArea configuration does that
automatically.
.. index:: RTE, TSConfig
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79302-MovedPagesurlSchemeToCompatibility7Extension.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79302-MovedPagesurlSchemeToCompatibility7Extension.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79302-MovedPagesurlSchemeToCompatibility7Extension.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79302-MovedPagesurlSchemeToCompatibility7Extension.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79327-TheVeriCode-VCParameterIsNotEvaluatedAnyMore.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79327-TheVeriCode-VCParameterIsNotEvaluatedAnyMore.rst
similarity index 71%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79327-TheVeriCode-VCParameterIsNotEvaluatedAnyMore.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79327-TheVeriCode-VCParameterIsNotEvaluatedAnyMore.rst
index 2f9087928467..61f4570ad606 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79327-TheVeriCode-VCParameterIsNotEvaluatedAnyMore.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79327-TheVeriCode-VCParameterIsNotEvaluatedAnyMore.rst
@@ -9,14 +9,14 @@ See :issue:`79327`
Description
===========
-The `veriCode` (`&vC=...`) parameter generated by :php:`AbstractUserAuthentication::veriCode` is not evaluated any more in:
+The `veriCode` (`&vC=...`) parameter generated by :php:`AbstractUserAuthentication::veriCode` is not evaluated anymore in:
- `ImportExportController::checkUpload()`
- `FileController::main()`
- `EditDocumentController::processData()`
- `SimpleDataHandlerController::main()`
-Also following properties are removed:
+Also the following properties have been removed:
- `EditDocumentController::vC`
- `SimpleDataHandlerController::vC`
@@ -26,13 +26,13 @@ Also following properties are removed:
Impact
======
-Any code reading from removed `vC` properties will now throw an "Undefined property" notice.
+Any code reading from the removed `vC` properties will now throw an "Undefined property" notice.
Affected Installations
======================
-Any installation having code calling relaying on 'vC' property being present in aforementioned classes, or relaying on `vC` parameter being checked.
+Any installation having code relying on 'vC' property being present in aforementioned classes, or relying on `vC` parameter being checked.
Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79364-MovePageModuleFunctionQuickEditToCompatibility7.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79364-MovePageModuleFunctionQuickEditToCompatibility7.rst
similarity index 90%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79364-MovePageModuleFunctionQuickEditToCompatibility7.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79364-MovePageModuleFunctionQuickEditToCompatibility7.rst
index 74b442969baf..bed647919f57 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79364-MovePageModuleFunctionQuickEditToCompatibility7.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79364-MovePageModuleFunctionQuickEditToCompatibility7.rst
@@ -21,7 +21,7 @@ Installation of EXT:compatibility7 is required to continue using the `QuickEdit`
Affected Installations
======================
-All installations depend on the `QuickEdit` function in the page module.
+All installations depending on the `QuickEdit` function in the page module.
.. index:: Backend
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79464-ExtFormRefactorFluidRendering.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79464-ExtFormRefactorFluidRendering.rst
new file mode 100644
index 000000000000..4843f7ff7055
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79464-ExtFormRefactorFluidRendering.rst
@@ -0,0 +1,133 @@
+.. include:: ../../Includes.txt
+
+======================================================
+Breaking: #51442 - EXT:form - Refactor fluid rendering
+======================================================
+
+See :issue:`79464`
+
+Description
+===========
+
+EXT:form uses "fluid" as the default rendering strategy.
+Therefore, EXT:form has to work closely with the concepts of fluid to avoid current and future problems.
+Until now, EXT:form tried to reuse a fluid view instance by reconfiguring the instance on each nesting level, but fluid is not intended for such a purpose.
+This change reduces the complexity of the rendering process and works closer with the concepts of fluid.
+
+Impact
+======
+
+The configuration options `renderingOptions.templateRootPaths`, `renderingOptions.partialRootPaths` and `renderingOptions.layoutRootPaths` for form elements are
+from now on only rules for the root form element ('Form') and will be applied for all child form elements.
+If you configure `renderingOptions.templateRootPaths` etc. for other form elements it will have no effect.
+
+The configuration option `renderingOptions.templatePathAndFilename` for form elements was removed from the configuration and will have no effect.
+To define a template file name which should be used instead of a filename which is named like the form element type, there is a new option `renderingOptions.templateName`.
+
+The internal setting `renderingOptions.renderableNameInTemplate` for form elements has been removed from the configuration and will have no effect.
+
+The setting `rendererClassName` for form elements are from now on only rules for the root form element ('Form').
+If you define this option for other form elements, an `invalid configuration` exception will be thrown.
+
+The configuration for the backend editor inline templates which are used by editor javascript has changed.
+The configuration path `prototypes.<prototypeName>.formEditor.formEditorTemplates` has been renamed and has no effect anymore.
+The fluid configuration part moved from `prototypes.<prototypeName>.formEditor.formEditorTemplates` to a new section `prototypes.<prototypeName>.formEditor.formEditorFluidConfiguration`.
+The backend editor inline template mapping moved to a new section `prototypes.<prototypeName>.formEditor.formEditorPartials`.
+The inline template mapping for stage templates has been condensed. If you define custom form editor stage templates which use a default stage template it could
+result in a javascript error within the form editor.
+
+The template files moved from `Resources/Private/Frontend/Templates/FormElements/` to `Resources/Private/Frontend/Partials`.
+The template structure has changed. Without adaptation of your overridden templates, no form elements are visible within the frontend.
+
+
+Affected Installations
+======================
+
+All installations since TYPO3 8.5 which use the new EXT:form extension and create or extend custom form elements through configuration and / or
+override EXT:form template files.
+
+Migration
+=========
+
+If you override/ extend
+
+ `TYPO3.CMS.Form.mixins.formElementMixins.BaseFormElementMixin.renderingOptions.templateRootPaths`
+ `TYPO3.CMS.Form.mixins.formElementMixins.BaseFormElementMixin.renderingOptions.partialRootPaths`
+ `TYPO3.CMS.Form.mixins.formElementMixins.BaseFormElementMixin.renderingOptions.layoutRootPaths`
+
+move it to
+
+ `TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.templateRootPaths`
+ `TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.partialRootPaths`
+ `TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.layoutRootPaths`
+
+
+If you override/ extend
+
+ `TYPO3.CMS.Form.mixins.formElementMixins.BaseFormElementMixin.renderingOptions.skipUnknownElements`
+
+move it to
+
+ `TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.skipUnknownElements`
+
+
+If you defined
+
+ `TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.<formElementType>.rendererClassName`
+
+for a <formElementType> which is *NOT* 'Form', you have to remove this setting.
+
+
+If you defined
+
+ `TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.renderableNameInTemplate`
+
+you have to use
+
+ `TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.templateName`
+
+`templateName` is the partial path, relative to `TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.partialRootPaths`
+
+
+If you defined custom form editor templates within
+
+ `TYPO3.CMS.Form.prototypes.<prototypeName>.formEditor.formEditorTemplates`
+
+you have to move this to
+
+ `TYPO3.CMS.Form.prototypes.<prototypeName>.formEditor.formEditorPartials`
+
+
+If you defined a custom form editor stage template which depends on a default form editor stage template you have to redefine it:
+
+ Stage/Text => Stage/SimpleTemplate
+ Stage/Password => Stage/SimpleTemplate
+ Stage/AdvancedPassword => Stage/SimpleTemplate
+ Stage/Textarea => Stage/SimpleTemplate
+ Stage/Checkbox => Stage/SimpleTemplate
+ Stage/MultiCheckbox => Stage/SelectTemplate
+ Stage/MultiSelect => Stage/SelectTemplate
+ Stage/RadioButton => Stage/SelectTemplate
+ Stage/SingleSelect => Stage/SelectTemplate
+ Stage/DatePicker => Stage/SimpleTemplate
+ Stage/Hidden => Stage/SimpleTemplate
+ Stage/FileUpload => Stage/FileUploadTemplate
+ Stage/ImageUpload => Stage/FileUploadTemplate
+
+
+All form element templates except the template for the `Form` element moved from templates to partials.
+You have to move this too, if you extended the fluid search paths.
+The 'Form' element is a template and will be found through `TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.templateRootPaths`.
+All other form elements are partials and will be found through `TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.partialRootPaths`.
+
+
+The template/partial structure has changed. You have to adapt this to your custom templates.
+Please look at the files within EXT:form/Resources/Private/Frontend/Partials
+to see what has happened.
+The main change is that you have to wrap the markup with
+
+ <formvh:renderRenderable renderable="{element}">
+ some form element
+ </formvh:renderRenderable>
+
+.. index:: Backend, Frontend, ext:form
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79513-RemovedSessionLockingBasedOnUseragent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79513-RemovedSessionLockingBasedOnUseragent.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79513-RemovedSessionLockingBasedOnUseragent.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79513-RemovedSessionLockingBasedOnUseragent.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-CSSStyledContentTableContentElementAdjustments.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-CSSStyledContentTableContentElementAdjustments.rst
similarity index 95%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-CSSStyledContentTableContentElementAdjustments.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-CSSStyledContentTableContentElementAdjustments.rst
index 570b99d768f1..67fe678e6bdd 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-CSSStyledContentTableContentElementAdjustments.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-CSSStyledContentTableContentElementAdjustments.rst
@@ -37,7 +37,7 @@ TypoScript options removed:
Table Summary
-------------
-The <table> summary attribute is not supported in HTML5 and was dropped.
+The <table> summary attribute is not supported in HTML5 and has been dropped.
No migration path available.
@@ -96,7 +96,7 @@ stored in flexforms to dedicated fields in the database.
Table summary
-------------
-The <table> summary attribute is not supported in HTML5 and was dropped.
+The <table> summary attribute is not supported in HTML5 and has been dropped.
No migration path available.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-DedicatedContentElementsForMenus.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-DedicatedContentElementsForMenus.rst
similarity index 98%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-DedicatedContentElementsForMenus.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-DedicatedContentElementsForMenus.rst
index dffc68e4a477..66c933659c58 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-DedicatedContentElementsForMenus.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-DedicatedContentElementsForMenus.rst
@@ -20,7 +20,7 @@ menu_categorized_content Categorized content Content elements for s
menu_categorized_pages Categorized pages Pages for selected categories
menu_pages Pages Menu of selected pages
menu_subpages Subpages Menu of subpages of selected pages
-menu_recently_updated Recently updated pages Menu of recenlty updated pages
+menu_recently_updated Recently updated pages Menu of recently updated pages
menu_related_pages Related pages Menu of related pages based on keywords
menu_section Section index Page content marked for section menus
menu_section_pages Section index of subpages Menu of subpages of selected pages including sections
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-DefaultContentElementChangedForFluidStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-DefaultContentElementChangedForFluidStyledContent.rst
similarity index 96%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-DefaultContentElementChangedForFluidStyledContent.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-DefaultContentElementChangedForFluidStyledContent.rst
index 18f727cca110..a74e7b4eb7d3 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-DefaultContentElementChangedForFluidStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-DefaultContentElementChangedForFluidStyledContent.rst
@@ -10,7 +10,7 @@ Description
===========
The default content element has been streamlined with CSS Styled Content
-and was changed to "Text".
+and has been changed to "Text".
Impact
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-DefaultLayoutsForFluidStyledContentChanged.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-DefaultLayoutsForFluidStyledContentChanged.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-DefaultLayoutsForFluidStyledContentChanged.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-DefaultLayoutsForFluidStyledContentChanged.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-DroppingThumbnailConfigurationForTt_content.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-DroppingThumbnailConfigurationForTt_content.rst
similarity index 86%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-DroppingThumbnailConfigurationForTt_content.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-DroppingThumbnailConfigurationForTt_content.rst
index ec1d81aa2e48..3b6653a696f2 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-DroppingThumbnailConfigurationForTt_content.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-DroppingThumbnailConfigurationForTt_content.rst
@@ -9,8 +9,8 @@ See :issue:`79622`
Description
===========
-We are currently not able to set the thumbnail field for records according
-to the type of the record. Since tt_content uses different fields to store
+It is currently not possible to set the thumbnail field depending on
+the type of the record. Since tt_content uses different fields to store
media we are removing this default configuration that was set to `images`
by CSS Styled Content and `assets` by Fluid Styled Content.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-RemovalOfFluidStyledContentMenuViewHelpers.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-RemovalOfFluidStyledContentMenuViewHelpers.rst
similarity index 86%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-RemovalOfFluidStyledContentMenuViewHelpers.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-RemovalOfFluidStyledContentMenuViewHelpers.rst
index 71304c28ca77..353fda5e3b86 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-RemovalOfFluidStyledContentMenuViewHelpers.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-RemovalOfFluidStyledContentMenuViewHelpers.rst
@@ -10,7 +10,7 @@ Description
===========
Fetching data directly in the view is not recommended and the temporary
-solution of menu viewhelpers are now replaced by it´s successor the menu
+solution of menu ViewHelpers has been replaced by its successor, the menu
processor that is based on HMENU.
Menu ViewHelpers have been moved to the `compatibility7` extension, and are
@@ -28,16 +28,16 @@ List of removed ViewHelpers:
Affected Installations
======================
-All installations that use the `fluid_styled_content` menu viewhelpers.
+All installations that use the `fluid_styled_content` menu ViewHelpers.
Migration
=========
-Use `TYPO3\CMS\Frontend\DataProcessing\MenuProcessor` instead of viewhelpers.
+Use `TYPO3\CMS\Frontend\DataProcessing\MenuProcessor` instead of ViewHelpers.
-For CMS 8 the viewhelpers will be available as soon as `compatibility7` is
-installed, but it´s highly recommended to migrate your configuration.
+For CMS 8 the ViewHelpers will be available as soon as `compatibility7` is
+installed, but it's highly recommended to migrate your configuration.
Example (Directory)
-------------------
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-SpaceBeforeAndSpaceAfterAdjustmentsForCSSStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-SpaceBeforeAndSpaceAfterAdjustmentsForCSSStyledContent.rst
similarity index 76%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-SpaceBeforeAndSpaceAfterAdjustmentsForCSSStyledContent.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-SpaceBeforeAndSpaceAfterAdjustmentsForCSSStyledContent.rst
index 3b444a75fb04..94acf6d2364b 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-SpaceBeforeAndSpaceAfterAdjustmentsForCSSStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-SpaceBeforeAndSpaceAfterAdjustmentsForCSSStyledContent.rst
@@ -9,21 +9,21 @@ See :issue:`79622`
Description
===========
-CSS Styled Content provided the editor the possibility to fine-tune distances
-between content elements. The concept of CSC relied on that the editor
-understood what `margins` are, how they are calculated and had to maintain
-an overview of pixels that where used on the site he is maintaining.
-
-This lead to different problems not only for the editor but also for the
-integrator because he has no control about what the editor fills into these
-fields. Also it was hardly controlable when these distances should be
+CSS Styled Content provided the possibility to the editor to fine-tune distances
+between content elements. The concept of CSC relied on the editor
+understanding what `margins` are, how they are calculated and had to maintain
+an overview of pixels that were used on the site he/she is maintaining.
+
+This led to different problems not only for the editor but also for the
+integrator because he had no control about what the editor fills into these
+fields. Also it was hardly controllable when these distances should be
variable and change on certain viewports for mobile usage.
-To regain control for this behaviour we are now introducing a new concept
+To regain control over this behaviour we are now introducing a new concept
that purely relies on CSS classes, that can be defined by the integrator.
The original fields `spaceAfter` and `spaceBefore` have been dropped, and also
-the method :php:`\TYPO3\CMS\CssStyledContent\Controller\CssStyledContentController::renderSpace`
+the method :php:`\TYPO3\CMS\CssStyledContent\Controller\CssStyledContentController::renderSpace()`
is not called anymore.
@@ -60,7 +60,7 @@ New TypoScript Rendering
Impact
======
-Userdefined distances between content elements are missing.
+User-defined distances between content elements are missing.
Affected Installations
@@ -90,7 +90,7 @@ Check if your site is affected
Migration
=========
-There is no automatic migration available. If a migration is nessesary you need
+There is no automatic migration available. If a migration is necessary you need
to check the new presets available and migrate the pixels defined before to the
a preset of your choice.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-StreamliningStructureOfCSSStyledContentAndFluidStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-StreamliningStructureOfCSSStyledContentAndFluidStyledContent.rst
similarity index 95%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-StreamliningStructureOfCSSStyledContentAndFluidStyledContent.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-StreamliningStructureOfCSSStyledContentAndFluidStyledContent.rst
index 1ddf24ae6eeb..070e4353f3d8 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79622-StreamliningStructureOfCSSStyledContentAndFluidStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-StreamliningStructureOfCSSStyledContentAndFluidStyledContent.rst
@@ -130,8 +130,8 @@ Fluid Styled Content
Migration
=========
-Database entries can automatically upgraded to the new locations. If you have
-references in your TypoScript files you need to to the migration manually.
+Database entries can be automatically upgraded to the new locations. If you have
+references in your TypoScript files you need to do the migration manually.
Use the new locations for accessing the TypoScript configuration.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-51291-PageRepositoryShouldFieldBeOverlaid.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-51291-PageRepositoryShouldFieldBeOverlaid.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-51291-PageRepositoryShouldFieldBeOverlaid.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-51291-PageRepositoryShouldFieldBeOverlaid.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-70316-FrontendBasketWithRecs.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-70316-FrontendBasketWithRecs.rst
similarity index 67%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-70316-FrontendBasketWithRecs.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-70316-FrontendBasketWithRecs.rst
index 6d1ef1db6d3e..a0ca2a9215b2 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-70316-FrontendBasketWithRecs.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-70316-FrontendBasketWithRecs.rst
@@ -10,7 +10,7 @@ Description
===========
The TypoScriptFrontendController has a basic mechanism to automatically register session data if the GET/POST
-variable :code:`recs is given. This has been deprecated. This additionally obsoletes the configuration
+variable :code:`recs` is given. This has been deprecated. This additionally obsoletes the configuration
variable :php:`$GLOBALS['TYPO3_CONF_VARS']['FE']['maxSessionDataSize']` which has been deprecated, too.
@@ -23,14 +23,14 @@ Handling baskets or other session data in :code:`recs` throws a deprecation warn
Affected Installations
======================
-Some old extension like `tt_products` rely on this handling and should be adapted. Searching extensions
+Extensions with a legacy that rely on this automatic basket (`tt_products` for example) should be adapted. Searching extensions
for string :php:`recs` should reveal affected parts.
Migration
=========
-Use the session functions :php:`setKey` and :php:`getKey` of :php:`$GLOBALS['TSFE']->fe_user` directly to store session data
+Use the session functions :php:`setKey()` and :php:`getKey()` of :php:`$GLOBALS['TSFE']->fe_user` directly to store session data
like basket information from within the extension.
.. index:: Frontend, PHP-API
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-77934-DeprecateTt_contentFieldSelect_key.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-77934-DeprecateTt_contentFieldSelect_key.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-77934-DeprecateTt_contentFieldSelect_key.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-77934-DeprecateTt_contentFieldSelect_key.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-78225-LegacyPreparedStatementsWithinExtbase.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-78225-LegacyPreparedStatementsWithinExtbase.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-78225-LegacyPreparedStatementsWithinExtbase.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-78225-LegacyPreparedStatementsWithinExtbase.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-78477-RefactoringOfFlashMessageRendering.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-78477-RefactoringOfFlashMessageRendering.rst
similarity index 92%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-78477-RefactoringOfFlashMessageRendering.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-78477-RefactoringOfFlashMessageRendering.rst
index 83e1af71f5e8..c1180e612002 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-78477-RefactoringOfFlashMessageRendering.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-78477-RefactoringOfFlashMessageRendering.rst
@@ -19,7 +19,7 @@ The following methods and properties within :php:`FlashMessage::class` have been
Impact
======
-Using this properties and methods will stop working in TYPO3 v9.
+Using these properties and methods will stop working in TYPO3 v9.
Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-78899-FormEngineMethods.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-78899-FormEngineMethods.rst
similarity index 77%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-78899-FormEngineMethods.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-78899-FormEngineMethods.rst
index d6021e00b9f0..40ee2442f9bd 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-78899-FormEngineMethods.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-78899-FormEngineMethods.rst
@@ -9,7 +9,7 @@ See :issue:`78899`
Description
===========
-The following methods have been deprecated:
+The following methods have been marked as deprecated:
* :code:`TYPO3\CMS\Core\Database\RelationHandler->readyForInterface()`
* :code:`TYPO3\CMS\Backend\Form\FormDataProvider->sanitizeMaxItems()`
@@ -34,20 +34,16 @@ Extensions using above methods.
Migration
=========
-* :code:`sanitizeMaxItems()` has been merged into calling methods using a default value
- and sanitizing with :code:`MathUtility::forceIntegerInRange()`.
-* :code:`readyForInterface()` has been substituted with the easier to parse
-method :code:`getResolvedItemArray()`.
+* :code:`sanitizeMaxItems()` has been merged into calling methods using a default value and sanitizing with :code:`MathUtility::forceIntegerInRange()`.
+* :code:`readyForInterface()` has been substituted with the easier to parse method :code:`getResolvedItemArray()`.
* :code:`getSpecConfParts()` is obsolete with the removal of :code:`defaultExtras` TCA
* :code:`ColorpickerController` is obsolete with the JavaScript based colorpicker in the backend
* :code:`SuggestWizard` has been merged into :code:`GroupElement` directly, the standalone class is obsolete
-* :code:`getValidationDataAsDataAttribute()` - use :code:`getValidationDataAsJsonString()` and :code:`htmlspecialchars()` the result,
- or use `GeneralUtility::implodeAttributes()` with second argument set to true.
-* :code:`renderWizards()` has been substituted with the new API :code:`NodeExpansion`. Old :code:`popup, userFunc, script` wizards
- are still called and rendered, but the method usage should be avoided and extensions should switch the new API.
+* :code:`getValidationDataAsDataAttribute()` - use :code:`getValidationDataAsJsonString()` and :code:`htmlspecialchars()` the result or use `GeneralUtility::implodeAttributes()` with second argument set to true.
+* :code:`renderWizards()` has been substituted with the new API :code:`NodeExpansion`. Old :code:`popup, userFunc, script` wizards are still called and rendered, but the method usage should be avoided and extensions should switch to the new API.
-Extensions using above methods should consider switch away from those methods.
+Extensions using above methods should consider to switch away from those methods.
.. index:: Backend, PHP-API
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-78899-TCACtrlFieldRequestUpdateDropped.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-78899-TCACtrlFieldRequestUpdateDropped.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-78899-TCACtrlFieldRequestUpdateDropped.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-78899-TCACtrlFieldRequestUpdateDropped.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79258-MethodsInLocalizationRepository.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79258-MethodsInLocalizationRepository.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-79258-MethodsInLocalizationRepository.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79258-MethodsInLocalizationRepository.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79265-CommandLineControllerAndCleanerCommand.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79265-CommandLineControllerAndCleanerCommand.rst
similarity index 98%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-79265-CommandLineControllerAndCleanerCommand.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79265-CommandLineControllerAndCleanerCommand.rst
index 780dbd190f75..7f94dd540f46 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79265-CommandLineControllerAndCleanerCommand.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79265-CommandLineControllerAndCleanerCommand.rst
@@ -19,7 +19,7 @@ were introduced in TYPO3 v4 have been marked as deprecated:
Impact
======
-Instantiating any of the PHP classes above will trigger a deprecation notice.
+Instantiating any of the PHP classes above will trigger a deprecation log entry.
Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79316-DeprecateArrayUtilityinArray.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79316-DeprecateArrayUtilityinArray.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-79316-DeprecateArrayUtilityinArray.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79316-DeprecateArrayUtilityinArray.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79327-DeprecateAbstractUserAuthenticationveriCodeMethod.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79327-DeprecateAbstractUserAuthenticationveriCodeMethod.rst
similarity index 74%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-79327-DeprecateAbstractUserAuthenticationveriCodeMethod.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79327-DeprecateAbstractUserAuthenticationveriCodeMethod.rst
index 88e19b07ff1f..5dd3cf0a9fde 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79327-DeprecateAbstractUserAuthenticationveriCodeMethod.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79327-DeprecateAbstractUserAuthenticationveriCodeMethod.rst
@@ -12,13 +12,13 @@ Description
The :php:`AbstractUserAuthentication::veriCode` method has been marked as deprecated.
Right now all Backend urls require module token, so veriCode is not needed any more.
-Veri token was used as an alternative verification when the JavaScript interface executes cmd's to tce_db.php from eg. MSIE 5.0 because the proper referer is not passed with this browser...
+The Veri token was used as an alternative verification when the JavaScript interface executes cmds to tce_db.php from eg. MSIE 5.0 because the proper referrer is not passed with this browser...
Impact
======
-Calling :php:`AbstractUserAuthentication::veriCode` will log deprecation message.
+Calling :php:`AbstractUserAuthentication::veriCode` will trigger a deprecation log entry.
Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79341-MethodsRelatedToRichtextConfiguration.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79341-MethodsRelatedToRichtextConfiguration.rst
similarity index 89%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-79341-MethodsRelatedToRichtextConfiguration.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79341-MethodsRelatedToRichtextConfiguration.rst
index 24f455051308..8e412b20975a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79341-MethodsRelatedToRichtextConfiguration.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79341-MethodsRelatedToRichtextConfiguration.rst
@@ -19,7 +19,7 @@ The following methods and method arguments have been deprecated:
Impact
======
-Using above methods or arguments throws deprecation log entries, the according methods will vanish with TYPO3 v9.
+Using above methods or arguments trigger deprecation log entries, the according methods will vanish with TYPO3 v9.
Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79341-TCARichtextConfigurationInDefaultExtrasDropped.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79341-TCARichtextConfigurationInDefaultExtrasDropped.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-79341-TCARichtextConfigurationInDefaultExtrasDropped.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79341-TCARichtextConfigurationInDefaultExtrasDropped.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79364-DeprecateMembersInPageLayoutController.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79364-DeprecateMembersInPageLayoutController.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-79364-DeprecateMembersInPageLayoutController.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79364-DeprecateMembersInPageLayoutController.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79440-TcaChanges.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79440-TcaChanges.rst
similarity index 99%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-79440-TcaChanges.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79440-TcaChanges.rst
index 57605ef72604..dd17381a390a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79440-TcaChanges.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79440-TcaChanges.rst
@@ -21,7 +21,7 @@ three different kinds:
* :code:`fieldWizard` - HTML typically shown below the element to enrich the element with further
functionality. Example is the rendering of thumbnails below a type=group element.
-Other wizards like the "suggest" functionality has been merged into the affected elements itself.
+Other wizards like the "suggest" functionality have been merged into the affected elements itself.
Additionally, the config option :code:`defaultExtras`, which was often set within :code:`columnsOverrides` has
been removed. The options were transferred to config options of the elements itself and can be set
@@ -201,7 +201,7 @@ Example after:
RTE wizard
^^^^^^^^^^
-The RTE wizard that jumps to a full screen view of a text field has been embedded into `ext:rtehtmlarea`
+The RTE wizard that jumps to a full screen view of a text field has been embedded into `EXT:rtehtmlarea`
directly and just needs to be turned on. This additionally obsoletes the :code:`defaultExtras=rte_only` setting.
Example before:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79441-ChangeVisibilityInternalCacheDatahandler.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79441-ChangeVisibilityInternalCacheDatahandler.rst
similarity index 64%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-79441-ChangeVisibilityInternalCacheDatahandler.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79441-ChangeVisibilityInternalCacheDatahandler.rst
index ab82e2be5062..d45c423812ca 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79441-ChangeVisibilityInternalCacheDatahandler.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79441-ChangeVisibilityInternalCacheDatahandler.rst
@@ -9,24 +9,24 @@ See :issue:`79441`
Description
===========
-The following variables have been marked as deprecated in the
-Datahandler since their visibility will change from public to
+The following variables have been marked as deprecated in
+DataHandler since their visibility will change from public to
protected or even be replaced by a run-time cache.
The documentation states that these are "internal-cache"
variables and hence the visibility public is misleading.
.. code-block:: php
- public $recUpdateAccessCache = [];
- public $recInsertAccessCache = [];
- public $isRecordInWebMount_Cache = [];
- public $isInWebMount_Cache = [];
- public $cachedTSconfig = [];
- public $pageCache = [];
+ public $recUpdateAccessCache = [];
+ public $recInsertAccessCache = [];
+ public $isRecordInWebMount_Cache = [];
+ public $isInWebMount_Cache = [];
+ public $cachedTSconfig = [];
+ public $pageCache = [];
The following variable has been marked as deprecated in the
-Datahandler since it is not referenced in the class.
+DataHandler since it is not referenced in the class.
.. code-block:: php
@@ -37,7 +37,7 @@ Datahandler since it is not referenced in the class.
Impact
======
-These variables should not be accessed in Datahandler from outside
+These variables should not be accessed in DataHandler from outside
the class since their visibility or even implementation will
change with TYPO3 v9.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79560-DeprecateClientUtilitygetDeviceType.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79560-DeprecateClientUtilitygetDeviceType.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-79560-DeprecateClientUtilitygetDeviceType.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79560-DeprecateClientUtilitygetDeviceType.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79622-DeprecationOfCSSStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79622-DeprecationOfCSSStyledContent.rst
similarity index 78%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-79622-DeprecationOfCSSStyledContent.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79622-DeprecationOfCSSStyledContent.rst
index c8e7b5029a79..26b62fc29471 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-79622-DeprecationOfCSSStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79622-DeprecationOfCSSStyledContent.rst
@@ -9,16 +9,16 @@ See :issue:`79622`
Description
===========
-CSS Styled Content has been a long time the preferred way of rendering
-content in the frontend. Fluid Styled Content was introduced as
+CSS Styled Content has been the preferred way of rendering
+content in the frontend for a long time. Fluid Styled Content has been introduced as
successor of CSC, but the feature set diverged from the beginning. The
-lack of flexibility and incomplete feature set in comparision to CSC made
+lack of flexibility and incomplete feature set in comparison to CSC made
it hard to migrate existing instances.
Since TYPO3 CMS 7.6 Fluid-Templates are the defined standard and
official recommendation for content rendering. The feature set of FSC is
now matching CSC. Both content renderings are now streamlined to be fully
-compatible with each other. For the period of CMS 8 LTS CSC will share
+compatible with each other. For the period of CMS 8 CSC will share
the same capabilities to make a transition as easy as possible. CSC is
now deprecated and goes into maintenance mode and will be removed with
CMS 9.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-12211-UsabilitySchedulerProvidePageBrowserToChooseStartPage.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-12211-UsabilitySchedulerProvidePageBrowserToChooseStartPage.rst
similarity index 91%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-12211-UsabilitySchedulerProvidePageBrowserToChooseStartPage.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-12211-UsabilitySchedulerProvidePageBrowserToChooseStartPage.rst
index f7f9657cdc7f..bec085e364bf 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-12211-UsabilitySchedulerProvidePageBrowserToChooseStartPage.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-12211-UsabilitySchedulerProvidePageBrowserToChooseStartPage.rst
@@ -15,7 +15,7 @@ To improve the usability of the linkvalidator scheduler task, the page browser i
Impact
======
-Scheduler tasks that needs a page `uid` can now add a button for the page browser popup.
+Scheduler tasks that need a page `uid` can now add a button for the page browser popup.
In the `ValidatorTaskAdditionalFieldProvider` two additional fields have to be added.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-28171-ImprovedLinkFieldInFormEngine.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-28171-ImprovedLinkFieldInFormEngine.rst
similarity index 86%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-28171-ImprovedLinkFieldInFormEngine.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-28171-ImprovedLinkFieldInFormEngine.rst
index 629afb49125b..51c749806e9d 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-28171-ImprovedLinkFieldInFormEngine.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-28171-ImprovedLinkFieldInFormEngine.rst
@@ -9,8 +9,8 @@ See :issue:`28171`
Description
===========
-The handling of link fields when managing records has been improved and now shows a speaking string,
-an icon and an additional help text instead of the cryptic :code:`t3://` syntaxt. This is enabled
+The handling of link fields when managing records has been improved and now shows a human readable string,
+an icon and an additional help text instead of the cryptic :code:`t3://` syntax. This is enabled
by default for all :code:`renderType="inputLink"` elements.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-45537-RunManuallyExecutedTasksOnNextCron-run.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-45537-RunManuallyExecutedTasksOnNextCron-run.rst
similarity index 85%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-45537-RunManuallyExecutedTasksOnNextCron-run.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-45537-RunManuallyExecutedTasksOnNextCron-run.rst
index 77b327df819f..be344b16fe73 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-45537-RunManuallyExecutedTasksOnNextCron-run.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-45537-RunManuallyExecutedTasksOnNextCron-run.rst
@@ -11,6 +11,6 @@ Description
There is a new action icon to mark a task to be run by cron.
Also a new button "Execute selected tasks on next cron job"
-was added to mark all selected actions to be run by next cron job.
+has been added to mark all selected actions to be run by next cron job.
.. index:: Backend
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-47006-ExtendTheWidgetIdentifierWithCustomString.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-47006-ExtendTheWidgetIdentifierWithCustomString.rst
similarity index 68%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-47006-ExtendTheWidgetIdentifierWithCustomString.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-47006-ExtendTheWidgetIdentifierWithCustomString.rst
index 71d2c21d6ace..265877312eca 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-47006-ExtendTheWidgetIdentifierWithCustomString.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-47006-ExtendTheWidgetIdentifierWithCustomString.rst
@@ -9,12 +9,12 @@ See :issue:`47006`
Description
===========
-The parameter "customWidgetId" has been introduced for fluid widgets. This string is used in the widget identifier
-in addition to the nextWidgetNumber.
+The parameter `customWidgetId` has been introduced for fluid widgets. This string is used in the widget identifier
+in addition to the `nextWidgetNumber`.
The widget identifier is used to create the GET parameter names.
-A good value for the customWidgetId is the {contentObjectData.uid}.
+A good value for the `customWidgetId` is the {contentObjectData.uid} to ensure no collisions happen.
Example:
.. code-block:: html
@@ -25,6 +25,6 @@ Example:
Impact
======
-Allows to use the same fluid widget more then once on one page in different content elements.
+Allows to use the same fluid widget more than once on one page in different content elements.
.. index:: Fluid
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-47135-PasteIconsAvailableAtPastingPositionAndUseModalNow.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-47135-PasteIconsAvailableAtPastingPositionAndUseModalNow.rst
similarity index 64%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-47135-PasteIconsAvailableAtPastingPositionAndUseModalNow.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-47135-PasteIconsAvailableAtPastingPositionAndUseModalNow.rst
index 5dcec9dbebb6..cee7d5fe8242 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-47135-PasteIconsAvailableAtPastingPositionAndUseModalNow.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-47135-PasteIconsAvailableAtPastingPositionAndUseModalNow.rst
@@ -9,9 +9,9 @@ See :issue:`47135`
Description
===========
-As soon as the normal clipboard contains an item, there will be a single paste icon available in the page module.
-The icon will be located at each possible pasting position directly besides the [content +] buttons.
+As soon as the normal clipboard contains an item, a single paste icon becomes available in the page module.
+The icon is located at each possible pasting position directly besides the [content +] buttons.
When the user clicks on the icon, a modal pops up to have the user confirm the action.
-Depending on the clibpoard mode this will either be "Copy" or "Move" together with the title of the item in the clipboard and a "Cancel" button.
+Depending on the clipboard mode this will either be "Copy" or "Move" together with the title of the item in the clipboard and a "Cancel" button.
.. index:: Backend, JavaScript
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-51291-SynchronizedFieldValuesInLocalizedRecords.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-51291-SynchronizedFieldValuesInLocalizedRecords.rst
similarity index 91%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-51291-SynchronizedFieldValuesInLocalizedRecords.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-51291-SynchronizedFieldValuesInLocalizedRecords.rst
index f938d286a0c4..78677489722e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-51291-SynchronizedFieldValuesInLocalizedRecords.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-51291-SynchronizedFieldValuesInLocalizedRecords.rst
@@ -9,7 +9,7 @@ See :issue:`51291`
Description
===========
-The localized record overlay behaviour has been changed to make localization rows standalone.
+The localized record overlay behaviour has been changed to make localization-rows standalone.
Previously, if fields in :code:`TCA` columns were set to :code:`l10n_mode` :code:`exclude`
or :code:`mergeIfNotBlank`, the localized record overlay did not contain values, and those
@@ -39,8 +39,8 @@ A typical configuration looks like that:
],
],
-:code:`TCA` tables that configure the language localization get field :code:`l10n_state` added by the schema analyzer
-which stores an json array with field names and the values :code:`custom`, :code:`parent` or :code:`source` to
+:code:`TCA` tables that configure the language localization get the field :code:`l10n_state` added by the schema analyzer
+which stores a json string with field names and the values :code:`custom`, :code:`parent` or :code:`source` to
specify if and from which record a single field gets its value.
.. index:: Backend, Database, Frontend, PHP-API, TCA
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-67243-ImplementFoldingOfSchedulerTaskGroups.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-67243-ImplementFoldingOfSchedulerTaskGroups.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-67243-ImplementFoldingOfSchedulerTaskGroups.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-67243-ImplementFoldingOfSchedulerTaskGroups.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-69572-PageModuleNoticeContentIsAlsoShownOn.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-69572-PageModuleNoticeContentIsAlsoShownOn.rst
new file mode 100644
index 000000000000..30e5efd48287
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-69572-PageModuleNoticeContentIsAlsoShownOn.rst
@@ -0,0 +1,21 @@
+.. include:: ../../Includes.txt
+
+================================================================
+Feature: #69572 - Page module Notice "Content is also shown on:"
+================================================================
+
+See :issue:`69572`
+
+Description
+===========
+
+When page content is inherited from a different page via "Show content from page" there is a notice displayed on the page that is pulling in content from a different page.
+
+As of now, the page whose content is used on other pages gets an info box that indicates which other pages use these contents.
+
+Impact
+======
+
+On pages that are inherited elsewhere you see a notice which links to the pages where the content is inherited.
+
+.. index:: Backend
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-70316-IntroduceSessionStorageFramework.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-70316-IntroduceSessionStorageFramework.rst
similarity index 98%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-70316-IntroduceSessionStorageFramework.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-70316-IntroduceSessionStorageFramework.rst
index dee1179eed25..309354038680 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-70316-IntroduceSessionStorageFramework.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-70316-IntroduceSessionStorageFramework.rst
@@ -46,7 +46,7 @@ sessions (default for `FE`), the `has_anonymous` option must be set to true.
The :php:`RedisSessionBackend` requires a running PHP redis module (PHP extension "redis") and a running redis service.
By default, a connection will be made to `hostname` 127.0.0.1 and `port` 3679. You may also specify a `database`
-number which to store the sessions in (default database is 0) and also a `password` for the connection.
+number which to store the sessions in (default database is 0) and a `password` for the connection.
A developer may implement a custom session backend. To achieve this, the interface
:php:`\TYPO3\CMS\Core\Session\Backend\SessionBackendInterface` has to be implemented.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-72749-CLISupportForT3DImport.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-72749-CLISupportForT3DImport.rst
similarity index 88%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-72749-CLISupportForT3DImport.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-72749-CLISupportForT3DImport.rst
index 224742b2779e..04bd409a2df7 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-72749-CLISupportForT3DImport.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-72749-CLISupportForT3DImport.rst
@@ -10,7 +10,7 @@ See :issue:`72749`
Description
===========
-The impexp extension now allows to import data files (T3D or XML) via the command line interface through a Symfony
+EXT:impexp now allows to import data files (T3D or XML) via the command line interface through a Symfony
Command.
Impact
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-75880-ImplementMultipleCroppingVariantsInImageManipulationTool.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-75880-ImplementMultipleCroppingVariantsInImageManipulationTool.rst
similarity index 96%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-75880-ImplementMultipleCroppingVariantsInImageManipulationTool.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-75880-ImplementMultipleCroppingVariantsInImageManipulationTool.rst
index 81a429ca8daf..9ce3dc3e53c3 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-75880-ImplementMultipleCroppingVariantsInImageManipulationTool.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-75880-ImplementMultipleCroppingVariantsInImageManipulationTool.rst
@@ -9,7 +9,7 @@ See :issue:`75880`
Description
===========
-The imageManipulation TCA type is now capable to handle multiple crop variants if configured.
+The `imageManipulation` TCA type is now capable to handle multiple crop variants if configured.
The default configuration is to have only one variant with the same possible aspect ratios
like in older TYPO3 versions.
@@ -137,7 +137,7 @@ Impact
TCA configuration for field type "imageManipulation" has changed. Old configuration options
still work but are deprecated and issue a warning when used.
-The TCA configuration option `enableZoom` has for now been removed. It wasn't really usable
+The TCA configuration option `enableZoom` has been removed for now. It wasn't really usable
anyway and will need some proper UX design before re-implementation. Setting the option
will have no effect.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-78169-IntroduceTranslationSourceFieldForTt_content.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78169-IntroduceTranslationSourceFieldForTt_content.rst
similarity index 77%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-78169-IntroduceTranslationSourceFieldForTt_content.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-78169-IntroduceTranslationSourceFieldForTt_content.rst
index 5308b7db9770..fe3206906f14 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-78169-IntroduceTranslationSourceFieldForTt_content.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78169-IntroduceTranslationSourceFieldForTt_content.rst
@@ -23,14 +23,14 @@ e.g.
The new field solves few issues:
1. There was no way to detect whether a record was translated using connected mode or free mode.
- If a record has value > 0 in the `transOrigPointerField` (e.g. `l10n_parent`) field, it means it was translated using "connected mode".
- If the `transOrigPointerField` is 0 but the `translationSource` field is > 0 it means it was translated using "free mode".
- If both are 0, it means the record was not translated but created manually.
+ If a record has value > 0 in the `transOrigPointerField` (e.g. `l10n_parent`) field, it means it was translated using "connected mode".
+ If the `transOrigPointerField` is 0 but the `translationSource` field is > 0 it means it was translated using "free mode".
+ If both are 0, it means the record was not translated but created manually.
-2. TYPO3 allows to use record in non-default language as a translation source. In this case the information about the translation source was lost.
- Now, the `translationSource` field always contains an uid of the record used as a translation source.
+2. TYPO3 allows to use a record in non-default language as a translation source. In this case the information about the translation source was lost.
+ Now, the `translationSource` field always contains an uid of the record used as a translation source.
-3. In some places `origUid` (e.g. `t3_origuid`) field was misused as a translation source. Now these places can be refactored to use the `translationSource` field.
+3. In some places `origUid` (e.g. `t3_origuid`) fields were misused as a translation source. Now these places can be refactored to use the `translationSource` field.
Difference between `translationSource` and other existing fields
----------------------------------------------------------------
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-78192-RefactorClickMenuContextMenu.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78192-RefactorClickMenuContextMenu.rst
similarity index 80%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-78192-RefactorClickMenuContextMenu.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-78192-RefactorClickMenuContextMenu.rst
index 3b5a3fd85e92..82ff28fa0a59 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-78192-RefactorClickMenuContextMenu.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78192-RefactorClickMenuContextMenu.rst
@@ -9,16 +9,16 @@ See :issue:`78192`
Description
===========
-Click menu (context menu) handling has been refactored and unified.
-The ExtJS/ExtDirect click menu used on the page tree has been replaced with jQuery based implementation.
-The same context menu implementation is used in all places in the Backend (page tree, page module, list module, file list, folder tree...).
+Click-menu (context-menu) handling has been refactored and unified.
+The ExtJS/ExtDirect click-menu used on the page tree has been replaced with a jQuery based implementation.
+The same context-menu implementation is used in all places in the Backend (page tree, page module, list module, file list, folder tree...).
-Context menu rendering flow
+Context-menu rendering flow
---------------------------
-Context menu is shown after click on the HTML element which has `class="t3js-contextmenutrigger"` together with `data-table`, `data-uid` and optional `data-context` attributes.
+The context-menu is shown after click on the HTML element which has `class="t3js-contextmenutrigger"` together with `data-table`, `data-uid` and optional `data-context` attributes.
-JavaScript click event handler is implemented in `TYPO3/CMS/Backend/ContextMenu` requireJS module. It takes data attributes mentioned above and executes an ajax call to the :php:`\TYPO3\CMS\Backend\Controller\ContextMenuController->getContextMenuAction()`.
+The JavaScript click event handler is implemented in the `TYPO3/CMS/Backend/ContextMenu` requireJS module. It takes the data attributes mentioned above and executes an ajax call to the :php:`\TYPO3\CMS\Backend\Controller\ContextMenuController->getContextMenuAction()`.
:php:`ContextMenuController` asks :php:`\TYPO3\CMS\Backend\ContextMenu\ContextMenu` to generate an array of items. ContextMenu builds a list of available item providers by asking each whether it can provide items (:php:`->canHandle()`), and what priority it has (:php:`->getPriority()`).
@@ -26,7 +26,7 @@ Custom item providers can be registered in :php:`$GLOBALS['TYPO3_CONF_VARS']['BE
A list of providers is sorted by priority, and then each provider is asked to add items. The generated array of items is passed from an item provider with higher priority to a provider with lower priority.
-After that, a compiled list of items is returned to the :php:`ContextMenuController` which passes it as JSON back to the ContextMenu.js.
+After that, a compiled list of items is returned to the :php:`ContextMenuController` which passes it back to the ContextMenu.js as JSON.
Example of the JSON response:
@@ -81,7 +81,7 @@ Example of the JSON response:
}
-Based on the JSON data ContextMenu.js is rendering a context menu. If one of the items is clicked, the according JS `callbackAction` is executed on the :js:`TYPO3/CMS/Backend/ContextMenuActions` JS module or other module defined in the `additionalAttributes['data-callback-module']`.
+Based on the JSON data ContextMenu.js is rendering a context-menu. If one of the items is clicked, the according JS `callbackAction` is executed on the :js:`TYPO3/CMS/Backend/ContextMenuActions` JS module or other modules defined in the `additionalAttributes['data-callback-module']`.
For example usage of this API see:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-78477-RefactoringOfFlashMessageRendering.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78477-RefactoringOfFlashMessageRendering.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-78477-RefactoringOfFlashMessageRendering.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-78477-RefactoringOfFlashMessageRendering.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-78899-TCAMaxitemsOptional.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78899-TCAMaxitemsOptional.rst
similarity index 99%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-78899-TCAMaxitemsOptional.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-78899-TCAMaxitemsOptional.rst
index 055a2bf40003..f2e2c9ab93c4 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-78899-TCAMaxitemsOptional.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78899-TCAMaxitemsOptional.rst
@@ -20,6 +20,7 @@ Fields that typically relate to multiple relations like the group element and so
Example before:
.. code-block:: php
+
aField => [
'config' => [
'type' => `select',
@@ -31,6 +32,7 @@ Example before:
Example after:
.. code-block:: php
+
aField => [
'config' => [
'type' => `select',
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79121-ImplementHookInTypolinkForModificationOfPageParams.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79121-ImplementHookInTypolinkForModificationOfPageParams.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79121-ImplementHookInTypolinkForModificationOfPageParams.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79121-ImplementHookInTypolinkForModificationOfPageParams.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79124-AllowOverwritingOfTemplatePathsInBackendTemplateView.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79124-AllowOverwritingOfTemplatePathsInBackendTemplateView.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79124-AllowOverwritingOfTemplatePathsInBackendTemplateView.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79124-AllowOverwritingOfTemplatePathsInBackendTemplateView.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79140-AddHookToAddCustomTypoScriptTemplates.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79140-AddHookToAddCustomTypoScriptTemplates.rst
new file mode 100644
index 000000000000..86fababab6fb
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79140-AddHookToAddCustomTypoScriptTemplates.rst
@@ -0,0 +1,65 @@
+.. include:: ../../Includes.txt
+
+=============================================================
+Feature: #79140 - Add hook to add custom TypoScript templates
+=============================================================
+
+See :issue:`79140`
+
+Description
+===========
+
+A new hook in TemplateService allows to add or modify existing TypoScript templates.
+
+Register the hook via :php:`$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['Core/TypoScript/TemplateService']['runThroughTemplatesPostProcessing']`
+in the extensions' ext_localconf.php file.
+
+Example
+=======
+
+An example implementation could look like this:
+
+EXT:my_site/ext_localconf.php
+
+.. code-block:: php
+
+ $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['Core/TypoScript/TemplateService']['runThroughTemplatesPostProcessing'][1313131313] =
+ \MyVendor\MySite\Hooks\TypoScriptHook::class . '->addCustomTypoScriptTemplate';
+
+
+EXT:my_site/Classes/Hooks/TypoScriptHook.php
+
+.. code-block:: php
+
+ namespace MyVendor\MySite\Hooks;
+
+ class TypoScriptHook
+ {
+
+ /**
+ * Hooks into TemplateService after
+ * @param array $parameters
+ * @param \TYPO3\CMS\Core\TypoScript\TemplateService $parentObject
+ * @return void
+ */
+ public function addCustomTypoScriptTemplate($parameters, $parentObject)
+ {
+ // Disable the inclusion of default TypoScript set via TYPO3_CONF_VARS
+ $parameters['isDefaultTypoScriptAdded'] = true;
+ // Disable the inclusion of ext_typoscript_setup.txt of all extensions
+ $parameters['processExtensionStatics'] = false;
+
+ // No template was found in rootline so far, so a custom "fake" sys_template record is added
+ if ($parentObject->outermostRootlineIndexWithTemplate === 0) {
+ $row = [
+ 'uid' => 'my_site_template',
+ 'config' => '<INCLUDE_TYPOSCRIPT: source="FILE:EXT:my_site/Configuration/TypoScript/site_setup.t3s">',
+ 'root' => 1,
+ 'pid' => 0
+ ];
+ $parentObject->processTemplate($row, 'sys_' . $row['uid'], 0, 'sys_' . $row['uid']);
+ }
+ }
+ }
+
+.. index:: PHP-API, TypoScript
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79196-AllowReloadOfTopbar.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79196-AllowReloadOfTopbar.rst
similarity index 96%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79196-AllowReloadOfTopbar.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79196-AllowReloadOfTopbar.rst
index dc8f5e70eabc..1eaa395ee8c1 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79196-AllowReloadOfTopbar.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79196-AllowReloadOfTopbar.rst
@@ -15,7 +15,7 @@ A new JavaScript API to reload the backend's topbar has been introduced to the T
Impact
======
-The toolbar reloading may be triggered on JavaScript and PHP code level. To enforce the reloading on PHP side,
+The toolbar reloading may be triggered on JavaScript and PHP code-level. To enforce the reloading on PHP side,
call :php:`\TYPO3\CMS\Backend\Utility\BackendUtility::setUpdateSignal('updateTopbar')`.
Reloading the topbar via JavaScript requires the following code:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79216-AddYAMLConfigurationForCKEditorRTE.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79216-AddYAMLConfigurationForCKEditorRTE.rst
similarity index 56%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79216-AddYAMLConfigurationForCKEditorRTE.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79216-AddYAMLConfigurationForCKEditorRTE.rst
index 8ec9d9815c5f..7249ff57c895 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79216-AddYAMLConfigurationForCKEditorRTE.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79216-AddYAMLConfigurationForCKEditorRTE.rst
@@ -9,25 +9,28 @@ See :issue:`79216`
Description
===========
-The CKEditor-flavored RTE can now be configured via YAML files, defined as presets.
+The CKEditor-flavored RTE can now be configured via YAML files, defined as *presets*.
A preset contains both the RTE configuration and the HTML processing when storing the content
in the database.
A YAML file for RTE configurations can be registered by any extension in `ext_localconf.php`:
-$GLOBALS['TYPO3_CONF_VARS']['RTE']['Presets']['default'] = 'EXT:rte_ckeditor/Configuration/RTE/Default.yaml';
+:php:`$GLOBALS['TYPO3_CONF_VARS']['RTE']['Presets']['default'] = 'EXT:rte_ckeditor/Configuration/RTE/Default.yaml';`
-The TYPO3 Core ships with three flavors for the RTE configuration which can also be overriden via
+The TYPO3 Core ships with three flavors for the RTE configuration which can also be overridden via
PageTSconfig on a per-field/type level:
-RTE.default.preset = minimal
-RTE.tt_content.types.textmedia.bodytext.preset = full
+.. code-block:: typoscript
+
+ RTE.default.preset = minimal
+ RTE.tt_content.types.textmedia.bodytext.preset = full
+
The PageTSconfig allows to use the minimal configuration everywhere, but to use the full
-configuration on tt_content.bodytext field (but only for textmedia content types).
+configuration on the tt_content.bodytext field (but only for textmedia content types).
-With the YAML configuration files, a "imports" functionality is allowed to import other
+With the YAML configuration files, an "imports" functionality allows to import other
configuration and just override the necessary values for a custom configuration for a specific site.
This way, the processing part of EXT:rte_ckeditor can be used directly (which acts as best practice)
but the editor part can be completely customized.
@@ -35,13 +38,13 @@ but the editor part can be completely customized.
The YAML format thus states three important parts considered by the RTE configuration preset:
1. "imports"
-Allows to import other files via the "resource" sub-property
+ Allows to import other files via the "resource" sub-property
2. "processing"
-uses the former "proc" options to hand over to RteHtmlParser to sanitize the content - the option
-are the same as for RTEHtmlArea
+ uses the former "proc" options to hand over to RteHtmlParser to sanitize the content - the option
+ are the same as for RTEHtmlArea
3. "editor"
-A configuration for CKEditor, where all CKEditor-related options can be set which are available
-from the ckeditor configuration specifications (see http://docs.ckeditor.com/#!/api/CKEDITOR.config
-for all options).
+ A configuration for CKEditor, where all CKEditor-related options can be set which are available
+ from the ckeditor configuration specifications (see http://docs.ckeditor.com/#!/api/CKEDITOR.config
+ for all options).
.. index:: LocalConfiguration, RTE
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79225-PluginPreviewWithFluid.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79225-PluginPreviewWithFluid.rst
similarity index 94%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79225-PluginPreviewWithFluid.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79225-PluginPreviewWithFluid.rst
index 467148b823d0..c7421d49687c 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79225-PluginPreviewWithFluid.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79225-PluginPreviewWithFluid.rst
@@ -10,7 +10,7 @@ Description
===========
The page TSconfig to render a preview of a single content element in the Backend has been improved
-by allowing the rendering of plugins now as well.
+by allowing the rendering of plugins as well.
The following option allows to override the default output of a plugin via page TSconfig:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79235-AddButtonToDeleteSimilarErrorsFromSys_log.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79235-AddButtonToDeleteSimilarErrorsFromSys_log.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79235-AddButtonToDeleteSimilarErrorsFromSys_log.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79235-AddButtonToDeleteSimilarErrorsFromSys_log.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79240-SingleCliUserForCliCommands.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79240-SingleCliUserForCliCommands.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79240-SingleCliUserForCliCommands.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79240-SingleCliUserForCliCommands.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79250-ExtFormExtendExtensionLocationFunctionality.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79250-ExtFormExtendExtensionLocationFunctionality.rst
similarity index 89%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79250-ExtFormExtendExtensionLocationFunctionality.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79250-ExtFormExtendExtensionLocationFunctionality.rst
index 6080aff759fc..791bb2b85864 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79250-ExtFormExtendExtensionLocationFunctionality.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79250-ExtFormExtendExtensionLocationFunctionality.rst
@@ -1,7 +1,7 @@
.. include:: ../../Includes.txt
======================================================================
-Feature: #79250 - Ext:form extend the extension location functionality
+Feature: #79250 - EXT:form extend the extension location functionality
======================================================================
See :issue:`79250`
@@ -9,8 +9,8 @@ See :issue:`79250`
Description
===========
-Ext:form has a feature to load custom form definitions from within extension locations.
-This locations can be configured through the :code:`allowedExtensionPaths` setting.
+EXT:form has a feature to load custom form definitions from within extension locations.
+These locations can be configured through the :code:`allowedExtensionPaths` setting.
To define whether forms can be changed from within extension locations through the form editor, a setting named :code:`allowSaveToExtensionPaths` exists.
But this setting affects only already existing form definitions within extension locations.
This feature makes it possible to store new forms within extension locations through the form manager as well.
@@ -18,6 +18,7 @@ You can also define whether forms can be deleted within extension locations thro
By default both settings :code:`allowSaveToExtensionPaths` and :code:`allowDeleteFromExtensionPaths` are disabled.
Summary
+=======
With this patch is it possible to:
@@ -32,6 +33,8 @@ Impact
Example to allow edit form definitions within 'EXT:my_ext/Resources/Private/Forms/':
.. code-block:: yaml
+
+
TYPO3:
CMS:
Form:
@@ -44,6 +47,7 @@ Example to allow edit form definitions within 'EXT:my_ext/Resources/Private/Form
Example to allow remove form definitions within 'EXT:my_ext/Resources/Private/Forms/':
.. code-block:: yaml
+
TYPO3:
CMS:
Form:
@@ -52,4 +56,5 @@ Example to allow remove form definitions within 'EXT:my_ext/Resources/Private/Fo
allowedExtensionPaths:
100: EXT:my_ext/Resources/Private/Forms/
+
.. index:: Backend, ext:form
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79262-AddPossibilityToCreateTRIMExpressionWithDoctrineDBAL.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79262-AddPossibilityToCreateTRIMExpressionWithDoctrineDBAL.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79262-AddPossibilityToCreateTRIMExpressionWithDoctrineDBAL.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79262-AddPossibilityToCreateTRIMExpressionWithDoctrineDBAL.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79263-SchedulerCLIAvailableAsSymfonyCommand.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79263-SchedulerCLIAvailableAsSymfonyCommand.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79263-SchedulerCLIAvailableAsSymfonyCommand.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79263-SchedulerCLIAvailableAsSymfonyCommand.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79337-AddUseCacheHashParameterToFlinktypolinkAndFuritypolink.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79337-AddUseCacheHashParameterToFlinktypolinkAndFuritypolink.rst
similarity index 56%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79337-AddUseCacheHashParameterToFlinktypolinkAndFuritypolink.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79337-AddUseCacheHashParameterToFlinktypolinkAndFuritypolink.rst
index 02ee5912ab8f..448a37880b9e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79337-AddUseCacheHashParameterToFlinktypolinkAndFuritypolink.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79337-AddUseCacheHashParameterToFlinktypolinkAndFuritypolink.rst
@@ -9,6 +9,12 @@ See :issue:`79337`
Description
===========
-The current implementation of the two typolink viewhelpers is lacking support of all sorts of typolink parameters, the useCacheHash parameter being the most important one.
+The older implementation of the two typolink ViewHelpers was lacking support of the useCacheHash parameter.
+
+The boolean argument `useCacheHash` has been added to the typoscript Viewhelpers.
+
+.. code-block:: html
+
+ <f:link.typolink parameter="{link}" useCacheHash="true">
.. index:: Fluid, Frontend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79341-TCARichtextConfigurationInConfigSection.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79341-TCARichtextConfigurationInConfigSection.rst
similarity index 66%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79341-TCARichtextConfigurationInConfigSection.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79341-TCARichtextConfigurationInConfigSection.rst
index 7655192135ff..9ff34c8f0910 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79341-TCARichtextConfigurationInConfigSection.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79341-TCARichtextConfigurationInConfigSection.rst
@@ -9,13 +9,13 @@ See :issue:`79341`
Description
===========
-A new config item "enableRichtext" has been introduced. It enables richtext editing on the text field and replaces the old setting under "defaultExtras".
+A new config setting `enableRichtext` has been introduced. It enables richtext editing on the text field and replaces the old setting `defaultExtras`.
Impact
======
-Setting enableRichtext will result in the text field being rendered with a richtext editor. Config example:
+Setting `enableRichtext` will result in the text field being rendered with a richtext editor. Config example:
.. code-block:: php
'columns' => [
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79387-AddSignalToExcludeTablesFromReferenceIndex.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79387-AddSignalToExcludeTablesFromReferenceIndex.rst
similarity index 92%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79387-AddSignalToExcludeTablesFromReferenceIndex.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79387-AddSignalToExcludeTablesFromReferenceIndex.rst
index aa6c4162fed9..ee9d6e528e25 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79387-AddSignalToExcludeTablesFromReferenceIndex.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79387-AddSignalToExcludeTablesFromReferenceIndex.rst
@@ -49,8 +49,8 @@ Your class could look like this:
Impact
======
-This signal allows extensions to speed up the process of maintaining the ReferenceIndex: If an extension has tables in which by definition none of its columns
-can contain any relations to other records it can be excluded from ReferenceIndex.
+This signal allows extensions to speed up the process of maintaining the ReferenceIndex. If an extension has tables in which by definition none of its columns
+can contain any relations to other records these can be excluded from the ReferenceIndex.
Only exclude tables from ReferenceIndex which do not contain any relations and never did since existing references won't be deleted if it is excluded! There is
no need to add tables without a definition in :php:`$GLOBALS['TCA]` since ReferenceIndex only handles those.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79402-VariableViewHelperForFluid.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79402-VariableViewHelperForFluid.rst
similarity index 97%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79402-VariableViewHelperForFluid.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79402-VariableViewHelperForFluid.rst
index 214d67dfd824..b3602b69e451 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79402-VariableViewHelperForFluid.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79402-VariableViewHelperForFluid.rst
@@ -15,8 +15,6 @@ The ViewHelper allows variables to be assigned in the template:
.. code-block:: html
- Assign a variable
-
<f:variable name="myvariable">My variable's content</f:variable>
<f:variable name="myvariable" value="My variable's content"/>
{f:variable(name: 'myvariable', value: 'My variable\'s content')}
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79409-AutorenderAssetSectionsInFluidTemplateWithController.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79409-AutorenderAssetSectionsInFluidTemplateWithController.rst
similarity index 88%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79409-AutorenderAssetSectionsInFluidTemplateWithController.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79409-AutorenderAssetSectionsInFluidTemplateWithController.rst
index b7465bbd9166..42eca62dd578 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79409-AutorenderAssetSectionsInFluidTemplateWithController.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79409-AutorenderAssetSectionsInFluidTemplateWithController.rst
@@ -10,7 +10,7 @@ See :issue:`73409`
Description
===========
-ActionController has received a new method, `renderAssetsForRequest` which receives the `RequestInterface`
+ActionController has received a new method, `renderAssetsForRequest` which receives the `RequestInterface` of the
Request currently being processed. The ActionController has a default implementation of this method which attempts
to render two sections in the Fluid template that is associated with the controller action being called:
@@ -22,7 +22,7 @@ Both sections are optional.
When rendering, `{request}` is available as template variable in both sections, as is `{arguments}`, allowing you
to make decisions based on various request/controller arguments. As usual, `{settings}` is also available.
-All content you write into these sections will be output in the respective location, meaning you must write the entire
+All content you write into these sections will be output in the respective location as is, meaning you must write the entire
`<script>` or whichever tag you are writing, including all attributes. You can of course use various Fluid ViewHelpers
to resolve extension asset paths.
@@ -33,11 +33,11 @@ extends either TemplateView or AbstractTemplateView from TYPO3's Fluid adapter).
Impact
======
-* Fluid templates renderered through any ActionController using a TemplateView may now contain two new sections for
+* Fluid templates rendered through any ActionController using a TemplateView may now contain two new sections for
either `HeaderAssets` or `FooterAssets` depending on desired output. Content of these sections will be rendered
and assigned via PageRenderer to either header or footer.
* ActionControllers can override the `renderAssetsForRequest` method to perform asset insertion using other means.
The method sits at a very opportune point right after the action method itself gets called, when the entire controller
- is fully initialized with arguments etc. but no forwarding/rediction has happened in the controller action.
+ is fully initialized with arguments etc. but no forwarding/redirection has happened in the controller action.
.. index:: Fluid, Frontend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79413-AutorenderAssetSectionsInFluidTemplateContentObject.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79413-AutorenderAssetSectionsInFluidTemplateContentObject.rst
similarity index 81%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79413-AutorenderAssetSectionsInFluidTemplateContentObject.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79413-AutorenderAssetSectionsInFluidTemplateContentObject.rst
index 33bd74bf0c48..4d007a636dfd 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79413-AutorenderAssetSectionsInFluidTemplateContentObject.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79413-AutorenderAssetSectionsInFluidTemplateContentObject.rst
@@ -13,8 +13,8 @@ Description
FLUIDTEMPLATE content object will now automatically render two sections and insert the rendered content as assets via
PageRenderer. The two sections can be defined in the template file rendered by the FLUIDTEMPLATE object.
-* `<f:section name="HeaderAssets">` for assets intented for the `<head>` tag
-* `<f:section name="FooterAssets">` for assets intented for the end of the `<body>` tag
+* `<f:section name="HeaderAssets">` for assets intended for the `<head>` tag
+* `<f:section name="FooterAssets">` for assets intended for the end of the `<body>` tag
Both sections are optional.
@@ -22,7 +22,7 @@ When rendering, `{contentObject}` is available as template variable in both sect
based on various aspects of the configured content object instance. In addition, all variables you declared for the
content object are available when rendering either section.
-All content you write into these sections will be output in the respective location, meaning you must write the entire
+All content you write into these sections will be output in the respective location as is, meaning you must write the entire
`<script>` or whichever tag you are writing, including all attributes. You can of course use various Fluid ViewHelpers
to resolve extension asset paths.
@@ -30,7 +30,7 @@ to resolve extension asset paths.
Impact
======
-* Fluid templates renderered through the FLUIDTEMPLATE content object may now contain two new sections for either
+* Fluid templates rendered through the FLUIDTEMPLATE content object may now contain two new sections for either
`HeaderAssets` or `FooterAssets` depending on desired output. Content of these sections will be rendered
and assigned via PageRenderer to either header or footer.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79420-HideFilesFromListOfDocumentation.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79420-HideFilesFromListOfDocumentation.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79420-HideFilesFromListOfDocumentation.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79420-HideFilesFromListOfDocumentation.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79438-OptionToDisableValidationOfStoredRecords.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79438-OptionToDisableValidationOfStoredRecords.rst
similarity index 98%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79438-OptionToDisableValidationOfStoredRecords.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79438-OptionToDisableValidationOfStoredRecords.rst
index db83bb63b719..93b38825c2af 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79438-OptionToDisableValidationOfStoredRecords.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79438-OptionToDisableValidationOfStoredRecords.rst
@@ -42,7 +42,7 @@ Impact
======
In TYPO3 installations where the administrator has configured the database to run in strict-mode
-disabling the validation of stored records can speed-up inserts and updates by a factor 2. With
+disabling the validation of stored records can speed-up inserts and updates by a factor of 2. With
strict-mode enabled the record will not be saved at all, if there are errors.
If the validation of stored records is disabled, the entry in the protocol (sys_log) does not
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79440-FormEngineElementExpansion.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79440-FormEngineElementExpansion.rst
similarity index 94%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79440-FormEngineElementExpansion.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79440-FormEngineElementExpansion.rst
index dffdfad74a5c..5c8ff163723c 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79440-FormEngineElementExpansion.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79440-FormEngineElementExpansion.rst
@@ -9,16 +9,16 @@ See :issue:`79440`
Description
===========
-A new API in FormEngine has been introduced that allowes fine grained additions to
+A new API in FormEngine has been introduced that allows fine grained additions to
single elements and containers without substituting the whole element.
-For elements, within the :code:`TCA` config section, three new options have been introduced:
+For elements within the :code:`TCA` config section, three new options have been introduced:
-* :code:`fieldInformation` An array of single field information. This could be additional describing text
+* :code:`fieldInformation` An array of single field information. This could be additionally describing text
that is rendered between the element label and the element itself. Field information are restricted, only
a couple of HTML tags are allowed within the result HTML.
* :code:`fieldControl` An array of single field controls. These are icons with JavaScript or
- links to further functionality of the framework. They are usually displaed next to the element. Each control
+ links to further functionality of the framework. They are usually displayed next to the element. Each control
must return an icon identifier, a title, and an array of a-tag attributes.
* :code:`fieldWizard` Additional functionality enriching the element. These are typically shown
below the element. Wizards may return any HTML.
@@ -28,7 +28,7 @@ the :code:`OuterWrapContainer` which renders the record title and delegates the
a different container. Adding :code:`fieldInformation` or :code:`fieldWizard` here allows embedding additional
functionality between the record title an the main record body.
-Single elements and container may register default information, control and wizards. The configuration is merged
+Single elements and containers may register default information, control and wizards. The configuration is merged
with any possibly given configuration from `TCA`.
Example from :code:`GroupElement`:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79442-EXTform-AddElementSelectorForTextEditors.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79442-EXTform-AddElementSelectorForTextEditors.rst
similarity index 90%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79442-EXTform-AddElementSelectorForTextEditors.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79442-EXTform-AddElementSelectorForTextEditors.rst
index e4ffa7aa5fed..5e50734dd9ca 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79442-EXTform-AddElementSelectorForTextEditors.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79442-EXTform-AddElementSelectorForTextEditors.rst
@@ -9,6 +9,6 @@ See :issue:`79442`
Description
===========
-A new button has been added to the text editors of the form editor. Clicking on this button opens an overlay with available form elements of the current form. The user has the possibility to choose one of these form elements. The process adds the dynamic identifier (e.g. "{text-1}" to the current tex editor field.
+A new button has been added to the text editors of the form editor. Clicking on this button opens an overlay with available form elements of the current form. The user has the possibility to choose one of these form elements. The process adds the dynamic identifier (e.g. "{text-1}" to the current text editor field.
.. index:: Backend, ext:form
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79467-EXTform-AddFormSettingsButtonToModuleHeader.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79467-EXTform-AddFormSettingsButtonToModuleHeader.rst
similarity index 69%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79467-EXTform-AddFormSettingsButtonToModuleHeader.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79467-EXTform-AddFormSettingsButtonToModuleHeader.rst
index 4e8c54542fc4..5136f642645a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79467-EXTform-AddFormSettingsButtonToModuleHeader.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79467-EXTform-AddFormSettingsButtonToModuleHeader.rst
@@ -9,6 +9,6 @@ See :issue:`79467`
Description
===========
-A new button has been added the module header of the form editor. Clicking on this button shows the form settings within the inspector.
+A new button has been added to the module header of the form editor. Clicking on this button shows the form settings within the inspector.
.. index:: Backend, ext:form
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79521-ShowListOfFailedInputElementsInFormEngine.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79521-ShowListOfFailedInputElementsInFormEngine.rst
similarity index 91%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79521-ShowListOfFailedInputElementsInFormEngine.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79521-ShowListOfFailedInputElementsInFormEngine.rst
index c31483b53b11..7a6e1d509d00 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79521-ShowListOfFailedInputElementsInFormEngine.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79521-ShowListOfFailedInputElementsInFormEngine.rst
@@ -9,7 +9,7 @@ See :issue:`79521`
Description
===========
-When validating input fields of the FormEngine fails, a button is now rendered into the least possible button bar in
+When validating input fields of the FormEngine fails, a button is now rendered into the button bar in
the module document header. Clicking the button renders a list of all input elements whose validation failed.
Clicking onto a field in that list automatically focuses the field in the form.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79530-EXTform-ExtendSaveToDatabaseFinisher.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79530-EXTform-ExtendSaveToDatabaseFinisher.rst
similarity index 83%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79530-EXTform-ExtendSaveToDatabaseFinisher.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79530-EXTform-ExtendSaveToDatabaseFinisher.rst
index 39f79e749d3e..b12c49e51f9a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79530-EXTform-ExtendSaveToDatabaseFinisher.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79530-EXTform-ExtendSaveToDatabaseFinisher.rst
@@ -14,7 +14,9 @@ The SaveToDatabase finisher has been extended by the following functions:
Perform multiple database operations
------------------------------------
-You can set options as an array to perform multiple database oprtations.
+You can set options as an array to perform multiple database operations.
+
+.. code-block:: yaml
finishers:
-
@@ -47,6 +49,8 @@ Add a special option value '{__currentTimestamp}'
You can write '{__currentTimestamp}' as an option value which returns the current timestamp.
+.. code-block:: yaml
+
finishers:
-
identifier: SaveToDatabase
@@ -61,16 +65,20 @@ You can write '{__currentTimestamp}' as an option value which returns the curren
Add a variable container object which is passed through all finishers
---------------------------------------------------------------------
-There is a simple data storage object availabe within the '\TYPO3\CMS\Form\Domain\Finishers\FinisherContext'.
-Access is from within a finisher with
+There is a simple data storage object available within the '\TYPO3\CMS\Form\Domain\Finishers\FinisherContext'.
+You can access this from within a finisher with
+
+.. code-block:: php
$this->finisherContext->getFinisherVariableProvider()
-Each finisher can write and/ or read data from this object.
-All data has to be prefixed with the finisher identifier, so you can determine what data from what finisher you want.
+Each finisher can write and/or read data from this object.
+All data has to be prefixed with the finisher identifier, so you can determine what data from which finisher you want.
Prototype to add some data:
+.. code-block:: php
+
$this->finisherContext->getFinisherVariableProvider()->add(
$this->shortFinisherIdentifier,
'some.data',
@@ -79,15 +87,19 @@ Prototype to add some data:
Prototype to get some data:
+.. code-block:: php
+
$otherFinisherData = $this->finisherContext->getFinisherVariableProvider()->get(
'SomeFinisherIdentifier',
'some.data'
);
-Access this data within the form definition:
+You can access this data within the form definition:
For example, a finisher with identifier 'SomeFinisherIdentifier' writes data with the key 'some.data'
+.. code-block:: yaml
+
finishers:
-
identifier: SaveToDatabase
@@ -100,6 +112,6 @@ For example, a finisher with identifier 'SomeFinisherIdentifier' writes data wit
value: '{SomeFinisherIdentifier.some.key}'
You can read more about the configuration options within the SaveToDatabase inline documentation.
-Please see \TYPO3\CMS\Form\Domain\Finishers\SaveToDatabaseFinisher.
+Please see `\TYPO3\CMS\Form\Domain\Finishers\SaveToDatabaseFinisher`.
.. index:: Frontend, ext:form
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79531-EXTform-AddInspectorMultiselectEditors.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79531-EXTform-AddInspectorMultiselectEditors.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79531-EXTform-AddInspectorMultiselectEditors.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79531-EXTform-AddInspectorMultiselectEditors.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79622-HeaderPositionSupportForFluidStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-HeaderPositionSupportForFluidStyledContent.rst
similarity index 94%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79622-HeaderPositionSupportForFluidStyledContent.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-HeaderPositionSupportForFluidStyledContent.rst
index 45811f04f1fa..e4559021794e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79622-HeaderPositionSupportForFluidStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-HeaderPositionSupportForFluidStyledContent.rst
@@ -14,8 +14,8 @@ Fluid Styled Content. This will allow the editor to have more control about
the alignment of the header in the frontend.
By default all CSS classes for header alignment are prefixed with
-`ce-headline-` to make the css class unique to allow even more adjustments
-without breaking your styling somwhere else.
+`ce-headline-` to make the css class unique and to allow even more adjustments
+without breaking your styling somewhere else.
Predefined values for header alignment and resulting CSS classes
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79622-NewContentElementsForFluidStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-NewContentElementsForFluidStyledContent.rst
similarity index 93%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79622-NewContentElementsForFluidStyledContent.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-NewContentElementsForFluidStyledContent.rst
index e3fbbf7d2b86..3ccb443ff1e6 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79622-NewContentElementsForFluidStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-NewContentElementsForFluidStyledContent.rst
@@ -25,7 +25,7 @@ Impact
======
The content elements Text, Text and Images, Images are now also available
-for use when Fluid Styled Content is used as content rendering definition.
+when Fluid Styled Content is used as content rendering definition.
.. index:: Frontend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79622-NewDefaultLayoutForFluidStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-NewDefaultLayoutForFluidStyledContent.rst
similarity index 94%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79622-NewDefaultLayoutForFluidStyledContent.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-NewDefaultLayoutForFluidStyledContent.rst
index ca8f4e9e1c97..5ca00b9440cb 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79622-NewDefaultLayoutForFluidStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-NewDefaultLayoutForFluidStyledContent.rst
@@ -9,10 +9,10 @@ See :issue:`79622`
Description
===========
-Previously there have been three layouts you could choose from when you are
-defining your own custom content elements or override an existing template.
+Previously there have been three layouts you could choose from when you were
+defining your own custom content elements or overriding an existing template.
-To provide a better maintainability and ease the overrides we are reducing
+To provide a better maintainability and ease of use of overrides we are reducing
these to a single layout that is named `Default` with all sections optional
and fallbacks if the section is not set. Also we are introducing the "DropIn"
concept.
@@ -88,9 +88,9 @@ exact ordering.
DropIn
------
-The sections `Before` and `After` are so called `DropIn` sections. DropIns
+The sections `Before` and `After` are so called "DropIn" sections. DropIns
have been introduced to be able to place additional functionality to all
-content elements without overriding layouts or the templates. DropIn´s are
+content elements without overriding layouts or templates. DropIns are
basically placeholders/empty partials that are meant to be overridden if necessary.
DropIn Locations:
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79622-SpaceBeforeAndSpaceAfterClassForCssStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForCssStyledContent.rst
similarity index 75%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79622-SpaceBeforeAndSpaceAfterClassForCssStyledContent.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForCssStyledContent.rst
index c4dd1daab8c6..290abd772a03 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79622-SpaceBeforeAndSpaceAfterClassForCssStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForCssStyledContent.rst
@@ -9,22 +9,22 @@ See :issue:`79622`
Description
===========
-CSS Styled Content provided the editor the possibility to fine-tune distances
-between content elements. The concept of CSC relied on that the editor
-understood what `margins` are, how they are calculated and had to maintain
-an overview of pixels that where used on the site he is maintaining.
-
-This lead to different problems not only for the editor but also for the
-integrator because he has no control about what the editor fills into these
-fields. Also it was hardly controlable when these distances should be
+CSS Styled Content provided the possibility to the editor to fine-tune distances
+between content elements. The concept of CSC relied on the editor
+understanding what `margins` are, how they are calculated and had to maintain
+an overview of pixels that were used on the site he/she is maintaining.
+
+This led to different problems not only for the editor but also for the
+integrator because he had no control about what the editor fills into these
+fields. Also it was hardly controllable when these distances should be
variable and change on certain viewports for mobile usage.
-To regain control for this behaviour we are now introducing a new concept
+To regain control over this behaviour we are now introducing a new concept
that purely relies on CSS classes, that can be defined by the integrator.
-All CSS classes are by default prefixed by `frame-space-before-` or
-`frame-spacer-after-` and added to the surrounding frame when available.
-If the frame if the content element is set to none, placeholder elements
+All CSS classes are prefixed with `frame-space-before-` or
+`frame-spacer-after-` by default and added to the surrounding frame when available.
+If the frame of the content element is set to none, placeholder elements
are placed before and after to generate that distance.
The default CSS definitions are placed in the optional static template
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79622-SpaceBeforeAndSpaceAfterClassForFluidStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForFluidStyledContent.rst
similarity index 75%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79622-SpaceBeforeAndSpaceAfterClassForFluidStyledContent.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForFluidStyledContent.rst
index a00e57c9779b..b0ad19959f7e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79622-SpaceBeforeAndSpaceAfterClassForFluidStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForFluidStyledContent.rst
@@ -9,22 +9,22 @@ See :issue:`79622`
Description
===========
-CSS Styled Content provided the editor the possibility to fine-tune distances
-between content elements. The concept of CSC relied on that the editor
-understood what `margins` are, how they are calculated and had to maintain
-an overview of pixels that where used on the site he is maintaining.
-
-This lead to different problems not only for the editor but also for the
-integrator because he has no control about what the editor fills into these
-fields. Also it was hardly controlable when these distances should be
+CSS Styled Content provided the possibility to the editor to fine-tune distances
+between content elements. The concept of CSC relied on the editor
+understanding what `margins` are, how they are calculated and had to maintain
+an overview of pixels that were used on the site he/she is maintaining.
+
+This led to different problems not only for the editor but also for the
+integrator because he had no control about what the editor fills into these
+fields. Also it was hardly controllable when these distances should be
variable and change on certain viewports for mobile usage.
-To regain control for this behaviour we are now introducing a new concept
+To regain control over this behaviour we are now introducing a new concept
that purely relies on CSS classes, that can be defined by the integrator.
-All CSS classes are by default prefixed by `frame-space-before-` or
-`frame-spacer-after-` and added to the surrounding frame when available.
-If the frame if the content element is set to none, placeholder elements
+All CSS classes are prefixed with `frame-space-before-` or
+`frame-spacer-after-` by default and added to the surrounding frame when available.
+If the frame of the content element is set to none, placeholder elements
are placed before and after to generate that distance.
The default CSS definitions are placed in the optional static template
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79622-TextmediaSupportForCSSStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-TextmediaSupportForCSSStyledContent.rst
similarity index 86%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79622-TextmediaSupportForCSSStyledContent.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-TextmediaSupportForCSSStyledContent.rst
index c2238c0a28c3..2ccd7aa1618e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79622-TextmediaSupportForCSSStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-TextmediaSupportForCSSStyledContent.rst
@@ -9,9 +9,9 @@ See :issue:`79622`
Description
===========
-CSS Styled content now comes with support for the content element "Text and Media"
+CSS Styled Content now comes with support for the content element "Text and Media"
that was previously exclusive to Fluid Styled Content, to make the transition from
-CSS Styled Content to Fluid Styled content more easy.
+CSS Styled Content to Fluid Styled content easier.
The "Text and Media" implementation uses the fluid rendering for the Gallery from
the Fluid Styled Content implementation and also the ClickEnlarge ViewHelper.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79626-IntegrateRecordLinkHandler.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79626-IntegrateRecordLinkHandler.rst
similarity index 76%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-79626-IntegrateRecordLinkHandler.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Feature-79626-IntegrateRecordLinkHandler.rst
index 851008dceb18..216390cf0583 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79626-IntegrateRecordLinkHandler.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79626-IntegrateRecordLinkHandler.rst
@@ -9,11 +9,11 @@ See :issue:`79626`
Description
===========
-The functionality of the extension `linkhandler` has been integrated into the core. It enables editors to link to single records.
+The functionality of EXT:linkhandler has been integrated into the core. It enables editors to link to single records.
The configuration consists of the following parts:
-*PageTsConfig* is used to create a new tab in the LinkBrowser to be able to select records:
+**PageTsConfig** is used to create a new tab in the LinkBrowser to be able to select records:
.. code-block:: typoscript
@@ -32,8 +32,10 @@ The following optional configuration is available:
- :typoscript:`configuration.storagePid = 1`: Let the link browser start with the given page
- :typoscript:`configuration.pageTreeMountPoints = 123,456`: Mount the given pages instead of the regular page tree
+You can position your own handlers in order as defined in https://docs.typo3.org/typo3cms/extensions/core/Changelog/7.6/Feature-66369-AddedLinkBrowserAPIs.html
-*TypoScript* is used to generate the actual link in the frontend
+
+**TypoScript** is used to generate the actual link in the frontend
.. code-block:: typoscript
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Important-75400-NewDataHandlerCommandCopyToLanguage.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Important-75400-NewDataHandlerCommandCopyToLanguage.rst
new file mode 100644
index 000000000000..848c761aaff3
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Important-75400-NewDataHandlerCommandCopyToLanguage.rst
@@ -0,0 +1,21 @@
+.. include:: ../../Includes.txt
+
+============================================================
+Important: #75400 - New DataHandler command 'copyToLanguage'
+============================================================
+
+See :issue:`75400`
+
+Description
+===========
+
+A new DataHandler command `copyToLanguage` has been introduced. It behaves like `localize` command
+(both record and child records are copied to a given language), but does not set `transOrigPointerField` fields (e.g. l10n_parent).
+
+The `copyToLanguage` command should be used when localizing records in "Free Mode". This command is used when localizing
+content elements using the translation wizard's "Copy" strategy.
+
+The `localize` DataHandler command should be used when translating records in "Connected Mode" (strict translation of records from the default language).
+This command is used when selecting "Translate" strategy in content elements translation wizard.
+
+.. index:: PHP-API
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-78899-DisplayCondStrictParsing.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Important-78899-DisplayCondStrictParsing.rst
similarity index 70%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-78899-DisplayCondStrictParsing.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Important-78899-DisplayCondStrictParsing.rst
index 200e3d28588c..43b907379655 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-78899-DisplayCondStrictParsing.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Important-78899-DisplayCondStrictParsing.rst
@@ -10,7 +10,7 @@ Description
===========
The parser handling :code:`displayCond` in :code:`TCA` fields is now strict and throws exceptions if the
-documented condition syntax is not followed and if referenced fields are not found. This should help
-debugging faulty conditions definitions a lot.
+documented condition syntax is not valid or if referenced fields are not found. This should help
+debugging faulty conditions a lot.
.. index:: Backend, FlexForm, TCA
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-79005-ConnectPersistentToRedisFromCacheBackend.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Important-79005-ConnectPersistentToRedisFromCacheBackend.rst
similarity index 72%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-79005-ConnectPersistentToRedisFromCacheBackend.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Important-79005-ConnectPersistentToRedisFromCacheBackend.rst
index 0adbc92958b5..24dda47945de 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-79005-ConnectPersistentToRedisFromCacheBackend.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Important-79005-ConnectPersistentToRedisFromCacheBackend.rst
@@ -9,9 +9,9 @@ See :issue:`79005`
Description
===========
-phpredis has support for persistent connections, but currently the Redis cache backend has hard-coded
-the regular connect call. For unknown reasons - possibly a simple oversight - this is the only
-connection setting missing from the Redis cache backend is now implemented.
+phpredis has support for persistent connections, but until now the Redis cache backend had
+the regular connect call hard-coded. For unknown reasons this is the only
+connection setting missing from the Redis cache backend but has now been implemented.
The configuration setting is named ``persistentConnection``. It is an optional boolean option.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-79119-RemovedPageRepository-versioningPreview_where_hid_delProperty.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Important-79119-RemovedPageRepository-versioningPreview_where_hid_delProperty.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-79119-RemovedPageRepository-versioningPreview_where_hid_delProperty.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Important-79119-RemovedPageRepository-versioningPreview_where_hid_delProperty.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-79221-UseGlobalsDollarInsteadOfTYPO3jQuery.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Important-79221-UseGlobalsDollarInsteadOfTYPO3jQuery.rst
similarity index 81%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-79221-UseGlobalsDollarInsteadOfTYPO3jQuery.rst
rename to typo3/sysext/core/Documentation/Changelog/8.6/Important-79221-UseGlobalsDollarInsteadOfTYPO3jQuery.rst
index 2298999430f2..8ab2d7ba8a3a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-79221-UseGlobalsDollarInsteadOfTYPO3jQuery.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Important-79221-UseGlobalsDollarInsteadOfTYPO3jQuery.rst
@@ -13,7 +13,7 @@ The TYPO3 Core uses jQuery in the TYPO3 Backend with a default namespace of `TYP
namespace, and is now also available as global `$` when no other namespace is given. This was not possible before due to conflicts with
prototype.js.
-If using the shipped jQuery code in the Frontend explictly via ts:`page.javascriptLibs.jQuery.noConflict.namespace = default` then the
+If using the shipped jQuery code in the Frontend explicitly via ts:`page.javascriptLibs.jQuery.noConflict.namespace = default` then the
global `$` is also available in frontend scripts.
.. index:: JavaScript, TypoScript
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Index.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Index.rst
new file mode 100644
index 000000000000..703edbffa603
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Index.rst
@@ -0,0 +1,51 @@
+
+.. include:: ../../Includes.txt
+
+8.6 Changes
+===========
+
+**Table of contents**
+
+.. contents::
+ :local:
+ :depth: 1
+
+Breaking Changes
+^^^^^^^^^^^^^^^^
+
+.. toctree::
+ :maxdepth: 1
+ :titlesonly:
+ :glob:
+
+ Breaking-*
+
+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/Breaking-79464-ExtFormRefactorFluidRendering.rst b/typo3/sysext/core/Documentation/Changelog/master/Breaking-79464-ExtFormRefactorFluidRendering.rst
deleted file mode 100644
index 4ea2750ed5a0..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-79464-ExtFormRefactorFluidRendering.rst
+++ /dev/null
@@ -1,133 +0,0 @@
-.. include:: ../../Includes.txt
-
-======================================================
-Breaking: #51442 - EXT:form - Refactor fluid rendering
-======================================================
-
-See :issue:`79464`
-
-Description
-===========
-
-EXT:form uses "fluid" as the default rendering strategy.
-Therefore, EXT:form has to work close with the concepts of fluid to avoid current and future problems.
-Until now, EXT:form tried to reuse a fluid view instance by reconfiguring the instance on each nesting level, but fluid is not intended for such a purpose.
-This change reduces the complexity of the rendering process and works closer with the concepts of fluid.
-
-Impact
-======
-
-The configuration options 'renderingOptions.templateRootPaths', 'renderingOptions.partialRootPaths' and 'renderingOptions.layoutRootPaths' for form elements are
-from now on only rules for the root form element ('Form') and will be applied for all child form elements.
-If you configure 'renderingOptions.templateRootPaths' etc. for other form elements it will have no effect.
-
-The configuration option 'renderingOptions.templatePathAndFilename' for form elements was removed from the configuration and will have no effect.
-To define a template file name which should be used instead of a filename which is named like the form element type, there is a new option 'renderingOptions.templateName'.
-
-The internal setting 'renderingOptions.renderableNameInTemplate' for form elements was removed from the configuration and will have no effect.
-
-The setting 'rendererClassName' for form elements are from now on only rules for the root form element ('Form').
-If you define this option for other form elements, an 'invalid configuration' exception will be thrown.
-
-The configuration for the backend editor inline templates which are used by editor javascript has changed.
-The configuration path 'prototypes.<prototypeName>.formEditor.formEditorTemplates' was renamed and has no longer any effect.
-The fluid configuration part moved from 'prototypes.<prototypeName>.formEditor.formEditorTemplates' to a new section 'prototypes.<prototypeName>.formEditor.formEditorFluidConfiguration'.
-The backend editor inline template mapping moved to a new section 'prototypes.<prototypeName>.formEditor.formEditorPartials'.
-The inline template mapping for stage templates was condensed. If you define custom form editor stage templates which use a default stage template it could
-result in a javascript error within the form editor.
-
-The template files moved from 'Resources/Private/Frontend/Templates/FormElements/' to 'Resources/Private/Frontend/Partials'.
-The template structure has changed. Without adaptation of your overridden templates, no form elements are visible within the frontend.
-
-
-Affected Installations
-======================
-
-All installations since TYPO3 8.5 which use the new EXT:form extension and create or extend custom form elements through configuration and / or
-override EXT:form template files.
-
-Migration
-=========
-
-If you override/ extend
-
- 'TYPO3.CMS.Form.mixins.formElementMixins.BaseFormElementMixin.renderingOptions.templateRootPaths'
- 'TYPO3.CMS.Form.mixins.formElementMixins.BaseFormElementMixin.renderingOptions.partialRootPaths'
- 'TYPO3.CMS.Form.mixins.formElementMixins.BaseFormElementMixin.renderingOptions.layoutRootPaths'
-
-move it to
-
- 'TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.templateRootPaths'
- 'TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.partialRootPaths'
- 'TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.layoutRootPaths'
-
-
-If you override/ extend
-
- 'TYPO3.CMS.Form.mixins.formElementMixins.BaseFormElementMixin.renderingOptions.skipUnknownElements'
-
-move it to
-
- 'TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.skipUnknownElements'
-
-
-If you defined
-
- 'TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.<formElementType>.rendererClassName'
-
-for a <formElementType> which is *NOT* 'Form', you have to remove this setting.
-
-
-If you defined
-
- 'TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.renderableNameInTemplate'
-
-you have to use
-
- 'TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.templateName'
-
-'templateName' is the partial path, relative to 'TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.partialRootPaths'
-
-
-If you defined custom form editor templates within
-
- 'TYPO3.CMS.Form.prototypes.<prototypeName>.formEditor.formEditorTemplates'
-
-you have to move this to
-
- 'TYPO3.CMS.Form.prototypes.<prototypeName>.formEditor.formEditorPartials'
-
-
-If you defined a custom form editor stage template which depends on a default form editor stage template you have to redefine it:
-
- Stage/Text => Stage/SimpleTemplate
- Stage/Password => Stage/SimpleTemplate
- Stage/AdvancedPassword => Stage/SimpleTemplate
- Stage/Textarea => Stage/SimpleTemplate
- Stage/Checkbox => Stage/SimpleTemplate
- Stage/MultiCheckbox => Stage/SelectTemplate
- Stage/MultiSelect => Stage/SelectTemplate
- Stage/RadioButton => Stage/SelectTemplate
- Stage/SingleSelect => Stage/SelectTemplate
- Stage/DatePicker => Stage/SimpleTemplate
- Stage/Hidden => Stage/SimpleTemplate
- Stage/FileUpload => Stage/FileUploadTemplate
- Stage/ImageUpload => Stage/FileUploadTemplate
-
-
-All form element templates except the template for the 'Form' element moved from templates to partials.
-You have to move this too, if you extended the fluid search paths.
-The 'Form' element is a template and will be found through 'TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.templateRootPaths'.
-All other form elements are partials and will be found through 'TYPO3.CMS.Form.prototypes.<prototypeName>.formElementsDefinition.Form.renderingOptions.partialRootPaths'.
-
-
-The template/ partial structure has changed. You have to adapt this to your custom templates.
-Please look at the files within EXT:form/Resources/Private/Frontend/Partials
-to see what has happened.
-The main change is that you have to wrap the markup with
-
- <formvh:renderRenderable renderable="{element}">
- some form element
- </formvh:renderRenderable>
-
-.. index:: Backend, Frontend, ext:form
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-69572-PageModuleNoticeContentIsAlsoShownOn.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-69572-PageModuleNoticeContentIsAlsoShownOn.rst
deleted file mode 100644
index 17a1b6c5460c..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-69572-PageModuleNoticeContentIsAlsoShownOn.rst
+++ /dev/null
@@ -1,23 +0,0 @@
-.. include:: ../../Includes.txt
-
-================================================================
-Feature: #69572 - Page module Notice "Content is also shown on:"
-================================================================
-
-See :issue:`69572`
-
-Description
-===========
-
-When page content is inherited from different page via "Show content from page" there is a notice displayed on the page.
-
-This feature does the opposite and displays a notice on pages that are inherited elsewhere:
-"This content is also shown on:"
-
-
-Impact
-======
-
-On pages that are inherited elsewhere you see a notice with links to the pages where the content is inherited.
-
-.. index:: Backend
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-79140-AddHookToAddCustomTypoScriptTemplates.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-79140-AddHookToAddCustomTypoScriptTemplates.rst
deleted file mode 100644
index 414b8ba705a3..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-79140-AddHookToAddCustomTypoScriptTemplates.rst
+++ /dev/null
@@ -1,65 +0,0 @@
-.. include:: ../../Includes.txt
-
-=============================================================
-Feature: #79140 - Add hook to add custom TypoScript templates
-=============================================================
-
-See :issue:`79140`
-
-Description
-===========
-
-A new hook in TemplateService allows to add or modify existing TypoScript templates.
-
-Register the hook via :php:`$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['Core/TypoScript/TemplateService']['runThroughTemplatesPostProcessing']`
-in the extensions' ext_localconf.php file.
-
-Example
-=======
-
-An example implementation could look like this:
-
-EXT:my_site/ext_localconf.php
-
-.. code-block:: php
-
-$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['Core/TypoScript/TemplateService']['runThroughTemplatesPostProcessing'][1313131313] =
- \MyVendor\MySite\Hooks\TypoScriptHook::class . '->addCustomTypoScriptTemplate';
-
-
-EXT:my_site/Classes/Hooks/TypoScriptHook.php
-
-.. code-block:: php
-
-namespace MyVendor\MySite\Hooks;
-
-class TypoScriptHook
-{
-
- /**
- * Hooks into TemplateService after
- * @param array $parameters
- * @param \TYPO3\CMS\Core\TypoScript\TemplateService $parentObject
- * @return void
- */
- public function addCustomTypoScriptTemplate($parameters, $parentObject)
- {
- // Disable the inclusion of default TypoScript set via TYPO3_CONF_VARS
- $parameters['isDefaultTypoScriptAdded'] = true;
- // Disable the inclusion of ext_typoscript_setup.txt of all extensions
- $parameters['processExtensionStatics'] = false;
-
- // No template was found in rootline so far, so a custom "fake" sys_template record is added
- if ($parentObject->outermostRootlineIndexWithTemplate === 0) {
- $row = [
- 'uid' => 'my_site_template',
- 'config' => '<INCLUDE_TYPOSCRIPT: source="FILE:EXT:my_site/Configuration/TypoScript/site_setup.t3s">',
- 'root' => 1,
- 'pid' => 0
- ];
- $parentObject->processTemplate($row, 'sys_' . $row['uid'], 0, 'sys_' . $row['uid']);
- }
- }
-}
-
-.. index:: PHP-API, TypoScript
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-75400-NewDataHandlerCommandCopyToLanguage.rst b/typo3/sysext/core/Documentation/Changelog/master/Important-75400-NewDataHandlerCommandCopyToLanguage.rst
deleted file mode 100644
index f7cdaf2e87bb..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-75400-NewDataHandlerCommandCopyToLanguage.rst
+++ /dev/null
@@ -1,21 +0,0 @@
-.. include:: ../../Includes.txt
-
-============================================================
-Important: #75400 - New DataHandler command 'copyToLanguage'
-============================================================
-
-See :issue:`75400`
-
-Description
-===========
-
-A new DataHandler command 'copyToLanguage' has been introduced. It behaves like 'localize' command
-(both record and child records are copied to given language), but does not set transOrigPointerField fields (e.g. l10n_parent).
-
-The 'copyToLanguage' command should be used when localizing records in the "Free Mode". This command is used when localizing
-content elements using translation wizard's "Copy" strategy.
-
-The 'localize' DataHandler command should be used when translating records in "Connected Mode" (strict translation of records from the default language).
-This command is used when selecting "Translate" strategy in content elements translation wizard.
-
-.. index:: PHP-API
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Index.rst b/typo3/sysext/core/Documentation/Index.rst
index 9d8de0988453..60426be8662e 100644
--- a/typo3/sysext/core/Documentation/Index.rst
+++ b/typo3/sysext/core/Documentation/Index.rst
@@ -13,6 +13,7 @@ Every change to the TYPO3 Core which might affect your site is documented here.
:hidden:
Changelog/master/Index
+ Changelog/8.6/Index
Changelog/8.5/Index
Changelog/8.4/Index
Changelog/8.3/Index
--
GitLab