Commit 6dddf4a1 authored by Mathias Schreiber's avatar Mathias Schreiber Committed by Christian Kuhn
Browse files

[DOCS] Proofread 8.1 docs

Resolves: #
Releases: master
Change-Id: I95f3737e1c78a606664f4d5e4043b6d4370a07f5
Reviewed-on: https://review.typo3.org/47970


Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
Reviewed-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
parent 211c3a7b
......@@ -54,9 +54,9 @@ Impact
Calling the mentioned classes above will result in a fatal PHP error.
Using the options in custom PHP code will result in unexpected behaviour as the options are non-existent and empty.
Using the options in custom PHP code will result in unexpected behavior as the options are non-existent and empty.
PHP code depending on the removed PEAR library "Http_Request2" will result in unexpected behaviour and possibly in a
Using PHP code that depends on the removed PEAR library "Http_Request2" will result in unexpected behaviour and possibly a
fatal PHP error.
......@@ -64,18 +64,18 @@ Affected Installations
======================
All 3rd party extensions calling the mentioned classes directly or using the configuration options directly, as well
as installations depending on the PEAR libary "Http_Request2".
as installations depending on the PEAR library "Http_Request2".
Migration
=========
For PHP code previously using the HttpRequest and Download classes a new object-oriented PSR-7-based approach is
For PHP code previously using the ``HttpRequest`` and ``Download`` classes a new object-oriented PSR-7-based approach is
introduced, see the Guzzle Feature integration documentation for more details. A new PHP class
``TYPO3\CMS\Core\Http\RequestFactory`` which generates PSR-7 compliant request objects, helps in simplifying the
``TYPO3\CMS\Core\Http\RequestFactory`` which generates PSR-7 compliant request objects helps in simplifying the
migration process.
All still necessary options are migrated to new options within ``$TYPO3_CONF_VARS[HTTP]`` when the install tool is run.
All still necessary options will be migrated to new options within ``$TYPO3_CONF_VARS[HTTP]`` when the install tool is run.
In special cases, the options ``$TYPO3_CONF_VARS[HTTP][ssl_verify_host]``, ``$TYPO3_CONF_VARS[HTTP][proxy_auth_scheme]``
and ``$TYPO3_CONF_VARS[HTTP][proxy_host]`` need to migrated manually to the newly available options.
......
......@@ -6,7 +6,7 @@ Description
===========
In order to make Indexed Search pi-based plugin PHP7 compatible, the ``SearchFormController::pi_list_browseresults()`` method has been renamed to ``SearchFormController::renderPagination()``.
Parameter types, order and count has been preserved. However the methods visibility has been changed to protected.
Parameter types, order and count have been preserved. However the methods visibility has been changed to protected.
Impact
......@@ -18,7 +18,7 @@ Call to old method name will result in fatal error "Call to undefined method".
Affected Installations
======================
Any installation of TYPO3 7.6 or TYPO3 8 where SearchFormController is overloaded (XCLASSed) and new class contains call to old method name and
Any installation of TYPO3 7.6 or TYPO3 8 where ``SearchFormController`` is overloaded (XCLASSed) and the new class contains a call to the old method name and
any code that called the public method from outside the class.
......
......@@ -11,7 +11,7 @@ If neither bodytext nor header were entered in the TextMedia element, the div el
Impact
======
The missing div could cause layout problems, if the layout and CSS depends on it.
The missing div could cause layout problems, if the layout and CSS depend on it.
Affected Installations
......
......@@ -5,7 +5,7 @@ Breaking: #75323 - Removed parameter entryPointPath from main applications
Description
===========
The entry point ``PHP`` classes for ``index.php``, ``typo3/index.php`` and so for forth (called "Application classes")
The entry point ``PHP`` classes for ``index.php``, ``typo3/index.php`` and so forth (called "Application classes")
now have a parameter not to define the path to the entry point but the number of subdirectories under the main
installation path, allowing to not specify the name of the path, but just the levels of subdirectories.
......@@ -16,7 +16,7 @@ Subsequently, the methods ``Bootstrap->baseSetup()``, ``Bootstrap->redirectToIns
Impact
======
Calling one of the methods above with a string as parameter instead of an integer the calculation for PATH_site
Calling one of the methods above with a string as parameter instead of an integer will fail because the calculation for PATH_site
which is the base for the whole installation will fail.
......
......@@ -7,8 +7,10 @@ Description
The Reference Index Updater Command Line command has been changed to use a Symfony Command.
To update the reference index on non-composer-mode installations is now called on the command line via
``typo3/sysext/core/bin/typo3 referenceindex:update``. To just check the reference index, the option ``-c``(alternatively the property "check" can be used) is used like this ``typo3/sysext/core/bin/typo3 referenceindex:update -c``
The command to update the reference index on non-composer-mode installations is now called on the command line via
``typo3/sysext/core/bin/typo3 referenceindex:update``.
To just check the reference index, the option ``-c`` (alternatively the property "check" can be used) is used like this ``typo3/sysext/core/bin/typo3 referenceindex:update -c``
For installations set up via composer, the typo3 CLI binary is available in the "bin/" directory directly inside the
project root.
......
......@@ -5,25 +5,25 @@ Breaking: #75349 - Move Indexed Search pi-based plugin to compatibility7
Description
===========
Indexed Search pi1 plugin (based on AbstractPlugin) has been moved to compatibility7 extension and will not be developed further. The compatibility7 extension will be moved to TER before the release of 8 LTS.
Extbase plugin (pi2) stays in Indexed Search as before.
Indexed Search pi1 plugin (based on AbstractPlugin) has been moved to EXT:compatibility7 and will not be developed further. EXT:compatibility7 will be moved to TER before the release of 8 LTS.
The Extbase plugin (pi2) stays in Indexed Search as before.
Impact
======
Installation of the compatibility7 extension is required to continue using pi1 plugin. In the longer run migration to Extbase plugin is required.
Installation of EXT:compatibility7 is required to continue using the pi1 plugin. In the longer run migrating to the Extbase plugin is required.
Affected Installations
======================
All installations using pi-based indexed search plugin.
All installations using the pi-based indexed search plugin.
Migration
=========
Installations using pi1 should migrate to Extbase plugin or install compatibility7 extension.
Installations using pi1 should migrate to the Extbase plugin or install EXT:compatibility7.
.. index:: php
......@@ -22,7 +22,7 @@ Impact
======
If the option was set previously to "1", the exception is not thrown but a redirect will now happen.
The same behaviour as the existing option "2".
The same behavior as the existing option "2".
Affected Installations
......
......@@ -5,8 +5,8 @@ Breaking: #75454 - TYPO3_db Constants removed
Description
===========
The PHP constants ``TYPO3_db``, ``TYPO3_db_username``, ``TYPO3_db_password`` and ``TYPO3_db_host`` have been
removed which were used when a TYPO3 initialized the database connection have been removed.
The PHP constants ``TYPO3_db``, ``TYPO3_db_username``, ``TYPO3_db_password`` and ``TYPO3_db_host``
which were used when TYPO3 initialized the database connection have been removed.
Impact
......
......@@ -13,16 +13,16 @@ Also the backend route ``wizard_backend_layout`` has been removed.
Impact
======
Extending or using the ``BackendLayoutWizardController`` will break your installation.
Extending or using the ``BackendLayoutWizardController`` will break installations.
Affected Installations
======================
An installation which uses an extension which make use of ``BackendLayoutWizardController``
Any installation which uses an extension which makes use of ``BackendLayoutWizardController``
Migration
=========
Use the renderType "belayoutwizard", which renders the backend layout wizard inline in FormEngine.
Use the renderType ``belayoutwizard``, which renders the backend layout wizard inline in FormEngine.
......@@ -6,7 +6,7 @@ Description
===========
When transforming HTML data from the Rich Text Editor to the database, the RteHtmlParser removed <p> tags from
lines where there were no attributes for the <p> tags, otherwise they were kept as <p> tags with
lines when there were no attributes for the <p> tags, otherwise they were kept as <p> tags with
their attributes.
The transformation now always keeps <p> tags within the content in order to minimize the transformation overhead
......@@ -16,7 +16,7 @@ between the RTE and the database.
Impact
======
Every time an RTE field is edited, the <p> are now stored inside the database when saving the content.
Every time an RTE field is edited, the <p> tags are now stored inside the database when saving the content.
Affected Installations
......
......@@ -17,9 +17,9 @@ The following methods have been removed from ``ContentObjectRenderer`` without s
The following TCA options have no effect anymore throughout the TYPO3 Core:
* $TCA[table][ctrl][fe_cruser_id]
* $TCA[table][ctrl][fe_crgroup_id]
* $TCA[table][ctrl][fe_admin_lock]
* $GLOBALS['TCA'][table]['ctrl']['fe_cruser_id']
* $GLOBALS['TCA'][table]['ctrl']['fe_crgroup_id']
* $GLOBALS['TCA'][table]['ctrl']['fe_admin_lock']
Impact
......
......@@ -13,7 +13,7 @@ The following public method has been removed: :php`\TYPO3\CMS\Impexp\Import::fix
Impact
======
Importing files into TYPO3 v8 that were created from a TYPO3 4.x installations will result in unexpected behaviour,
Importing files into TYPO3 v8 that were created from a TYPO3 4.x installations will result in unexpected behavior,
especially when dealing with files and relations.
Calling the PHP method above will result in a fatal PHP error.
......@@ -22,7 +22,7 @@ Calling the PHP method above will result in a fatal PHP error.
Affected Installations
======================
Any installation using the t3d import functionality for importing files that are created from a TYPO3 instance older
Any installation using the t3d import functionality for importing files that were created from a TYPO3 instance older
than TYPO3 6.0.0.
......
......@@ -6,15 +6,15 @@ Description
===========
Setting page TSConfig values ``PAGE_TSCONFIG_ID``, ``PAGE_TSCONFIG_IDLIST`` and
`` PAGE_TSCONFIG_STR`` for flex form fields globally has been deprecated, specific
`` PAGE_TSCONFIG_STR`` for flexform fields globally has been marked as deprecated, specific
fields must be set now.
Example for a now deprecated global TSConfig value:
``TCEFORM.tt_content.pi_flexform.PAGE_TSCONFIG_ID = 42``
This should now be restricted to specific fields of the flex from data structure, if for example
the flex form ``foreign_table_where`` of field ``settings.categories`` of a ``tt_content`` plugin`s
This should now be restricted to specific fields of the flexfrom data structure, if for example
the flexform ``foreign_table_where`` of field ``settings.categories`` of a ``tt_content`` plugin`s
data structure should be set, the new page TSConfig option should look like:
``TCEFORM.tt_content.pi_flexform.theDataStructure.theSheet.settings\.categories.PAGE_TSCONFIG_ID = 42``
......@@ -22,18 +22,20 @@ data structure should be set, the new page TSConfig option should look like:
Note that any dots within the field name must be escaped with ``\``, this is a typical
scenario for extbase.
Impact
======
This page TSConfig can not be set for section elements anymore: ``PAGE_TSCONFIG_ID``,
This pageTSConfig cannot be set for section elements anymore: ``PAGE_TSCONFIG_ID``,
``PAGE_TSCONFIG_IDLIST`` and ``PAGE_TSCONFIG_STR`` do not have any effect on repeatable
elements.
Affected Installations
======================
Installations that set ``PAGE_TSCONFIG_ID``, ``PAGE_TSCONFIG_IDLIST`` and ``PAGE_TSCONFIG_STR``
for flex form fields globally should be restricted to set those values for single elements.
for flexform fields globally should be restricted to set those values for single elements.
Migration
......
......@@ -7,15 +7,15 @@ Description
The color-picker is now available as dedicated render-type which will integrate
an inline color-picker widget based on bootstrap. Thus, the old wizard type
``colorbox`` is deprecated.
``colorbox`` has been marked as deprecated.
Impact
======
Using the TCA wizard type ``colorbox`` will trigger an internal deprecation
message. The possibility to pick the color from a custom image has been removed
without any substitution as well as the possibility to use color names like
Using the TCA wizard type ``colorbox`` will trigger a deprecation log entry.
The possibility to pick the color from a custom image has been removed
without substitution together with the possibility to use color names like
"red" or "white".
......
......@@ -5,7 +5,7 @@ Deprecation: #75327 - $TSFE->csConvObj and $TSFE->csConv()
Description
===========
The public property "csConvObj" and the public method "csConv()" inside the TypoScriptFrontendController PHP
The public property ``csConvObj`` and the public method ``csConv()`` inside the TypoScriptFrontendController PHP
class have been marked as deprecated.
......@@ -18,7 +18,7 @@ Calling ``$TSFE->csConv()`` will trigger a deprecation log entry.
Affected Installations
======================
Any TYPO3 installation which uses the property or the method directly above.
Any TYPO3 installation which uses the property or the method directly.
Migration
......
......@@ -29,6 +29,10 @@ Migration
Migrate to UriBuilder routes, which can be registered via Configuration/Backend/AjaxRoutes.php,
and can be linked to like this:
.. code-block:: php
/** @var \TYPO3\CMS\Backend\Routing\UriBuilder $uriBuilder */
$uriBuilder = GeneralUtility::makeInstance(\TYPO3\CMS\Backend\Routing\UriBuilder::class);
$path = $uriBuilder->buildUriFromRoute('ajax_myroute');
\ No newline at end of file
$path = $uriBuilder->buildUriFromRoute('ajax_myroute');
Keep in mind that the newly created Ajax routes need to implement PSR-7 as well.
\ No newline at end of file
......@@ -28,8 +28,8 @@ Use :php:`GeneralUtility::array2xml()` instead. The XML declaration must be writ
Example code:
.. code-block:: php
// Deprecated
$bodyText = GeneralUtility::array2xml_cs($array, 'phparray');
// Deprecated
$bodyText = GeneralUtility::array2xml_cs($array, 'phparray');
// Migrated
$bodyText = '<?xml version="1.0" encoding="utf-8" standalone="yes" ?>' . LF . GeneralUtility::array2xml($array, '', 0, 'phparray');
// Migrated
$bodyText = '<?xml version="1.0" encoding="utf-8" standalone="yes" ?>' . LF . GeneralUtility::array2xml($array, '', 0, 'phparray');
Supports Markdown
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