[TASK] Remove TYPO3 v12.4 related version hints

Releases: main, 13.4
TYPO3-Documentation · Oct 21, 2024 · 1f26918 · 1f26918
1 parent 3ff3b4a
commit 1f26918
Show file tree

Hide file tree

Showing 26 changed files with 17 additions and 228 deletions.
diff --git a/Documentation/Conditions/Index.rst b/Documentation/Conditions/Index.rst
@@ -940,18 +940,15 @@ ip()
 request()
 =========
 
-..  deprecated:: 12.3
-    Using this function in **page TSconfig** or **user TSconfig** conditions is
-    deprecated. Such conditions will stop working with TYPO3 v13 and will then
-    always evaluate to false. For migration hints see the
-    :ref:`changelog <ext_core:deprecation-100047-1677608959>`.
-
 ..  confval:: request()
     :name: condition-request
     :type: Mixed
 
     Allows to fetch information from current request.
 
+    ..  note:: This function cannot be used in **page TSconfig** or
+        **user TSconfig** conditions. They always evaluate to false.
+
 ..  tip::
     Checking for the :ref:`request object <t3coreapi:typo3-request>` before
     using in a condition may be necessary, for example, when using

diff --git a/Documentation/ContentObjects/Extbaseplugin/Index.rst b/Documentation/ContentObjects/Extbaseplugin/Index.rst
@@ -1,13 +1,12 @@
 ..  include:: /Includes.rst.txt
 ..  index:: Content objects; EXTBASEPLUGIN
+..  _cobj-extbaseplugin-history:
 ..  _cobj-extbaseplugin:
 
 =============
 EXTBASEPLUGIN
 =============
 
-..  versionadded:: 12.3
-
 The content object :typoscript:`EXTBASEPLUGIN` allows to render
 :ref:`Extbase <t3coreapi:extbase>` plugins.
 
@@ -98,30 +97,3 @@ action by getting the currentContentObject from the request:
     :php-short:`\TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer` as
     potential user input. Do not use it unescaped and do not trust to receive
     certain types.
-
-..  _cobj-extbaseplugin-history:
-
-History
-=======
-
-The :typoscript:`EXTBASEPLUGIN` allows Extbase authors to not reference the
-Extbase Bootstrap class anymore, like for previous TYPO3 versions below version
-12.
-
-Previously, TypoScript code for Extbase plugins looked like this:
-
-..  code-block:: typoscript
-
-    page.10 = USER
-    page.10 {
-        userFunc = TYPO3\\CMS\\Extbase\\Core\\Bootstrap->run
-        extensionName = MyExtension
-        pluginName = MyPlugin
-    }
-
-This way still works, but it is recommended to use the
-:typoscript:`EXTBASEPLUGIN` content object, as the direct reference to a PHP
-class (Bootstrap) might be optimized in future versions.
-
-For extension that need to remain compatible with TYPO3 v11 and v12, the
-Bootstrap way should be used.
diff --git a/Documentation/ContentObjects/Fluidtemplate/Index.rst b/Documentation/ContentObjects/Fluidtemplate/Index.rst
@@ -115,24 +115,6 @@ Properties
 
     Sets the extension name of the controller.
 
-    ..  warning::
-        Up to TYPO3 v11, this property could be used as an alternative to the `extensionName`
-        argument in the :ref:`f:translate <t3viewhelper:typo3-fluid-translate>`
-        and :ref:`f:uri.resource <t3viewhelper:typo3-fluid-uri-resource>` ViewHelpers,
-        provided that translations and public images were stored in the usual paths in your extension.
-
-        Since TYPO3 v12 this is no longer supported and it is recommended to either use absolute keys:
-
-        ..  code-block:: html
-
-            <f:translate key="LLL:EXT:my_extension/Resources/Private/Language/locallang.xlf:myKey" />
-
-        or the `extensionName` argument plus `key` argument in the ViewHelper:
-
-        ..  code-block:: html
-
-            <f:translate key="myKey" extensionName="MyExtension" />
-
 ..  _cobj-fluidtemplate-properties-extbase-controllername:
 
 ..  confval:: extbase.controllerName

diff --git a/Documentation/ContentObjects/Hmenu/Tmenu/Index.rst b/Documentation/ContentObjects/Hmenu/Tmenu/Index.rst
@@ -171,14 +171,6 @@ Properties
         has clicked a menu item and the menu folds out the next level. This
         can enable that to happen on all items as default.
 
-    ..  confval:: collapse (removed)
-        :name: menu-common-properties-collapse
-
-        ..  versionchanged:: 12.0
-            The property was removed with TYPO3 v12.0. Use a custom user function or
-            the PSR-14 event :ref:`t3coreapi:FilterMenuItemsEvent` to modify the menu
-            items.
-
     ..  confval:: sectionIndex
         :name: menu-common-properties-sectionIndex
         :type: :ref:`data-type-boolean`
@@ -466,8 +458,6 @@ Properties
         holding the page ID of the page coming from (could be used to look up
         which fe\_groups was required for access.
 
-        ..  versionadded:: 12.3
-
         **.ATagParams**: Add custom attributes to the anchor tag.
 
         ..  rubric:: Example

diff --git a/Documentation/DataProcessing/CommaSeparatedValueProcessor.rst b/Documentation/DataProcessing/CommaSeparatedValueProcessor.rst
@@ -6,11 +6,6 @@
 `comma-separated-value` data processor
 ======================================
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`comma-separated-value` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\CommaSeparatedValueProcessor`.
-
 The :php:`\TYPO3\CMS\Frontend\DataProcessing\CommaSeparatedValueProcessor`,
 alias `comma-separated-value`, allows to split values into a
 two-dimensional array used for :abbr:`CSV (Comma-separated values)` files or

diff --git a/Documentation/DataProcessing/DatabaseQueryProcessor.rst b/Documentation/DataProcessing/DatabaseQueryProcessor.rst
@@ -6,11 +6,6 @@
 `database-query` data processor
 ===============================
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`database-query` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor`.
-
 The :php:`\TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor`,
 alias `database-query`, fetches records from the database, using
 standard TypoScript :ref:`select` semantics. The result is then passed to the

diff --git a/Documentation/DataProcessing/FilesProcessor.rst b/Documentation/DataProcessing/FilesProcessor.rst
@@ -6,11 +6,6 @@
 `files` data processor
 ======================
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`files` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\FilesProcessor`.
-
 This data processor :php:`\TYPO3\CMS\Frontend\DataProcessing\FilesProcessor`,
 alias `files`, can be used for processing file information:
 

diff --git a/Documentation/DataProcessing/FlexFormProcessor.rst b/Documentation/DataProcessing/FlexFormProcessor.rst
@@ -7,11 +7,6 @@
 `flex-form` data processor
 ==========================
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`flex-form` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\FlexFormProcessor`.
-
 TYPO3 offers :ref:`FlexForms <t3coreapi:flexforms>` which can be used to store
 data within an XML structure inside a single database column. The data processor
 :php:`\TYPO3\CMS\Frontend\DataProcessing\FlexFormProcessor`,
@@ -86,9 +81,6 @@ Example of a minimal TypoScript configuration
 ..  code-block:: typoscript
     :caption: EXT:my_extension/Configuration/TypoScript/setup.typoscript
 
-    # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-    # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\FlexFormProcessor
-    # Since TYPO3 v12.1 one can also use the available alias
     10 = flex-form
 
 The converted array can be accessed within the Fluid template with the
@@ -102,9 +94,6 @@ Example of an advanced TypoScript configuration
 ..  code-block:: typoscript
     :caption: EXT:my_extension/Configuration/TypoScript/setup.typoscript
 
-    # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-    # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\FlexFormProcessor
-    # Since TYPO3 v12.1 one can also use the available alias
     10 = flex-form
     10 {
         fieldName = my_flexform_field
@@ -122,9 +111,6 @@ Example with a custom sub-processor
 ..  code-block:: typoscript
     :caption: EXT:my_extension/Configuration/TypoScript/setup.typoscript
 
-    # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-    # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\FlexFormProcessor
-    # Since TYPO3 v12.1 one can also use the available alias
     10 = flex-form
     10 {
         fieldName = my_flexform_field

diff --git a/Documentation/DataProcessing/GalleryProcessor.rst b/Documentation/DataProcessing/GalleryProcessor.rst
@@ -6,11 +6,6 @@
 `gallery` data processor
 ========================
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`gallery` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\GalleryProcessor`.
-
 The :php:`\TYPO3\CMS\Frontend\DataProcessing\GalleryProcessor`,
 alias `gallery`, provides the logic for working with galleries and
 calculates the maximum asset size. It uses the files already present in

diff --git a/Documentation/DataProcessing/LanguageMenuProcessor.rst b/Documentation/DataProcessing/LanguageMenuProcessor.rst
@@ -6,11 +6,6 @@
 language-menu data processor
 ============================
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`language-menu` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\LanguageMenuProcessor`.
-
 The processor :php:`\TYPO3\CMS\Frontend\DataProcessing\LanguageMenuProcessor`,
 alias `language-menu`, generates a list of language menu items which can be
 assigned to the :typoscript:`FLUIDTEMPLATE` as a variable.

diff --git a/Documentation/DataProcessing/MenuProcessor.rst b/Documentation/DataProcessing/MenuProcessor.rst
@@ -6,11 +6,6 @@
 `menu` data processor
 =====================
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`menu` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\MenuProcessor`.
-
 The :php:`\TYPO3\CMS\Frontend\DataProcessing\MenuProcessor`,
 alias `menu`, utilizes :ref:`HMENU <cobj-hmenu>` to generate a list
 of menu items which can be assigned to :typoscript:`FLUIDTEMPLATE` as a

diff --git a/Documentation/DataProcessing/SiteLanguageProcessor.rst b/Documentation/DataProcessing/SiteLanguageProcessor.rst
@@ -6,11 +6,6 @@
 `site-language` data processor
 ==============================
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`site-language` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\SiteLanguageProcessor`.
-
 The :php:`\TYPO3\CMS\Frontend\DataProcessing\SiteLanguageProcessor`,
 alias `site-language`, fetches language-related data from the
 :ref:`site configuration<t3coreapi:sitehandling>`.

diff --git a/Documentation/DataProcessing/SiteProcessor.rst b/Documentation/DataProcessing/SiteProcessor.rst
@@ -6,11 +6,6 @@
 `site` data processor
 =====================
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`site` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\SiteProcessor`.
-
 The :php:`\TYPO3\CMS\Frontend\DataProcessing\SiteProcessor`,
 alias `site`, fetches data from the :ref:`site configuration
 <t3coreapi:sitehandling>`.

diff --git a/Documentation/DataProcessing/SplitProcessor.rst b/Documentation/DataProcessing/SplitProcessor.rst
@@ -6,11 +6,6 @@
 `split` data processor
 ======================
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`split` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\SplitProcessor`.
-
 The :php:`\TYPO3\CMS\Frontend\DataProcessing\SplitProcessor`,
 alias `split`, allows to split values separated with a delimiter
 from a single database field. The result is an array that can be iterated over.

diff --git a/Documentation/Functions/Data.rst b/Documentation/Functions/Data.rst
@@ -991,13 +991,11 @@ siteLanguage
         configuration setting.
 
     :typoscript:`hreflang`
-        ..  versionchanged:: 12.4
-            This option is not relevant anymore for regular websites without
-            rendering hreflang tag, but is now customizable, and has a proper
-            fallback.
-
         The language tag for this language defined by RFC 1766 / 3066 for
-        :html:`hreflang` attributes
+        :html:`hreflang` attributes.
+
+        This option is not relevant for regular websites without
+        rendering hreflang tag.
 
     :typoscript:`languageId`
         The language mapped to the ID of the site language.
@@ -1045,8 +1043,6 @@ Example: Get values from the current site language
 siteSettings
 ------------
 
-..  versionadded:: 12.1
-
 ..  confval:: siteSettings
     :name: data-siteSettings
 

diff --git a/Documentation/Functions/If.rst b/Documentation/Functions/If.rst
@@ -70,8 +70,6 @@ bitAnd
 contains
 --------
 
-..  versionadded:: 12.1
-
 ..  confval::  contains
     :name: if-contains
     :type:  value / :ref:`stdwrap`
@@ -119,8 +117,6 @@ directReturn
 endsWith
 --------
 
-..  versionadded:: 12.1
-
 ..  confval::  endsWith
     :name: if-endsWith
     :type:  value / :ref:`stdwrap`
@@ -302,8 +298,6 @@ negate
 startsWith
 ----------
 
-..  versionadded:: 12.1
-
 ..  confval::  startsWith
     :name: if-startsWith
     :type:  value / :ref:`stdwrap`

diff --git a/Documentation/Functions/Stdwrap.rst b/Documentation/Functions/Stdwrap.rst
@@ -867,8 +867,6 @@ strftime
 formattedDate
 ~~~~~~~~~~~~~
 
-..  versionadded:: 12.3
-
 ..  confval:: formattedDate
     :name: stdwrap-formattedDate
     :type: :ref:`data-type-string`

diff --git a/Documentation/Functions/Typolink.rst b/Documentation/Functions/Typolink.rst
@@ -165,12 +165,7 @@ addQueryString
         query arguments are never added by default. This is the recommended
         behaviour.
 
-        ..  versionchanged:: 12.0
-            Before TYPO3 v12 this setting added all query parameters. To ensure
-            the previous behaviour use :typoscript:`untrusted`.
-
     :typoscript:`untrusted`
-        ..  versionadded:: 12.0
 
         Any given query parameters of the current request are added.
 

diff --git a/Documentation/TopLevelObjects/Config.rst b/Documentation/TopLevelObjects/Config.rst
@@ -484,8 +484,6 @@ Properties of 'config'
         :type: :ref:`data-type-boolean`
         :Default: `0`
 
-        ..  versionadded:: 12.1
-
         If this option is set, all links, reference to images or assets
         previously built with a relative or absolute path (for example,
         :file:`/fileadmin/my-pdf.pdf`) will be rendered as absolute URLs
@@ -922,8 +920,6 @@ Properties of 'config'
         :type: :ref:`data-type-boolean`
         :Default: 1
 
-        ..  versionadded:: 12.0
-
         The option can be used to specify whether the website title defined in
         the :ref:`site configuration <t3coreapi:sitehandling>` should be added
         to the page title (used for the :html:`<title>` tag, for example).
@@ -1002,8 +998,6 @@ Properties of 'config'
         :type: :ref:`data-type-string`
         :Example: :ref:`setup-config-typolinklinkaccessrestrictedpages`
 
-        ..  versionadded:: 12.3
-
         `typolinkLinkAccessRestrictedPages.ATagParams` Add custom attributes to
         the anchor tag.
 

diff --git a/Documentation/TopLevelObjects/Module.rst b/Documentation/TopLevelObjects/Module.rst
@@ -18,9 +18,9 @@ settings should be done globally and not changed on a per-page basis.
 Therefore they are usually done in the file
 :ref:`EXT:my_extension/ext_typoscript_setup.typoscript <t3coreapi:ext_typoscript_setup_typoscript>`.
 
-..  versionchanged:: 12.0
+..  note::
     All Core extensions, and in general all extensions
-    that switch to the :ref:`simplified backend templating <changelog:feature-96812>`
+    that switched to the :ref:`simplified backend templating <changelog:feature-96812>`
     no longer use the frontend TypoScript based override approach. This has been
     superseded by a general override strategy based on TSconfig:
     :ref:`templates <t3tsconfig:pagetemplates>`.
@@ -77,7 +77,7 @@ view.templateRootPaths
     :name: module-view-templateRootPaths
     :type: file path with :ref:`stdWrap <stdwrap>`
 
-    ..  versionchanged:: 12.0
+    ..  note::
         All Core extensions, and in general all extensions
         that switch to the :ref:`simplified backend templating <changelog:feature-96812>`
         no longer use the frontend TypoScript based override approach. This has been
@@ -115,7 +115,7 @@ view.partialRootPaths
     :name: module-view-partialRootPaths
     :type: file path with :ref:`stdWrap <stdwrap>`
 
-    ..  versionchanged:: 12.0
+    ..  note::
         All Core extensions, and in general all extensions
         that switch to the :ref:`simplified backend templating <changelog:feature-96812>`
         no longer use the frontend TypoScript based override approach. This has been