diff --git a/typo3/sysext/core/Documentation/Changelog/8.0/Breaking-73445-RemoveFlashmessage_compatibilityjsFromCore.rst b/typo3/sysext/core/Documentation/Changelog/8.0/Breaking-73445-RemoveFlashmessage_compatibilityjsFromCore.rst
index 818eb09acca2567e434681132adf12e19f7593a2..b72dd948b1fd70fc9f8fc440390d3f176af753a0 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.0/Breaking-73445-RemoveFlashmessage_compatibilityjsFromCore.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.0/Breaking-73445-RemoveFlashmessage_compatibilityjsFromCore.rst
@@ -16,12 +16,12 @@ The `flashmessage_compatibility.js` has been removed from the core.
Impact
======
-Extensions which make use of :js:`TYPO3.Flashmessage` JavaScript function will not work anymore.
+Extensions which make use of :javascript:`TYPO3.Flashmessage` JavaScript function will not work anymore.
Migration
=========
-Use :js:`top.TYPO3.Notification.*` to create flash messages within JavaScript for the TYPO3 backend.
+Use :javascript:`top.TYPO3.Notification.*` to create flash messages within JavaScript for the TYPO3 backend.
.. index:: JavaScript
diff --git a/typo3/sysext/core/Documentation/Changelog/8.0/Deprecation-73442-ModalGetSeverityClassHasBeenMovedToTheSeverityModule.rst b/typo3/sysext/core/Documentation/Changelog/8.0/Deprecation-73442-ModalGetSeverityClassHasBeenMovedToTheSeverityModule.rst
index 00d4c61a0f236217a1cbdbddd1b1630949fc7488..ed7d6f8c67007510ef5f6a1a29b261da2e873ca2 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.0/Deprecation-73442-ModalGetSeverityClassHasBeenMovedToTheSeverityModule.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.0/Deprecation-73442-ModalGetSeverityClassHasBeenMovedToTheSeverityModule.rst
@@ -10,24 +10,24 @@ See :issue:`73442`
Description
===========
-The method :js:`Modal.getSeverityClass` has been moved to :js:`Severity.getCssClass`. :js:`Modal.getSeverityClass` has been marked as deprecated.
+The method :javascript:`Modal.getSeverityClass` has been moved to :javascript:`Severity.getCssClass`. :javascript:`Modal.getSeverityClass` has been marked as deprecated.
Impact
======
-Calling :js:`Modal.getSeverityClass` will trigger a console warning in the browser.
+Calling :javascript:`Modal.getSeverityClass` will trigger a console warning in the browser.
Affected Installations
======================
-All 3rd party extensions using :js:`Modal.getSeverityClass` are affected.
+All 3rd party extensions using :javascript:`Modal.getSeverityClass` are affected.
Migration
=========
-Change the calls to :js:`Severity.getCssClass(severity)`.
+Change the calls to :javascript:`Severity.getCssClass(severity)`.
.. index:: JavaScript, Backend
diff --git a/typo3/sysext/core/Documentation/Changelog/8.0/Feature-73429-WizardComponentHasBeenAdded.rst b/typo3/sysext/core/Documentation/Changelog/8.0/Feature-73429-WizardComponentHasBeenAdded.rst
index 5e3e10e3f5719a3b6a5e0e2570252d35b5b96619..c70988f55ec91cc0c3f9735af3bc2a4b1aea559e 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.0/Feature-73429-WizardComponentHasBeenAdded.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.0/Feature-73429-WizardComponentHasBeenAdded.rst
@@ -20,14 +20,23 @@ Impact
======
The wizard component has the following public methods:
-#. :code:`addSlide(identifier, title, content, severity, callback)`
-#. :code:`addFinalProcessingSlide(callback)`
-#. :code:`set(key, value)`
-#. :code:`show()`
-#. :code:`dismiss()`
-#. :code:`getComponent()`
-#. :code:`lockNextStep()`
-#. :code:`unlockNextStep()`
+
+* :code:`addSlide(identifier, title, content, severity, callback)`
+
+* :code:`addFinalProcessingSlide(callback)`
+
+* :code:`set(key, value)`
+
+* :code:`show()`
+
+* :code:`dismiss()`
+
+* :code:`getComponent()`
+
+* :code:`lockNextStep()`
+
+* :code:`unlockNextStep()`
+
addSlide
~~~~~~~~
@@ -43,15 +52,15 @@ content string Yes The content of the slide
severity int Represents the severity of a slide. Please see TYPO3.Severity. Default is :code:`TYPO3.Severity.info`.
callback function Callback method run after the slide appeared. The callback receives two parameters:
:code:`$slide`: The current slide as a jQuery object
- :code:`settings`: The settings defined via :js:`Wizard.set()`
+ :code:`settings`: The settings defined via :javascript:`Wizard.set()`
========== =============== ============ ======================================================================================================
addFinalProcessingSlide
~~~~~~~~~~~~~~~~~~~~~~~
Adds a slide to the wizard containing a spinner. This should always be the latest slide. This method returns a Promise
-object due to internal handling. This means you have to add a :js:`done()` callback containing :js:`Wizard.show()` and ,
-:js:`Wizard.getComponent()` please see the example below.
+object due to internal handling. This means you have to add a :javascript:`done()` callback containing :javascript:`Wizard.show()` and
+:javascript:`Wizard.getComponent()` please see the example below.
========== =============== ============ ======================================================================================================
Name DataType Mandatory Description
@@ -62,7 +71,7 @@ callback function Callback method run after the slide appe
Example code:
-.. code-block:: js
+.. code-block:: javascript
Wizard.addFinalProcessingSlide().done(function() {
Wizard.show();
@@ -92,7 +101,7 @@ The event `wizard-visible` is fired when the wizard rendering has finished.
Example code:
-.. code-block:: js
+.. code-block:: javascript
Wizard.getComponent().on('wizard-visible', function() {
Wizard.unlockNextButton();
@@ -103,16 +112,16 @@ Wizards can be closed by firing the `wizard-dismiss` event.
Example code:
-.. code-block:: js
+.. code-block:: javascript
Wizard.getComponent().trigger('wizard-dismiss');
-Wizards fire the `wizard-dismissed` event if the wizard is closed. You can integrate your own listener by using :js:`Wizard.getComponent()`.
+Wizards fire the `wizard-dismissed` event if the wizard is closed. You can integrate your own listener by using :javascript:`Wizard.getComponent()`.
Example code:
-.. code-block:: js
+.. code-block:: javascript
Wizard.getComponent().on('wizard-dismissed', function() {
// Calculate the answer of life the universe and everything
diff --git a/typo3/sysext/core/Documentation/Changelog/8.1/Feature-75386-GetIdentifierInSlideCallback.rst b/typo3/sysext/core/Documentation/Changelog/8.1/Feature-75386-GetIdentifierInSlideCallback.rst
index 954a1c8d029650867d2c78f99afd76b19c5c605e..e140f8d890ee8f3ad33f40420caa61aac2c1361b 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.1/Feature-75386-GetIdentifierInSlideCallback.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.1/Feature-75386-GetIdentifierInSlideCallback.rst
@@ -10,13 +10,13 @@ See :issue:`75386`
Description
===========
-The callback of :js:`Wizard.addSlide()` now has a new parameter `identifier`.
+The callback of :javascript:`Wizard.addSlide()` now has a new parameter `identifier`.
Impact
======
-The identifier is passed to the callback function of :js:`Wizard.addSlide()`.
+The identifier is passed to the callback function of :javascript:`Wizard.addSlide()`.
Example code:
diff --git a/typo3/sysext/core/Documentation/Changelog/8.2/Breaking-76285-PopupConfigurationIsMovedToTYPO3settings.rst b/typo3/sysext/core/Documentation/Changelog/8.2/Breaking-76285-PopupConfigurationIsMovedToTYPO3settings.rst
index 75117b6b47fa72ea6ae538e2e0d9fdeb21edcb07..d8d05b77d6bcce9ea5488eb3d4be449548bc67d4 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.2/Breaking-76285-PopupConfigurationIsMovedToTYPO3settings.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.2/Breaking-76285-PopupConfigurationIsMovedToTYPO3settings.rst
@@ -14,10 +14,10 @@ The popup window configuration has been moved to `TYPO3.settings`.
The following configuration options are not working anymore.
-:js:`top.TYPO3.configuration.RTEPopupWindow.width`
-:js:`top.TYPO3.configuration.RTEPopupWindow.height`
-:js:`top.TYPO3.configuration.PopupWindow.width`
-:js:`top.TYPO3.configuration.PopupWindow.height`
+:javascript:`top.TYPO3.configuration.RTEPopupWindow.width`
+:javascript:`top.TYPO3.configuration.RTEPopupWindow.height`
+:javascript:`top.TYPO3.configuration.PopupWindow.width`
+:javascript:`top.TYPO3.configuration.PopupWindow.height`
Impact
@@ -37,12 +37,12 @@ Migration
The migration can be done with the following replacements.
-:js:`top.TYPO3.configuration.RTEPopupWindow.width` to :js:`TYPO3.settings.Textarea.RTEPopupWindow.width`
+:javascript:`top.TYPO3.configuration.RTEPopupWindow.width` to :javascript:`TYPO3.settings.Textarea.RTEPopupWindow.width`
-:js:`top.TYPO3.configuration.RTEPopupWindow.height` to :js:`TYPO3.settings.Textarea.RTEPopupWindow.height`
+:javascript:`top.TYPO3.configuration.RTEPopupWindow.height` to :javascript:`TYPO3.settings.Textarea.RTEPopupWindow.height`
-:js:`top.TYPO3.configuration.PopupWindow.width` to :js:`TYPO3.settings.Popup.PopupWindow.width`
+:javascript:`top.TYPO3.configuration.PopupWindow.width` to :javascript:`TYPO3.settings.Popup.PopupWindow.width`
-:js:`top.TYPO3.configuration.PopupWindow.height` to :js:`TYPO3.settings.Popup.PopupWindow.height`
+:javascript:`top.TYPO3.configuration.PopupWindow.height` to :javascript:`TYPO3.settings.Popup.PopupWindow.height`
.. index:: JavaScript, Backend
diff --git a/typo3/sysext/core/Documentation/Changelog/8.2/Feature-76590-IntroduceUnitTestsForJavaScript.rst b/typo3/sysext/core/Documentation/Changelog/8.2/Feature-76590-IntroduceUnitTestsForJavaScript.rst
index 4fe50da533380a04dc2d0145819b109851e1b1d2..90c442289747a2160950b42eaa0516f186836155 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.2/Feature-76590-IntroduceUnitTestsForJavaScript.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.2/Feature-76590-IntroduceUnitTestsForJavaScript.rst
@@ -43,7 +43,7 @@ Test-Files
Any test file must be located in extension folder `typo3/sysext/<EXTKEY>/Tests/JavaScript/`
The filename must end with Test.js, e.g. `GridEditorTest.js`
-Each test file must be implemented as AMD module, must use strict mode and has to use :js:`describe` with module name as outer wrap for each test.
+Each test file must be implemented as AMD module, must use strict mode and has to use :javascript:`describe` with module name as outer wrap for each test.
The following code block shows a good example:
.. code-block:: javascript
@@ -68,7 +68,7 @@ Please take a look at the existing test files and read the jasmine documentation
DataProvider for tests
----------------------
-For testing a set of values, the core implement a kind of DataProvider. To use the DataProvider you have to use the function :js:`using`.
+For testing a set of values, the core implement a kind of DataProvider. To use the DataProvider you have to use the function :javascript:`using`.
Please take a look at `FormEngineValidationTest.js` for an example.
.. index:: JavaScript
diff --git a/typo3/sysext/core/Documentation/Changelog/8.3/Breaking-76108-ReplaceExtJSCategoryTreeWithD3AndSVG.rst b/typo3/sysext/core/Documentation/Changelog/8.3/Breaking-76108-ReplaceExtJSCategoryTreeWithD3AndSVG.rst
index 11001b757294929d459251dcce5669369184977a..4a2ae34a9183888c883dcfbf588ffcbed467f5f3 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.3/Breaking-76108-ReplaceExtJSCategoryTreeWithD3AndSVG.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.3/Breaking-76108-ReplaceExtJSCategoryTreeWithD3AndSVG.rst
@@ -20,14 +20,14 @@ It also polluted backend user settings with tons of data without giving much usa
Impact
======
-Any JS code referencing ExtJS component :js:`TYPO3.Components.Tree` or its sub-components
-(like :js:`TYPO3.Components.Tree.StandardTree`) will no longer work.
+Any JS code referencing ExtJS component :javascript:`TYPO3.Components.Tree` or its sub-components
+(like :javascript:`TYPO3.Components.Tree.StandardTree`) will no longer work.
Affected Installations
======================
-All installations having extensions which modify the :js:`TYPO3.Components.Tree`
+All installations having extensions which modify the :javascript:`TYPO3.Components.Tree`
(implemented in `typo3/sysext/backend/Resources/Public/JavaScript/tree.js`) component,
or rely on the file being present.
diff --git a/typo3/sysext/core/Documentation/Changelog/8.3/Breaking-77137-JavaScriptAPIOfRTEChanged.rst b/typo3/sysext/core/Documentation/Changelog/8.3/Breaking-77137-JavaScriptAPIOfRTEChanged.rst
index 26e460e633ce2bcd0cfcfb1b50df1044440b8135..4a86a3e2e3b437d9974d2ace6ce026495bf337aa 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.3/Breaking-77137-JavaScriptAPIOfRTEChanged.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.3/Breaking-77137-JavaScriptAPIOfRTEChanged.rst
@@ -49,6 +49,6 @@ buildButtonConfig
The method takes now two additional arguments: `active` and `severity`. The parameter `active` is a boolean
value and declares the button being either active or not. The parameter `severity` is an integer representing the
severity of the button. This should always represent the severity of the modal, use one of the severities defined in
- :js:`TYPO3/CMS/Backend/Severity`.
+ :javascript:`TYPO3/CMS/Backend/Severity`.
.. index:: JavaScript, RTE
diff --git a/typo3/sysext/core/Documentation/Changelog/8.3/Feature-76108-ReplaceExtJSCategoryTreeWithD3AndSVG.rst b/typo3/sysext/core/Documentation/Changelog/8.3/Feature-76108-ReplaceExtJSCategoryTreeWithD3AndSVG.rst
index c8cb9adce5f9466047fd829f06280b09513a1229..d30f95c7bf69744c18cadc9de376d0534293f793 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.3/Feature-76108-ReplaceExtJSCategoryTreeWithD3AndSVG.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.3/Feature-76108-ReplaceExtJSCategoryTreeWithD3AndSVG.rst
@@ -36,7 +36,7 @@ Data binding
------------
Thanks to D3, each SVG node representing tree item is bound to the data object. The general idea is that all operations (like showing/hiding/selecting...) are first performed on the dataset, and then the view (SVG) is refreshed.
-In the :js:`initialize` function SvgTree loads the whole tree as json
+In the :javascript:`initialize` function SvgTree loads the whole tree as json
Impact
diff --git a/typo3/sysext/core/Documentation/Changelog/8.4/Feature-77900-IntroduceTypeScriptForTheCore.rst b/typo3/sysext/core/Documentation/Changelog/8.4/Feature-77900-IntroduceTypeScriptForTheCore.rst
index 8d029d7886f4bd752e5caf20d3b72cc18a5c2ece..571a6e37df9e65b57d1e0bf7829a875ea82a9b0e 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.4/Feature-77900-IntroduceTypeScriptForTheCore.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.4/Feature-77900-IntroduceTypeScriptForTheCore.rst
@@ -37,7 +37,7 @@ An example:
will be compiled to:
-:js:`define(["require", "exports", "TYPO3/CMS/Core/Contrib/jquery.minicolors"], function (require, exports, minicolors) {`
+:javascript:`define(["require", "exports", "TYPO3/CMS/Core/Contrib/jquery.minicolors"], function (require, exports, minicolors) {`
A very simple example is the `EXT:backend/Resources/Private/TypeScript/ColorPicker.ts` file.
@@ -54,11 +54,11 @@ Additional Rules
For the core we have defined some additional rules which you should know, because not all of them can be checked by the Linter yet:
#. Always define types and return types, also if TypeScript provides a default type. [checked by Linter]
-#. Variable scoping: Prefer :js:`let` instead of :js:`var`. [checked by Linter]
+#. Variable scoping: Prefer :javascript:`let` instead of :javascript:`var`. [checked by Linter]
#. Optional properties in interfaces are possible but a bad style, this is not allowed for the core. [NOT checked by Linter]
#. An interface will never extend a class. [NOT checked by Linter]
-#. Iterables: Use :js:`for (i of list)` if possible instead of :ts:`for (i in list)` [NOT checked by Linter]
-#. The :js:`implements` keyword is required for any usage, also if TypeScript does not require it. [NOT checked by Linter]
+#. Iterables: Use :javascript:`for (i of list)` if possible instead of :ts:`for (i in list)` [NOT checked by Linter]
+#. The :javascript:`implements` keyword is required for any usage, also if TypeScript does not require it. [NOT checked by Linter]
#. Any class or interface must be declared with "export" to ensure re-use or export an instance of the object for existing code which can't be updated now. [NOT checked by Linter]
diff --git a/typo3/sysext/core/Documentation/Changelog/8.4/Index.rst b/typo3/sysext/core/Documentation/Changelog/8.4/Index.rst
index 9adfb134db0fdd7470e4d058bbff98125343a64c..fdb769086565526e091cf51ecf2d4ca929872859 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.4/Index.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.4/Index.rst
@@ -39,13 +39,3 @@ Deprecation
:glob:
Deprecation-*
-
-Important
-^^^^^^^^^
-
-.. toctree::
- :maxdepth: 1
- :titlesonly:
- :glob:
-
- Important-*
diff --git a/typo3/sysext/core/Documentation/Changelog/8.5/Breaking-78521-DropUnusedJavaScriptFromBackendjs.rst b/typo3/sysext/core/Documentation/Changelog/8.5/Breaking-78521-DropUnusedJavaScriptFromBackendjs.rst
index 0471cf6b5259a8ff10bb06763d70844268f7ad87..8a7192aed1808d9e012ac65cf4da561e5107055f 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.5/Breaking-78521-DropUnusedJavaScriptFromBackendjs.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.5/Breaking-78521-DropUnusedJavaScriptFromBackendjs.rst
@@ -12,10 +12,10 @@ Description
The following JavaScript methods related to ExtJS have been removed from the Backend main frame
as defined in the main `backend.js` file.
-:js:`TYPO3._instances`
-:js:`TYPO3.addInstance`
-:js:`TYPO3.getInstance`
-:js:`TYPO3.helpers.split`
+:javascript:`TYPO3._instances`
+:javascript:`TYPO3.addInstance`
+:javascript:`TYPO3.getInstance`
+:javascript:`TYPO3.helpers.split`
Impact
diff --git a/typo3/sysext/core/Documentation/Changelog/8.5/Breaking-78522-RemoveBackendUserOptionDebugInWindow.rst b/typo3/sysext/core/Documentation/Changelog/8.5/Breaking-78522-RemoveBackendUserOptionDebugInWindow.rst
index 6c9a7fdd78e467e42b5b3443798990c013b9ca6e..e3e9c53b8bb933396287536cf4d9c59aa1d4212f 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.5/Breaking-78522-RemoveBackendUserOptionDebugInWindow.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.5/Breaking-78522-RemoveBackendUserOptionDebugInWindow.rst
@@ -16,7 +16,7 @@ as the option of opening the debug information in a window was migrated already.
Impact
======
-The setting is not available anymore in JavaScript under :js:`TYPO3.configuration`.
+The setting is not available anymore in JavaScript under :javascript:`TYPO3.configuration`.
Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/8.5/Breaking-78525-RemoveUnusedConfigurationOptionsForJavaScript.rst b/typo3/sysext/core/Documentation/Changelog/8.5/Breaking-78525-RemoveUnusedConfigurationOptionsForJavaScript.rst
index 68f012a1aa75080b0c710487217cdd40ae65967b..9a4cfac7bd089871d8395f402cfe8a0b9797df20 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.5/Breaking-78525-RemoveUnusedConfigurationOptionsForJavaScript.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.5/Breaking-78525-RemoveUnusedConfigurationOptionsForJavaScript.rst
@@ -11,14 +11,14 @@ Description
Removed all options that are not used anymore from TYPO3.configuration in JavaScript context.
-:js:`TYPO3.configuration.moduleMenuWidth`
-:js:`TYPO3.configuration.topBarHeight`
+:javascript:`TYPO3.configuration.moduleMenuWidth`
+:javascript:`TYPO3.configuration.topBarHeight`
Impact
======
-Both settings are not available anymore in JavaScript under :js:`TYPO3.configuration`.
+Both settings are not available anymore in JavaScript under :javascript:`TYPO3.configuration`.
Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/8.5/Deprecation-78279-DeprecateTopTYPO3BackendContentContaineriframe.rst b/typo3/sysext/core/Documentation/Changelog/8.5/Deprecation-78279-DeprecateTopTYPO3BackendContentContaineriframe.rst
index ff68838539b1cee3716b224b85464ef4b165f220..c8191bd20c54791f1aea018d00bfa70eb99353b9 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.5/Deprecation-78279-DeprecateTopTYPO3BackendContentContaineriframe.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.5/Deprecation-78279-DeprecateTopTYPO3BackendContentContaineriframe.rst
@@ -9,7 +9,7 @@ See :issue:`78279`
Description
===========
-The property :js:`top.TYPO3.Backend.ContentContainer.iframe` has been marked as deprecated.
+The property :javascript:`top.TYPO3.Backend.ContentContainer.iframe` has been marked as deprecated.
Impact
@@ -21,12 +21,12 @@ Using this property will stop working in TYPO3 v9.
Affected Installations
======================
-All installations using :js:`top.TYPO3.Backend.ContentContainer.iframe`.
+All installations using :javascript:`top.TYPO3.Backend.ContentContainer.iframe`.
Migration
=========
-Use accessor method :js:`top.TYPO3.Backend.ContentContainer.get()` instead.
+Use accessor method :javascript:`top.TYPO3.Backend.ContentContainer.get()` instead.
.. index:: Backend
diff --git a/typo3/sysext/core/Documentation/Changelog/8.5/Important-17904-ShowAccessRestrictedPagesDoesNotWorkWithSpecialMenus.rst b/typo3/sysext/core/Documentation/Changelog/8.5/Important-17904-ShowAccessRestrictedPagesDoesNotWorkWithSpecialMenus.rst
index 537ffc049d9f6ab505f95c630dc0af5a2c23de8f..2211504ce06ba849bf1d1e2712c64a42fbae404a 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.5/Important-17904-ShowAccessRestrictedPagesDoesNotWorkWithSpecialMenus.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.5/Important-17904-ShowAccessRestrictedPagesDoesNotWorkWithSpecialMenus.rst
@@ -9,7 +9,8 @@ See :issue:`17904`
Description
===========
-HMENU setting `showAccessRestrictedPages`=NONE now acts as documented in https://docs.typo3.org/typo3cms/TyposcriptReference/MenuObjects/CommonProperties/Index.html.
+HMENU setting `showAccessRestrictedPages=NONE` now acts as documented in
+:ref:`TypoScript reference <t3tsref:menu-common-properties>`.
Before: using the option renders `<a>Page title</a>` when page is inaccessible.
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78192-RefactorClickMenuContextMenu.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78192-RefactorClickMenuContextMenu.rst
index cde7ecf6ceafb8dc82c9fe3e5918a46881ac674a..6ab2222cf263a2368307c2405a17e0ac61c240cd 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78192-RefactorClickMenuContextMenu.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-78192-RefactorClickMenuContextMenu.rst
@@ -27,8 +27,8 @@ Classes removed
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 have been removed.
+- The :javascript:`TYPO3.Components.PageTree.ContextMenu` component defined in contextmenu.js has been removed.
+- The `contextMenuProvider` property as well as `enableContextMenu` and `openContextMenu` methods of the :javascript:`TYPO3.Components.PageTree.Tree` component have been removed.
Migration
^^^^^^^^^
@@ -95,7 +95,7 @@ Changed markup (data attributes) for click menu
- 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`
+- the class which triggers the context-menu has changed from :javascript:`t3-js-clickmenutrigger` to :javascript:`t3js-contextmenutrigger`
Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79109-LowlevelVersionsCommandParametersChanged.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79109-LowlevelVersionsCommandParametersChanged.rst
index b4e248b3488beec49ca0d2cde90892f560f2654e..5edafa5d6bc7c47fd87528bc9f1b10d9d5e269d3 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79109-LowlevelVersionsCommandParametersChanged.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79109-LowlevelVersionsCommandParametersChanged.rst
@@ -15,24 +15,33 @@ has been migrated to a Symfony Console command.
The command previously available via `./typo3/cli_dispatch.phpsh lowlevel_cleaner versions` is now available
via `./typo3/sysext/core/bin/typo3 cleanup:versions` and allows the following CLI options to be set:
-The following options can be set
-`--action={nameofaction}` to clean up versioned records, one of the following actions are possible:
- "versions_in_live": Delete versioned records in the live workspace
- "published_versions": Delete versions of published records
- "invalid_workspace": Move records inside a non-existing workspace ID into the live workspace
- "unused_placeholders": Remove placeholders which are not used anymore from the database
-`-v` and `-vv` to show more detailed information on the records affected
-`--pid=23` or `-p=23` to only find versions with page ID 23 (otherwise "0" is taken)
-`--depth=4` or `-d=4` to only clean recursively until a certain page tree level.
-`--dry-run` to only show the records to be changed / deleted
+The following options can be set:
-The PHP class of the old CLI command `TYPO3\CMS\Lowlevel\VersionsCommand` has been removed.
+- :shell:`--action={nameofaction}` to clean up versioned records, one of the following actions are possible:
+
+ - "versions_in_live": Delete versioned records in the live workspace
+
+ - "published_versions": Delete versions of published records
+
+ - "invalid_workspace": Move records inside a non-existing workspace ID into the live workspace
+
+ - "unused_placeholders": Remove placeholders which are not used anymore from the database
+
+- :shell:`-v` and :shell:`-vv` to show more detailed information on the records affected
+
+- :shell:`--pid=23` or :shell:`-p=23` to only find versions with page ID 23 (otherwise "0" is taken)
+
+- :shell:`--depth=4` or :shell:`-d=4` to only clean recursively until a certain page tree level.
+
+- :shell:`--dry-run` to only show the records to be changed / deleted
+
+The PHP class of the old CLI command :php:`TYPO3\CMS\Lowlevel\VersionsCommand` has been removed.
Impact
======
-Calling the old CLI command `./typo3/cli_dispatch.phpsh lowlevel_cleaner versions` will result in an error message.
+Calling the old CLI command :shell:`./typo3/cli_dispatch.phpsh lowlevel_cleaner versions` will result in an error message.
Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-StreamliningStructureOfCSSStyledContentAndFluidStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-StreamliningStructureOfCSSStyledContentAndFluidStyledContent.rst
index 070e4353f3d8e0ca74c4d881310ff1f696c157a8..f68fd94199dd990886a623ae87783395f07140d1 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-StreamliningStructureOfCSSStyledContentAndFluidStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Breaking-79622-StreamliningStructureOfCSSStyledContentAndFluidStyledContent.rst
@@ -15,7 +15,7 @@ The file structures of CSS Styled Content and Fluid Styled Content have been str
File structure of CSS Styled Content
------------------------------------
-.. code-block::
+.. code-block:: php
- Configuration/TypoScript
| - ContentElement
@@ -57,7 +57,7 @@ File structure of CSS Styled Content
File structure of Fluid Styled Content
--------------------------------------
-.. code-block::
+.. code-block:: php
- Configuration/TypoScript
| - ContentElement
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79341-TCARichtextConfigurationInDefaultExtrasDropped.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79341-TCARichtextConfigurationInDefaultExtrasDropped.rst
index 1ee6ca16ce9af24082d59895129547d6a8d43278..1dc9207589cf040e41158671168f2adddebf88a2 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79341-TCARichtextConfigurationInDefaultExtrasDropped.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79341-TCARichtextConfigurationInDefaultExtrasDropped.rst
@@ -14,6 +14,7 @@ Enabling richtext rendering for fields in the Backend record editor has been sim
In the past, a typical :php:`TCA` configuration of a richtext field looked like:
.. code-block:: php
+
'columns' => [
'content' => [
'config' => [
@@ -26,6 +27,7 @@ In the past, a typical :php:`TCA` configuration of a richtext field looked like:
The :php:`defaultExtras` is obsolete and substituted with :php:`enableRichtext` within the :php:`config` section:
.. code-block:: php
+
'columns' => [
'content' => [
'config' => [
@@ -39,6 +41,7 @@ The :php:`defaultExtras` is obsolete and substituted with :php:`enableRichtext`
If the RTE was enabled for a specific type only, it looked like this:
.. code-block:: php
+
'columns' => [
'content' => [
'config' => [
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79440-TcaChanges.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79440-TcaChanges.rst
index dd17381a390ade77f89d1e987c6840e85cb03215..093d0f64f91dad45298419c8127e96858307efb0 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79440-TcaChanges.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Deprecation-79440-TcaChanges.rst
@@ -11,7 +11,7 @@ Description
The :code:`TCA` on field level has been changed. Nearly all column types are affected.
In general, the sub-section :code:`wizards` is gone and replaced by a combination of new
-:code:`renderType`s and a new set of configuration options. Wizards are now divided into
+:code:`renderType's` and a new set of configuration options. Wizards are now divided into
three different kinds:
* :code:`fieldInformation` - Informational HTML, typically displayed between the element label
@@ -714,6 +714,8 @@ Example after:
Disable other parts of type=group:
+.. code-block:: php
+
'group_db_1' => [
'label' => 'group_db_1',
'config' => [
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78192-RefactorClickMenuContextMenu.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78192-RefactorClickMenuContextMenu.rst
index 963f93e88df8721ed85828fe80c531648aec5525..f5ff97d36ebaab2f055b8d9e98bd48f3ac9314c0 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78192-RefactorClickMenuContextMenu.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-78192-RefactorClickMenuContextMenu.rst
@@ -80,17 +80,17 @@ 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 modules 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 :javascript:`TYPO3/CMS/Backend/ContextMenuActions` JS module or other modules defined in the `additionalAttributes['data-callback-module']`.
For example usage of this API see:
- - Beuser item provider :php:`\TYPO3\CMS\Beuser\ContextMenu\ItemProvider` and requireJS module :js:`TYPO3/CMS/Beuser/ContextMenuActions`
- - Impexp item provider :php:`\TYPO3\CMS\Impexp\ContextMenu\ItemProvider` and requireJS module :js:`TYPO3/CMS/Impexp/ContextMenuActions`
- - Version item provider :php:`\TYPO3\CMS\Version\ContextMenu\ItemProvider` and requireJS module :js:`TYPO3/CMS/Version/ContextMenuActions`
- - Version item provider :php:`\TYPO3\CMS\Version\ContextMenu\ItemProvider` and requireJS module :js:`TYPO3/CMS/Version/ContextMenuActions`
+ - Beuser item provider :php:`\TYPO3\CMS\Beuser\ContextMenu\ItemProvider` and requireJS module :javascript:`TYPO3/CMS/Beuser/ContextMenuActions`
+ - Impexp item provider :php:`\TYPO3\CMS\Impexp\ContextMenu\ItemProvider` and requireJS module :javascript:`TYPO3/CMS/Impexp/ContextMenuActions`
+ - Version item provider :php:`\TYPO3\CMS\Version\ContextMenu\ItemProvider` and requireJS module :javascript:`TYPO3/CMS/Version/ContextMenuActions`
+ - Version item provider :php:`\TYPO3\CMS\Version\ContextMenu\ItemProvider` and requireJS module :javascript:`TYPO3/CMS/Version/ContextMenuActions`
- Filelist item providers :php:`\TYPO3\CMS\Filelist\ContextMenu\ItemProviders\FileDragProvider`, :php:`\TYPO3\CMS\Filelist\ContextMenu\ItemProviders\FileProvider`,
:php:`\TYPO3\CMS\Filelist\ContextMenu\ItemProviders\FileStorageProvider`, :php:`\TYPO3\CMS\Filelist\ContextMenu\ItemProviders\FilemountsProvider`
- and requireJS module :js:`TYPO3/CMS/Filelist/ContextMenuActions`
+ and requireJS module :javascript:`TYPO3/CMS/Filelist/ContextMenuActions`
.. index:: Backend, JavaScript, PHP-API, TSConfig
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79262-AddPossibilityToCreateTRIMExpressionWithDoctrineDBAL.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79262-AddPossibilityToCreateTRIMExpressionWithDoctrineDBAL.rst
index 5fe7b8c68df0798bfa6517a884211fdaeb6e875e..f4c38a9ccbeb60c13e261e2ad0741482ced3a41f 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79262-AddPossibilityToCreateTRIMExpressionWithDoctrineDBAL.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79262-AddPossibilityToCreateTRIMExpressionWithDoctrineDBAL.rst
@@ -26,10 +26,13 @@ The call to :php:`$queryBuilder->expr()-trim()` can be one of the following:
* :php:`trim('fieldName')`
results in :sql:`TRIM("tableName"."fieldName")`
+
* :php:`trim('fieldName', AbstractPlatform::TRIM_LEADING, 'x')`
results in :sql:`TRIM(LEADING "x" FROM "tableName"."fieldName")`
+
* :php:`trim('fieldName', AbstractPlatform::TRIM_TRAILING, 'x')`
results in :sql:`TRIM(TRAILING "x" FROM "tableName"."fieldName")`
+
* :php:`trim('fieldName', AbstractPlatform::TRIM_BOTH, 'x')`
results in :sql:`TRIM(BOTH "x" FROM "tableName"."fieldName")`
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79341-TCARichtextConfigurationInConfigSection.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79341-TCARichtextConfigurationInConfigSection.rst
index 9ff34c8f0910022b3965923764190f6982813d63..9957762cfeab9badb9172cb559d03cb510612f2a 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79341-TCARichtextConfigurationInConfigSection.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79341-TCARichtextConfigurationInConfigSection.rst
@@ -18,6 +18,7 @@ Impact
Setting `enableRichtext` will result in the text field being rendered with a richtext editor. Config example:
.. code-block:: php
+
'columns' => [
'content' => [
'config' => [
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-HeaderPositionSupportForFluidStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-HeaderPositionSupportForFluidStyledContent.rst
index e4559021794eb6b45dd0ed6f64d95f6c698dadd7..eb583d2dfa99d2b937f7b022ff159b86d56fb1d4 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-HeaderPositionSupportForFluidStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-HeaderPositionSupportForFluidStyledContent.rst
@@ -28,6 +28,7 @@ Default (empty) (No CSS Class added)
Center center ce-headline-center
Right right ce-headline-right
Left left ce-headline-left
+========== ========== ====================
Implementation Example
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-NewContentElementsForFluidStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-NewContentElementsForFluidStyledContent.rst
index 3ccb443ff1e6694991f0c7b94c45c9fc08344d88..df5d19621b669c6b416dbde366a335c6b602220a 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-NewContentElementsForFluidStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-NewContentElementsForFluidStyledContent.rst
@@ -19,6 +19,7 @@ Name cType Description
Text text A regular text element with header and bodytext fields.
Text and Images textpic Any number of images wrapped right around a regular text element.
Images image Any number of images aligned in columns and rows with a caption.
+================= ========== =================================================================
Impact
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForCssStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForCssStyledContent.rst
index 290abd772a03428ace600e346dd48f641525c42e..399947b1dffb83f4f5c3eb642dc952da8e0adcc3 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForCssStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForCssStyledContent.rst
@@ -45,6 +45,7 @@ Small small csc-space-before-small 2em
Medium medium csc-space-before-medium 3em
Large large csc-space-before-large 4em
Extra Large extra-large csc-space-before-extra-large 5em
+============= ============= =============================== =============
Example Output
diff --git a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForFluidStyledContent.rst b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForFluidStyledContent.rst
index b0ad19959f7e9fb82a6c57508bc6db020f604285..b747d58b967d99f2e2dc868094ada08d9f8644ea 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForFluidStyledContent.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.6/Feature-79622-SpaceBeforeAndSpaceAfterClassForFluidStyledContent.rst
@@ -44,6 +44,7 @@ Small small frame-space-before-small 2em
Medium medium frame-space-before-medium 3em
Large large frame-space-before-large 4em
Extra Large extra-large frame-space-before-extra-large 5em
+============= ============= =============================== =============
Example Output
diff --git a/typo3/sysext/core/Documentation/Changelog/8.7/Breaking-80149-RemoveGLOBALSTYPO3_CONF_VARSFEpageOverlayFields.rst b/typo3/sysext/core/Documentation/Changelog/8.7/Breaking-80149-RemoveGLOBALSTYPO3_CONF_VARSFEpageOverlayFields.rst
index b99cfe21a34e4fcd67391e3d01be6089ae48d308..b6d2011743313c3f2112c40105fc20c72d2ab986 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.7/Breaking-80149-RemoveGLOBALSTYPO3_CONF_VARSFEpageOverlayFields.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.7/Breaking-80149-RemoveGLOBALSTYPO3_CONF_VARSFEpageOverlayFields.rst
@@ -41,6 +41,6 @@ Migration
Check the TCA of :sql:`pages_language_overlay` and remove l10n_mode for those fields
that previously were not defined in :php:`$GLOBALS['TYPO3_CONF_VARS']['FE']['pageOverlayFields']`
- and thus should not be overlaid.
+and thus should not be overlaid.
.. index:: Frontend, TCA
diff --git a/typo3/sysext/core/Documentation/Changelog/8.7/Deprecation-80579-ModalCenter.rst b/typo3/sysext/core/Documentation/Changelog/8.7/Deprecation-80579-ModalCenter.rst
index c45e1465a4a37d10d546937aa280fd77fe456454..4f533e49c307551dc616634c9a3638ded61c3c4c 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.7/Deprecation-80579-ModalCenter.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.7/Deprecation-80579-ModalCenter.rst
@@ -9,26 +9,26 @@ See :issue:`80579`
Description
===========
-The method :js:`Modal.center` has been marked as deprecated. Alignment is now
+The method :javascript:`Modal.center` has been marked as deprecated. Alignment is now
handled via CSS and this method is now obsolete.
Impact
======
-Calling :js:`Modal.center` will trigger a console warning in the browser.
+Calling :javascript:`Modal.center` will trigger a console warning in the browser.
Affected Installations
======================
-All 3rd party extensions using :js:`Modal.center` are affected.
+All 3rd party extensions using :javascript:`Modal.center` are affected.
Migration
=========
-Remove obsolete calls to :js:`Modal.center()`.
+Remove obsolete calls to :javascript:`Modal.center()`.
.. index:: JavaScript
diff --git a/typo3/sysext/core/Documentation/Changelog/8.7/Feature-80579-ImprovedJavaScriptModalAPI.rst b/typo3/sysext/core/Documentation/Changelog/8.7/Feature-80579-ImprovedJavaScriptModalAPI.rst
index 60324c9c50db0472ae4df77303bdf4a7cef4bdc8..9bc0cc7f2d9b25f5fb611fa85b6d7b5149457f55 100644
--- a/typo3/sysext/core/Documentation/Changelog/8.7/Feature-80579-ImprovedJavaScriptModalAPI.rst
+++ b/typo3/sysext/core/Documentation/Changelog/8.7/Feature-80579-ImprovedJavaScriptModalAPI.rst
@@ -25,8 +25,8 @@ attributes that also can set by configuration.
Advanced API
------------
-Unlike the existing api functions like :js:`Modal.confirm`, :js:`Modal.loadUrl` or
-:js:`Modal.show`, :js:`Modal.advanced` uses a JavaScript object instead of fixed
+Unlike the existing api functions like :javascript:`Modal.confirm`, :javascript:`Modal.loadUrl` or
+:javascript:`Modal.show`, :javascript:`Modal.advanced` uses a JavaScript object instead of fixed
parameters.
.. code-block:: javascript
@@ -58,8 +58,8 @@ Configuration Options
Type
^^^^
-The :js:`type` will define the behaviour of content loading, and only accepts
-:js:`Modal.types.ajax`, :js:`Modal.types.iframe` and the default :js:`Modal.types.default`.
+The :javascript:`type` will define the behaviour of content loading, and only accepts
+:javascript:`Modal.types.ajax`, :javascript:`Modal.types.iframe` and the default :javascript:`Modal.types.default`.
.. code-block:: javascript
@@ -83,7 +83,7 @@ Title
^^^^^
The `title` will be display above the modal content. For the type
-:js:`Modal.types.iframe` this option will have no effect. As soon as the content
+:javascript:`Modal.types.iframe` this option will have no effect. As soon as the content
from the iframe is loaded, the title will be replaced with title of the
contained document. The default will set the title to "Information".
@@ -99,7 +99,7 @@ Content
^^^^^^^
The `content` accepts only strings that can be either a HTML or a url for types
-:js:`Modal.types.ajax` and :js:`Modal.types.iframe`. The default will show a warning
+:javascript:`Modal.types.ajax` and :javascript:`Modal.types.iframe`. The default will show a warning
that there is a possible misconfiguration of the modal.
.. code-block:: javascript
@@ -134,7 +134,7 @@ Severity
Severity is used to change the appearance of the modal window to represent a
contextual state like success, information, warning or danger. The default is
-:js:`Severity.notice`. Only options provided by the :js:`Severity` object will be
+:javascript:`Severity.notice`. Only options provided by the :javascript:`Severity` object will be
accepted.
.. code-block:: javascript
@@ -199,8 +199,8 @@ Style
^^^^^
The ``style`` option will change the appearance of the modal like the ``severity``
-both without contextual meaning. The default option is :js:`Modal.styles.light`.
-The second available option is :js:`Modal.styles.dark` will override all contextual
+both without contextual meaning. The default option is :javascript:`Modal.styles.light`.
+The second available option is :javascript:`Modal.styles.dark` will override all contextual
styling.
.. code-block:: javascript
@@ -215,11 +215,11 @@ Size
^^^^
While the modal itself adapts to the window, there are several options available
-to limit the maximal size of the modal. The sizes :js:`Modal.sizes.small` and the
-default :js:`Modal.sizes.default` will automaticly adapt to the content and are only
-limited to the width of the modal. :js:`Modal.sizes.large` and :js:`Modal.sizes.full`
+to limit the maximal size of the modal. The sizes :javascript:`Modal.sizes.small` and the
+default :javascript:`Modal.sizes.default` will automaticly adapt to the content and are only
+limited to the width of the modal. :javascript:`Modal.sizes.large` and :javascript:`Modal.sizes.full`
are designed to contain a undefined lenth of content in a fixed sized modal.
-These are suited best for :js:`Modal.types.ajax` or :js:`Modal.types.iframe` content.
+These are suited best for :javascript:`Modal.types.ajax` or :javascript:`Modal.types.iframe` content.
.. code-block:: javascript
@@ -280,7 +280,7 @@ Callback after ajax processing
Callback function that will be called after the ajax call has been done and
the response added to the desired location. This option is only available for
-type :js:`Modal.types.ajax`.
+type :javascript:`Modal.types.ajax`.
.. code-block:: javascript
@@ -298,7 +298,7 @@ Target for ajax response
The ajax response will be added to the body of the particular modal window by
default but can be set to a different selector if necessary. This option is only
-available for type :js:`Modal.types.ajax`.
+available for type :javascript:`Modal.types.ajax`.
.. code-block:: javascript
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-71306-DroppedProtocolFieldFromPageTypeLinkToExternalURL.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-71306-DroppedProtocolFieldFromPageTypeLinkToExternalURL.rst
index 5927a8920523f62cdcbeab8286b6860f41c9f5b7..d1621cb0368bcbbe85ae7a2a0041e6396c084633 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-71306-DroppedProtocolFieldFromPageTypeLinkToExternalURL.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-71306-DroppedProtocolFieldFromPageTypeLinkToExternalURL.rst
@@ -20,7 +20,7 @@ The according PHP functionality has been removed:
* The TCA definition for "pages.urltype" and "pages_language_overlay.urltype" has been removed.
* The according database fields is not populated anymore, and will be removed when using the Database
-Scheme Migrations in the install tool. For new installations the fields are not created anymore.
+ Scheme Migrations in the install tool. For new installations the fields are not created anymore.
* The public PHP class property php:``PageRepository->urltypes`` has been removed.
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-82378-RemoveNamespacedJQuery.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-82378-RemoveNamespacedJQuery.rst
index 57feb754f535f02b772d48d974c03f0d93def65f..81b9ba0353dead80b4b284b863bd4bf2e728c442 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-82378-RemoveNamespacedJQuery.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-82378-RemoveNamespacedJQuery.rst
@@ -10,7 +10,7 @@ Description
===========
The possibility to jail jQuery into a namespace has been removed. This affects custom namespaces and
-:js:`TYPO3.jQuery` as well.
+:javascript:`TYPO3.jQuery` as well.
The class constants :php:`TYPO3\CMS\Core\Page\PageRenderer::JQUERY_NAMESPACE_DEFAULT` and
:php:`TYPO3\CMS\Core\Page\PageRenderer::JQUERY_NAMESPACE_DEFAULT_NOCONFLICT` have been removed without
@@ -22,20 +22,20 @@ Impact
Namespaces will be ignored and automatically fall back to noConflict behavior.
-Calling :js:`TYPO3.jQuery.*` will result in a TypeError.
+Calling :javascript:`TYPO3.jQuery.*` will result in a TypeError.
Affected Installations
======================
All installations using a custom namespace, :php:`PageRenderer::JQUERY_NAMESPACE_DEFAULT`
-:php:`PageRenderer::JQUERY_NAMESPACE_DEFAULT` or relying on :js:`TYPO3.jQuery` are affected.
+:php:`PageRenderer::JQUERY_NAMESPACE_DEFAULT` or relying on :javascript:`TYPO3.jQuery` are affected.
Migration
=========
-Remove :php:`$namespace` argument in :php:`PageRenderer->loadJquery()` and either use :js:`window.$` or migrate
+Remove :php:`$namespace` argument in :php:`PageRenderer->loadJquery()` and either use :javascript:`window.$` or migrate
to RequireJS.
.. index:: Backend, Frontend, JavaScript, PartiallyScanned
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-83161-RemoveTYPO3LLLUsagesInTYPO3Core.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-83161-RemoveTYPO3LLLUsagesInTYPO3Core.rst
index 9fa85cb8746a22a54108cf03ce1cd503427e346d..e38e5b0306ff262ed06229adc8dd88b82d5ad55c 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-83161-RemoveTYPO3LLLUsagesInTYPO3Core.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-83161-RemoveTYPO3LLLUsagesInTYPO3Core.rst
@@ -9,25 +9,25 @@ See :issue:`83161`
Description
===========
-After moving to the :js:`TYPO3.lang` API for javascript, the :js:`TYPO3.LLL` is not needed anymore.
+After moving to the :javascript:`TYPO3.lang` API for javascript, the :javascript:`TYPO3.LLL` is not needed anymore.
Impact
======
-All extensions which are using :js:`TYPO3.LLL` for translation in javascript should be checked and updated accordingly.
+All extensions which are using :javascript:`TYPO3.LLL` for translation in javascript should be checked and updated accordingly.
Affected Installations
======================
-Any installation using extensions, which are using :js:`TYPO3.LLL`.
+Any installation using extensions, which are using :javascript:`TYPO3.LLL`.
Migration
=========
-Use :js:`TYPO3.lang['label']` from javascript. To make custom language labels available in javascript,
+Use :javascript:`TYPO3.lang['label']` from javascript. To make custom language labels available in javascript,
add :php:`$this->pageRenderer->addInlineLanguageLabelFile('EXT:foo/Resources/Private/Language/locallang.xlf');`
in your backend controller.
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-83265-DroppedSupportForSettingTypeNumViaIdGETParameterInFrontend.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-83265-DroppedSupportForSettingTypeNumViaIdGETParameterInFrontend.rst
index 5d540a4bd9fcd595c59784afc45d9fda212ec076..a68e37feb4c34e2bd9de0159371fdb6c336700c5 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-83265-DroppedSupportForSettingTypeNumViaIdGETParameterInFrontend.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-83265-DroppedSupportForSettingTypeNumViaIdGETParameterInFrontend.rst
@@ -22,7 +22,7 @@ since TYPO3 v4.0.
Impact
======
-Calling Frontend URLs via `index.php?id=23.13" - adding the typeNum with a dot - will result in a PageNotFound exception.
+Calling Frontend URLs via `index.php?id=23.13` - adding the typeNum with a dot - will result in a PageNotFound exception.
Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-78410-DeprecatePopoverMemberInstanceInTYPO3GlobalObject.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-78410-DeprecatePopoverMemberInstanceInTYPO3GlobalObject.rst
index 3e6a391134b952345a960d043bb746c3d4a52751..1edde4fd028bbd6b51579e2383de55673c468e3a 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-78410-DeprecatePopoverMemberInstanceInTYPO3GlobalObject.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-78410-DeprecatePopoverMemberInstanceInTYPO3GlobalObject.rst
@@ -9,7 +9,7 @@ See :issue:`78410`
Description
===========
-The member instance :js:`TYPO3.Popover` has been marked as deprecated.
+The member instance :javascript:`TYPO3.Popover` has been marked as deprecated.
Impact
@@ -21,7 +21,7 @@ Using the global instance will not throw any deprecation message.
Affected Installations
======================
-Any backend JavaScript or TypeScript using :js:`TYPO3.Popover`.
+Any backend JavaScript or TypeScript using :javascript:`TYPO3.Popover`.
Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-81464-AddAPIForMetaTagManagement.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-81464-AddAPIForMetaTagManagement.rst
index aa1699034010fd76540a1cd53d6b1b6ed5ec5f5e..4e700dabf8dd5b5f918fdf3e34b1da8cb4682589 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-81464-AddAPIForMetaTagManagement.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-81464-AddAPIForMetaTagManagement.rst
@@ -16,7 +16,7 @@ The following methods have been marked as deprecated and should no longer be use
It has been replaced by the method :php:`PageRenderer->setMetaTag()`.
-.. codeblock:: php
+.. code-block:: php
$pageRenderer = GeneralUtility::makeInstance(PageRenderer::class);
// has meta tag been set already?
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-82603-DeprecateStorageModule.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-82603-DeprecateStorageModule.rst
index e999dcaeca8f39e1a374c3d200597be572e5c07a..8f2bf7505eae5b0eb74e9d2847bdf3fe2117adc6 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-82603-DeprecateStorageModule.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-82603-DeprecateStorageModule.rst
@@ -9,25 +9,25 @@ See :issue:`82603`
Description
===========
-The RequireJS module :js:`TYPO3/CMS/Backend/Storage` has been marked as deprecated. The module has been split into the
-modules :js:`TYPO3/CMS/Backend/Storage/Client` and :js:`TYPO3/CMS/Backend/Storage/Persistent`.
+The RequireJS module :javascript:`TYPO3/CMS/Backend/Storage` has been marked as deprecated. The module has been split into the
+modules :javascript:`TYPO3/CMS/Backend/Storage/Client` and :javascript:`TYPO3/CMS/Backend/Storage/Persistent`.
Impact
======
-Using :js:`TYPO3/CMS/Backend/Storage` will trigger a warning in the browser's developer console.
+Using :javascript:`TYPO3/CMS/Backend/Storage` will trigger a warning in the browser's developer console.
Affected Installations
======================
-All extensions using :js:`TYPO3/CMS/Backend/Storage` are affected.
+All extensions using :javascript:`TYPO3/CMS/Backend/Storage` are affected.
Migration
=========
-Instead of using :js:`Storage.Client` and :js:`Storage.Persistent` use the introduced modules instead.
+Instead of using :javascript:`Storage.Client` and :javascript:`Storage.Persistent` use the introduced modules instead.
Example code:
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-82609-DeprecateTYPO3Utility.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-82609-DeprecateTYPO3Utility.rst
index 7e56dcb93c344672810c813c50a8d03c6e32da35..4c1b83d85ac60b2942ad9334b1fe3a7259ec3dd7 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-82609-DeprecateTYPO3Utility.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Deprecation-82609-DeprecateTYPO3Utility.rst
@@ -9,20 +9,20 @@ See :issue:`82609`
Description
===========
-The public property :js:`TYPO3.Utility` has been marked as deprecated. `Utility` may be used in AMD based modules by
-importing :js:`TYPO3/CMS/Backend/Utility` instead.
+The public property :javascript:`TYPO3.Utility` has been marked as deprecated. `Utility` may be used in AMD based modules by
+importing :javascript:`TYPO3/CMS/Backend/Utility` instead.
Affected Installations
======================
-All extensions using :js:`TYPO3.Utility` are affected.
+All extensions using :javascript:`TYPO3.Utility` are affected.
Migration
=========
-Import :js:`TYPO3/CMS/Backend/Utility` in your AMD module.
+Import :javascript:`TYPO3/CMS/Backend/Utility` in your AMD module.
Example code:
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-57594-OptimizeReflectionServiceCacheHandling.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-57594-OptimizeReflectionServiceCacheHandling.rst
index ca07f9406a0cbbae8c3a24e08ed2f60125cf25de..0f32fe35c6177bca9f7c2f127ecd77ce979725e3 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-57594-OptimizeReflectionServiceCacheHandling.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-57594-OptimizeReflectionServiceCacheHandling.rst
@@ -28,27 +28,27 @@ There were a few issues with these two approaches:
* Data was fetched multiple times at different locations
* The `extbase_reflection` cache was stored each plugin separately, resulting in a lot of redundant
-cache data for each plugin cache
+ cache data for each plugin cache
* At a lot of places, the reflection service was used to reflect objects, but the data wasn't cached
-or taken from a cache resulting in performance drawbacks
+ or taken from a cache resulting in performance drawbacks
Impact
======
* The `extbase_object` cache has been removed completely and all necessary information about objects,
-mainly :php:`@inject` functionality, is now fetched from the `ReflectionService` as well.
+ mainly :php:`@inject` functionality, is now fetched from the `ReflectionService` as well.
* The `ReflectionService` does still create `ClassSchema` instances but these were improved a lot.
-All necessary information is now gathered during the instantiation of ClassSchema instances. This
-means that all necessary data is fetched once and then it can be used everywhere making any further
-reflection superfluous.
+ All necessary information is now gathered during the instantiation of ClassSchema instances. This
+ means that all necessary data is fetched once and then it can be used everywhere making any further
+ reflection superfluous.
* As runtime reflection has been removed completely, along with it several reflection classes, that
-analyzed doc blocks, have been removed as well. These are no longer necessary.
+ analyzed doc blocks, have been removed as well. These are no longer necessary.
* The `extbase_reflection` cache is no longer plugin based and will no longer be stored in the
-database in the first place. Serialized `ClassSchema` instances will be stored in `typo3temp/var/Cache`.
+ database in the first place. Serialized `ClassSchema` instances will be stored in `typo3temp/var/Cache`.
.. index:: PHP-API
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-73357-MakeThumbnailSizeInFileBrowserConfigurable.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-73357-MakeThumbnailSizeInFileBrowserConfigurable.rst
index c0a806b03fc43a3533d5af34c90ac14da56251dd..0e06827a933377bc64c2b228803483cc65f96a29 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-73357-MakeThumbnailSizeInFileBrowserConfigurable.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-73357-MakeThumbnailSizeInFileBrowserConfigurable.rst
@@ -14,6 +14,7 @@ The default size of thumbnails in the file list is 64x64. These values can now b
Example:
.. code-block:: typoscript
+
options.file_list.thumbnail.width = 256
options.file_list.thumbnail.height = 256
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-79777-AddedDeletedColumnForSchedulerTasks.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-79777-AddedDeletedColumnForSchedulerTasks.rst
index fd7bdbb37b2b69b64f54285c2c559abc8014ddec..bc3c602d985aed9036d5b996304b745228535fee 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-79777-AddedDeletedColumnForSchedulerTasks.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-79777-AddedDeletedColumnForSchedulerTasks.rst
@@ -9,7 +9,7 @@ See :issue:`79777`
Description
===========
-A reference to a previously deleted task is now kept in the database with a :sql:`deleted=1` flag, in order to check
-historic calls on scheduler tasks.
+A reference to a previously deleted task is now kept in the database with a :sql:`deleted=1` flag,
+in order to check historic calls on scheduler tasks.
.. index:: Backend, NotScanned
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-81223-IncludeCSSinlineProperty.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-81223-IncludeCSSinlineProperty.rst
index e008f383d7d192ebc71f19f42f5a51c346e0011d..3a22a113a9461b9bf34fba054a0ed0938c3349e2 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-81223-IncludeCSSinlineProperty.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-81223-IncludeCSSinlineProperty.rst
@@ -19,6 +19,7 @@ Impact
Example:
.. code-block:: typoscript
+
page.includeCSS {
inline = EXT:test/Resources/Public/Css/inline.css
inline {
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-81464-AddAPIForMetaTagManagement.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-81464-AddAPIForMetaTagManagement.rst
index 29e37ef5eb6ccb03a60719079b727408bdb909f0..78bc1b3a51c5cdcdecef2fd201d1d9d050ff3ea1 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-81464-AddAPIForMetaTagManagement.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-81464-AddAPIForMetaTagManagement.rst
@@ -61,7 +61,7 @@ Used to remove a meta tag from the stack.
Example
-------
-.. codeblock:: php
+.. code-block:: php
$pageRenderer = GeneralUtility::makeInstance(PageRenderer::class);
// has meta tag been set already?
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-81901-ExtendT3editor.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-81901-ExtendT3editor.rst
index 8b3f59ec581a96bb0f8ea8ce794b4866f24e0142..0595152a2f0da87b3b1cd8f8bc515b49ece2d50b 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-81901-ExtendT3editor.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-81901-ExtendT3editor.rst
@@ -45,13 +45,13 @@ To register an addon, the following code may be used:
| Key | Type | Description |
+==============+========+=============================================================================================================================================================================+
| <identifier> | string | Represents the unique identifier of the module (`my/addon` in this example) |
-+==============+========+=============================================================================================================================================================================+
++-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| module | string | Mandatory: Holds the RequireJS namespace of the CodeMirror module. For custom modules placed in an extension, the known `TYPO3/CMS/Extension/Module` namespace must be used |
-+==============+========+=============================================================================================================================================================================+
++-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| cssFiles | array | Holds all CSS files that must be loaded for the module |
-+==============+========+=============================================================================================================================================================================+
++-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| options | array | Options that are used by the addon |
-+==============+========+=============================================================================================================================================================================+
++-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| modes | array | "Jails" the addon to specific modes. This means, the module is only loaded if any of the given modes is used |
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
@@ -73,11 +73,11 @@ To register a mode, the following code may be used:
| Key | Type | Description |
+==============+========+=========================================================================================================================================================================+
| <identifier> | string | Represents the unique identifier and format code of the mode (`css` in this example). The format code is used in TCA to define the CodeMirror mode to be used |
-+==============+========+=========================================================================================================================================================================+
++--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| module | string | Mandatory: Holds the RequireJS namespace of the CodeMirror mode. For custom modules placed in an extension, the known `TYPO3/CMS/Extension/Mode` namespace must be used |
-+==============+========+=========================================================================================================================================================================+
++--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| extensions | array | Binds the mode to specific file extension. This is important for using T3editor in the Filelist module. |
-+==============+========+=========================================================================================================================================================================+
++--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| default | bool | If set, the mode is used as fallback if no sufficient mode is available. By factory default, the default mode is `html` |
+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-82441-InjectLoggerWhenCreatingObjects.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-82441-InjectLoggerWhenCreatingObjects.rst
index 443850292108d02dd2afe42e7d5f8e16a9546412..c4f6e083db52948dc49c0260f19e2ea0086c57f8 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Feature-82441-InjectLoggerWhenCreatingObjects.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Feature-82441-InjectLoggerWhenCreatingObjects.rst
@@ -21,16 +21,16 @@ A minimal example looks like this (example from a test case fixture):
.. code-block:: php
-<?php
-declare(strict_types=1);
-namespace TYPO3\CMS\Core\Tests\Unit\Utility\Fixtures;
+ <?php
+ declare(strict_types=1);
+ namespace TYPO3\CMS\Core\Tests\Unit\Utility\Fixtures;
-use Psr\Log\LoggerAwareInterface;
-use Psr\Log\LoggerAwareTrait;
+ use Psr\Log\LoggerAwareInterface;
+ use Psr\Log\LoggerAwareTrait;
-class GeneralUtilityMakeInstanceInjectLoggerFixture implements LoggerAwareInterface
-{
- use LoggerAwareTrait;
-}
+ class GeneralUtilityMakeInstanceInjectLoggerFixture implements LoggerAwareInterface
+ {
+ use LoggerAwareTrait;
+ }
.. index:: PHP-API
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Important-23178-NewTYPO3_CONF_VARSOptionFEpageNotFound_handling_accessdeniedheader.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Important-23178-NewTYPO3_CONF_VARSOptionFEpageNotFound_handling_accessdeniedheader.rst
index 005b5aa0d2a9d7472cc9ad88064e11cf025e1eca..cc400fcd8d5afe3c4af723188acf1a0d2555b3fe 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Important-23178-NewTYPO3_CONF_VARSOptionFEpageNotFound_handling_accessdeniedheader.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Important-23178-NewTYPO3_CONF_VARSOptionFEpageNotFound_handling_accessdeniedheader.rst
@@ -11,7 +11,7 @@ Description
In order to send a correct HTTP header to the browser when access to a page is denied,
a new option :php:`pageNotFound_handling_accessdeniedheader` has been introduced to
-:php:`$GLOBALS['TYPO3_CONF_VARS'].
+:php:`$GLOBALS['TYPO3_CONF_VARS']`.
The option :php:`$GLOBALS['FE']['pageNotFound_handling_accessdeniedheader']` allows to configure the
header which defaults to :php:`HTTP/1.0 403 Access denied`.
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Important-81568-MigrateChashConfiguration.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Important-81568-MigrateChashConfiguration.rst
index f13a692448ba655e1abc57bf3326451ce48260bc..5657dc91857cb3a8429a7bd2c3148bba8f004d84 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Important-81568-MigrateChashConfiguration.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Important-81568-MigrateChashConfiguration.rst
@@ -15,21 +15,21 @@ into an array-structured form.
The following cHash-related configuration entries below have been migrated:
- :php:`$TYPO3_CONF_VARS['FE']['cHashExcludedParameters']` is now an array instead of a
-comma-separated list, and migrated to :php:`$TYPO3_CONF_VARS['FE']['cacheHash']['excludedParameters']`
+ comma-separated list, and migrated to :php:`$TYPO3_CONF_VARS['FE']['cacheHash']['excludedParameters']`
- :php:`$TYPO3_CONF_VARS['FE']['cHashOnlyForParameters']` is now an array instead of a
-comma-separated list, and migrated to :php:`$TYPO3_CONF_VARS['FE']['cacheHash']['cachedParametersWhiteList']`
+ comma-separated list, and migrated to :php:`$TYPO3_CONF_VARS['FE']['cacheHash']['cachedParametersWhiteList']`
- :php:`$TYPO3_CONF_VARS['FE']['cHashRequiredParameters']` is now an array instead of a
-comma-separated list, and migrated to :php:`$TYPO3_CONF_VARS['FE']['cacheHash']['requireCacheHashPresenceParameters']`
+ comma-separated list, and migrated to :php:`$TYPO3_CONF_VARS['FE']['cacheHash']['requireCacheHashPresenceParameters']`
- :php:`$TYPO3_CONF_VARS['FE']['cHashExcludedParametersIfEmpty']`
* If the old value was ``*``, the following parameter is now set to true to the
- option :php:`$TYPO3_CONF_VARS['FE']['cacheHash']['excludeAllEmptyParameters']`
+ option :php:`$TYPO3_CONF_VARS['FE']['cacheHash']['excludeAllEmptyParameters']`
* If the old values were a comma-separated list, they are now migrated as an array to
- :php:`$TYPO3_CONF_VARS['FE']['cacheHash']['excludedParametersIfEmpty']`
+ :php:`$TYPO3_CONF_VARS['FE']['cacheHash']['excludedParametersIfEmpty']`
These values are now migrated as a "silent upgrade wizard" via the Install Tool to the format
that TYPO3 uses internally since several versions.
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Important-81868-OptimizeAutoloaderIsNoLongerForcedInComposerjson.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Important-81868-OptimizeAutoloaderIsNoLongerForcedInComposerjson.rst
index fe4177f75032cfd0066b9c8e9333a906733d3a5b..ac1552cb3653c500e77636b9b1b326fc9b1d3056 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Important-81868-OptimizeAutoloaderIsNoLongerForcedInComposerjson.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Important-81868-OptimizeAutoloaderIsNoLongerForcedInComposerjson.rst
@@ -13,8 +13,11 @@ The option "optimize autoloader" (in config section of TYPO3's own composer.json
optimized autoloader files.
This improves speed but had three disadvantages:
+
- creating optimized autoloader may take much longer
+
- new namespaces (folders) during development require an additional :shell:`composer dump`
+
- no possibility existing to deactivate optimized autoloader
from CLI, once it's set in composer.json config section
diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Important-82328-EXTform-UseOwnFolderForFormDefinitions.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Important-82328-EXTform-UseOwnFolderForFormDefinitions.rst
index 6b5be4648aca00ae64f3601096d97ed7d8b40ce4..64ca71c44ff08ea82c97b8b0ae626c9bef16f9b0 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.0/Important-82328-EXTform-UseOwnFolderForFormDefinitions.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.0/Important-82328-EXTform-UseOwnFolderForFormDefinitions.rst
@@ -18,8 +18,7 @@ but not edited.
Since no migration wizard can be provided for this, a manual migration is
necessary which can be done
-1) ... by moving all form definitions to the new directory via filesystem or
-2) ... by duplicating all form definitions (thus storing them in the new
-location) and removing the old form definitions.
+* by moving all form definitions to the new directory via filesystem or
+* by duplicating all form definitions (thus storing them in the new location) and removing the old form definitions.
.. index:: Backend
diff --git a/typo3/sysext/core/Documentation/Includes.txt b/typo3/sysext/core/Documentation/Includes.txt
index 521e23923c6c83cccaaba5dac66a52f1590f4acc..fded53037192cd6494b432d0ee4763a43b88b4ca 100644
--- a/typo3/sysext/core/Documentation/Includes.txt
+++ b/typo3/sysext/core/Documentation/Includes.txt
@@ -8,9 +8,12 @@
.. role:: typoscript(code)
.. role:: typescript(code)
.. role:: shell(code)
+.. role:: sql(code)
.. role:: ts(typoscript)
:class: typoscript
+.. role:: javascript(js)
+ :class: js
.. default-role:: code
.. highlight:: php