Commit b3187510 authored by Lina Wolf's avatar Lina Wolf Committed by Christian Kuhn
Browse files

[BUGFIX] Fix sphinx warnings in previous changelog entries

Fixes Layout problems: Malformed lists, malformed
headlines, non-working links to documentation or
other changelogs.
Directive `:ts:` and `.. code-block:: ts` is only
used for typescript, exchanged it into `:typoscript:`
for typoscript examples.

Resolves: #94534
Releases: master, 10.4, 9.5
Change-Id: I61e3c5910d6a5bc97f1ec887ce5b2c1e6d59a2db
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69922

Tested-by: Simon Gilli's avatarSimon Gilli <typo3@gilbertsoft.org>
Tested-by: core-ci's avatarcore-ci <typo3@b13.com>
Tested-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Simon Gilli's avatarSimon Gilli <typo3@gilbertsoft.org>
Reviewed-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
parent bf8c6585
.. include:: ../../Includes.txt
===========================================================================================
============================================================================================
Feature: #84250 - Separately enable / disable "Add media by URL" and "Select & upload files"
===========================================================================================
============================================================================================
See :issue:`84250`
......@@ -11,8 +11,8 @@ Description
A new appearance property "fileByUrlAllowed" is used to separately enable / disable the buttons "Add media by URL" and "Select & upload files".
* :php:`fileUploadAllowed = false` now only hides the button "Select & upload files".
* :php:`fileByUrlAllowed = false` now hides the button "Add media by URL".
* :php:`fileUploadAllowed = false` now only hides the button "Select & upload files".
* :php:`fileByUrlAllowed = false` now hides the button "Add media by URL".
If "elementBrowserType" is set to "file" both values are true by default.
......
......@@ -14,8 +14,8 @@ This makes it easier to check if the correct context is provided.
Output example:
.. code-block:: plain
.. code-block:: none
TYPO3 CMS 10.1.0-dev (Application Context: Development/Docker)
TYPO3 CMS 10.1.0-dev (Application Context: Development/Docker)
.. index:: CLI, ext:core
......@@ -14,7 +14,7 @@ on the edit icon for a broken link in order to edit the record directly.
If the record was edited, the list of broken links may no longer be up to date.
There are now 2 possibilities, depending on how :ref:`actionAfterEditRecord <actionAfterEditRecord>`
There are now 2 possibilities, depending on how :php:`actionAfterEditRecord`
is configured:
recheck (default):
......
......@@ -19,7 +19,7 @@ Examples
Match the current workspace id:
.. code-block:: ts
.. code-block:: typoscript
[workspace.workspaceId === 3]
# Current workspace id equals: 3
......@@ -27,7 +27,7 @@ Match the current workspace id:
Match against current workspace state:
.. code-block:: ts
.. code-block:: typoscript
[workspace.isLive]
# Current workspace is live
......
......@@ -21,18 +21,18 @@ Example
An example usage could look like this:
.. code-block:: ts
.. code-block:: typoscript
hideDefaultLanguageOfPage = TEXT
hideDefaultLanguageOfPage {
value = 0
value {
override = 1
override.if {
bitAnd.field = l18n_cfg
value = 1
}
value = 0
value {
override = 1
override.if {
bitAnd.field = l18n_cfg
value = 1
}
}
}
.. index:: ext:frontend, TypoScript
......@@ -15,10 +15,10 @@ AssetCollector is a concept to allow custom CSS/JS code, inline or external, to
times in e.g. a Fluid template (via :html:`<f:asset.script>` or :html:`<f:asset.css>` ViewHelpers) but only rendered once
in the output.
The :php:`priority` flag (default: :php:`false`) controls where the asset is included:
The :php:`priority` flag (default: :php:`false`) controls where the asset is included:
- JavaScript will be output inside :html:`<head>` (:php:`priority`=true) or at the bottom of the :html:`<body>` tag (:php:`priority`=false)
- CSS will always be output inside :html:`<head>`, yet grouped by :php:`priority`.
* JavaScript will be output inside :html:`<head>` (:php:`priority=true`) or at the bottom of the :html:`<body>` tag (:php:`priority=false`)
* CSS will always be output inside :html:`<head>`, yet grouped by :javascript:`priority`.
By including assets per-component, it can leverage the adoption of HTTP/2 multiplexing which removes the necessity of having all CSS/JavaScript
concatenated into one file.
......
......@@ -12,7 +12,7 @@ Description
JavaScript events in custom User Settings Configuration options shall
not be placed as inline JavaScript anymore, but utilize a dedicated
JavaScript module to handle custom events
(see :ref:`Important #91132 <changelog-Important-91132-AvoidJavaScriptInUserSettingsConfigurationOptions>`)
(see :doc:`Important-91132-AvoidJavaScriptInUserSettingsConfigurationOptions`)
This new PSR-14 event is introduced:
......@@ -75,6 +75,6 @@ A listener using mentioned PSR-14 event could look like the following.
Related
=======
- :ref:`changelog-Important-91132-AvoidJavaScriptInUserSettingsConfigurationOptions`
- :doc:`Important-91132-AvoidJavaScriptInUserSettingsConfigurationOptions`
.. index:: PHP-API, ext:core
......@@ -21,7 +21,7 @@ This step is advised to reduce the amount of inline JavaScript code towards
better support for Content-Security-Policy headers.
Applications having custom changes in :php:`$GLOBALS['TYPO3_USER_SETTINGS']`
and using mentioned options `onClick*` or ``confirmData.jsCodeAfterOk`.
and using mentioned options `onClick*` or `confirmData.jsCodeAfterOk`.
The following example show a potential migration path to avoid inline JavaScript.
......
......@@ -2,7 +2,7 @@
=======================================================
Important: #93331 - Description of SelectCheckBox items
========================================================
=======================================================
See :issue:`93331`
......
......@@ -30,22 +30,22 @@ An example configuration in the :file:`config/sites/<site-name>/config.yml`:
settings:
categoryPid: 658
  styles:
    content:
     loginform:
        pid: 23
styles:
content:
loginform:
pid: 23
This will make these constants available in the template and in page TSconfig:
* :ts:`{$categoryPid}`
* :ts:`{$styles.content.loginform.pid}`
* :typoscript:`{$categoryPid}`
* :typoscript:`{$styles.content.loginform.pid}`
The newly introduced constants for page TSconfig can be used just like constants
in TypoScript.
In page TSconfig this can be used like this:
.. code-block:: ts
.. code-block:: typoscript
# store tx_ext_data records on the given storage page by default (e.g. through IRRE)
TCAdefaults.tx_ext_data.pid = {$categoryPid}
......
......@@ -38,41 +38,41 @@ the functionality. Instead, all session properties are placed inside the
The following public properties within :php:`AbstractUserAuthentication` and
its subclasses have been removed:
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->id`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->hash_length`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->sessionTimeout`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->gc_time`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->gc_probability`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->newSessionID`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->id`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->hash_length`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->sessionTimeout`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->gc_time`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->gc_probability`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->newSessionID`
The following public methods within :php:`AbstractUserAuthentication` and its
subclasses have been removed:
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->getNewSessionRecord()`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->getSessionId()`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->isExistingSessionRecord()`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->getNewSessionRecord()`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->getSessionId()`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->isExistingSessionRecord()`
The following public property within :php:`AbstractUserAuthentication` has
changed their visibility to :php:`protected`:
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->lifetime`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->lifetime`
The following public methods within :php:`AbstractUserAuthentication` and its
subclasses have changed their return type:
* :php:`TYPO3\CMS\Frontend\Authentication\FrontendUserAuthentication->createUserSession()`
now returns :php:`TYPO3\CMS\Core\Session\UserSession` and the first parameter
:php:`$tempuser` is now type-hinted :php:`array`.
* :php:`TYPO3\CMS\Frontend\Authentication\FrontendUserAuthentication->createUserSession()`
now returns :php:`TYPO3\CMS\Core\Session\UserSession` and the first parameter
:php:`$tempuser` is now type-hinted :php:`array`.
The following public properties within :php:`FrontendUserAuthentication` have
been removed:
* :php:`TYPO3\CMS\Frontend\Authentication\FrontendUserAuthentication->sesData_change`
* :php:`TYPO3\CMS\Frontend\Authentication\FrontendUserAuthentication->sesData_change`
The following database fields have been removed:
* :sql:`be_sessions.ses_backuserid`
* :sql:`fe_sessions.ses_anonymous`
* :sql:`be_sessions.ses_backuserid`
* :sql:`fe_sessions.ses_anonymous`
Impact
......@@ -148,7 +148,7 @@ If a session is anonymous can furthermore be checked using
Related
=======
- :ref:`changelog-Deprecation-93023-ReworkedSessionHandling`
- :ref:`changelog-Feature-93023-IntroduceUserSessionAndUserSessionManager`
- :ref:`changelog-Deprecation-93023-ReworkedSessionHandling`
- :ref:`changelog-Feature-93023-IntroduceUserSessionAndUserSessionManager`
.. index:: PHP-API, FullyScanned, ext:core
......@@ -18,8 +18,8 @@ out of the user authentication classes.
Therefore some properties and methods within :php:`AbstractUserAuthentication`
and its subclasses have been marked as deprecated:
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->createSessionId()`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->fetchUserSession()`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->createSessionId()`
* :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->fetchUserSession()`
Impact
......@@ -63,7 +63,8 @@ access this information from an user authentication object, call
Related
=======
- :ref:`changelog-Breaking-93023-ReworkedSessionHandling`
- :ref:`changelog-Feature-93023-IntroduceUserSessionAndUserSessionManager`
* :ref:`changelog-Breaking-93023-ReworkedSessionHandling`
* :ref:`changelog-Feature-93023-IntroduceUserSessionAndUserSessionManager`
.. index:: PHP-API, FullyScanned, ext:core
......@@ -18,7 +18,7 @@ syntax now allows the LLL prefix for the use of language labels.
Example
=======
.. code-block:: ts
.. code-block:: typoscript
options.bookmarkGroups.2 = LLL:EXT:sitepackage/Resources/Private/Language/locallang_be.xlf:bookmarkGroups.2
......
......@@ -37,7 +37,7 @@ Migration
Use the new :js:`TYPO3/CMS/T3editor/Element/CodeMirrorElement` module and adapt
your markup to read:
.. block:: html
.. code-block:: html
<typo3-t3editor-codemirror mode="..." addons="[..]" options="{..}">
<textarea name="foo">..</textarea>
......
......@@ -29,7 +29,7 @@ changes ever since - had several downsides:
* The database field :sql:`be_users.lang` was not really needed
* Administrators did not see available language packs when changing the language
* Administrators could only change an editor's preferred language by
switching to the user (:pn:`Switch User Mode`).
switching to the user (:guilabel:`Switch User Mode`).
* Administrators could not filter / sort editors to see what languages the
users had chosen
* Fetching the user's preferred language always meant to fetch the whole
......
......@@ -15,15 +15,15 @@ according functionality has been moved to the legacy extension EXT:compatibility
The following TypoScript option has been marked for deprecation:
.. code-block:: ts
.. code-block:: typoscript
config.xhtml_cleaning
config.xhtml_cleaning
The following PHP method has been marked for deprecation:
.. code-block:: php
TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::doXHTML_cleaning()
TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::doXHTML_cleaning()
Impact
======
......@@ -34,7 +34,8 @@ The content output of the TYPO3 frontend is not cleaned anymore unless EXT:compa
Affected installations
======================
Any installation having the TypoScript option `config.xhtml_cleaning` set will have different behaviour in the
Any installation having the TypoScript option :typoscript:`config.xhtml_cleaning`
set will have different behaviour in the
frontend rendering.
Migration
......
......@@ -12,7 +12,7 @@ Description
It was possible to retrieve the local path of a FAL file via TypoScript
.. code-block:: ts
.. code-block:: typoscript
a = TEXT
a.value.data = file:current:localPath
......
......@@ -17,19 +17,19 @@ The following PHP methods within PageRenderer have been removed:
.. code-block:: php
$pageRenderer->setSvgPath()
$pageRenderer->getSvgPath()
$pageRenderer->loadSvg()
$pageRenderer->enableSvgDebug()
$pageRenderer->svgForceFlash()
$pageRenderer->setSvgPath()
$pageRenderer->getSvgPath()
$pageRenderer->loadSvg()
$pageRenderer->enableSvgDebug()
$pageRenderer->svgForceFlash()
The following TypoScript options are removed:
.. code-block:: ts
.. code-block:: typoscript
page.javascriptLibs.SVG
page.javascriptLibs.SVG.debug
page.javascriptLibs.SVG.forceFlash
page.javascriptLibs.SVG
page.javascriptLibs.SVG.debug
page.javascriptLibs.SVG.forceFlash
Impact
......
......@@ -16,16 +16,16 @@ the legacy extension EXT:compatibility6.
The following TypoScript option has been marked for deprecation:
.. code-block:: ts
.. code-block:: typoscript
config.prefixLocalAnchors
config.prefixLocalAnchors
The following PHP methods have been marked for deprecation:
.. code-block:: php
TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::prefixLocalAnchorsWithScript()
TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::doLocalAnchorFix()
TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::prefixLocalAnchorsWithScript()
TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::doLocalAnchorFix()
Impact
......
......@@ -98,7 +98,7 @@ Migration
If you want to use the JumpURL features you need to install the jumpurl extension. Your configuration should
work as before.
Please note that the configuration of the :ref:`filelink <t3tsref:filelink>` TypoScript function has changed.
Please note that the configuration of the :ref:`filelink <t3tsref:typolink-resource_references>` TypoScript function has changed.
Passing the :code:`jumpurl` parameter in the configuration has been marked as deprecated and will be removed in future versions.
You can now pass arbitrary configuration options for the typolink call that is used to generate
......@@ -106,12 +106,12 @@ the file link in the :code:`typolinkConfiguration` parameter:
.. code-block:: typoscript
lib.myfilelink = TEXT
lib.myfilelink.value = fileadmin/myfile.txt
lib.myfilelink.filelink {
typolinkConfiguration.jumpurl = 1
typolinkConfiguration.jumpurl.secure = 1
}
lib.myfilelink = TEXT
lib.myfilelink.value = fileadmin/myfile.txt
lib.myfilelink.filelink {
typolinkConfiguration.jumpurl = 1
typolinkConfiguration.jumpurl.secure = 1
}
.. index:: PHP-API, ext:jumpurl, TypoScript, Frontend
\ No newline at end of file
.. index:: PHP-API, ext:jumpurl, TypoScript, Frontend
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment