Commit 436461fb authored by Mathias Schreiber's avatar Mathias Schreiber Committed by Benni Mack
Browse files

[TASK] Update Documentation for release of TYPO3 CMS 7.3

Releases: master
Change-Id: Ib9cc9e07ada7a60cf6fc1bbc878c16ff83c5df27
Reviewed-on: http://review.typo3.org/40252


Reviewed-by: Benni Mack's avatarBenjamin Mack <benni@typo3.org>
Tested-by: Benni Mack's avatarBenjamin Mack <benni@typo3.org>
parent cc462e9d
......@@ -28,7 +28,7 @@ Migration
=========
Change the slot to use the ``\TYPO3\CMS\Lang\Service\TranslationService::postProcessMirrorUrl``
signal. If it's required to serve multiple TYPO3 installations, use the following code:
signal. If it is required to serve multiple TYPO3 versions, use the following code:
.. code-block:: php
......
......@@ -8,7 +8,7 @@ Description
The default (``renderMode="ul"``) rendering output of the ``FlashMessagesViewHelper`` has been changed.
By default the view helper rendered an unordered list, each list item containing one message.
This output has been adjusted and more markup is added.
This output has been adjusted and more markup has been added.
Impact
......@@ -21,13 +21,14 @@ Affected Installations
======================
Any template using the ``FlashMessagesViewHelper`` unless the attribute ``renderMode`` is set to "div".
Be aware, though, that the ``renderMode`` attribute is deprecated.
Be aware that the ``renderMode`` attribute has been deprecated.
Migration
=========
Add a custom rendering template for the flash messages, like outlined in the example, to obtain the same output as before.
Add a custom rendering template for the flash messages, like outlined in the example, to obtain the same output
as before.
.. code-block:: html
......
......@@ -20,16 +20,16 @@ TCA changes
-----------
* Keys `_PADDING`, `_VALIGN` and `DISTANCE` of `TCA['aTable']['columns']['aField']['config']['wizards']`
are removed and have no effect anymore.
have been removed and have no effect anymore.
* Key `TCA['aTable']['ctrl']['mainPalette']` is dropped and has no effect anymore.
* Key `TCA['aTable']['ctrl']['mainPalette']` has been dropped and has no effect anymore.
TSconfig changes
----------------
* Key `mod.web_layout.tt_content.fieldOrder` is dropped and has no effect anymore.
* Key `mod.web_layout.tt_content.fieldOrder` has been dropped and has no effect anymore.
* Key `TCEFORM.aTable.aField.linkTitleToSelf` is dropped and has no effect anymore.
* Key `TCEFORM.aTable.aField.linkTitleToSelf` has been dropped and has no effect anymore.
Code level
......@@ -37,30 +37,30 @@ Code level
Most methods and properties from FormEngine except the main entry methods like `getMainFields()` are
not available anymore. Classes like `InlineElement` are gone. New structures like a factory
for elements and container are introduced.
for elements and container have been introduced.
While not too many extensions in the wild hook or code with FormEngine, those that do will probably throw
fatal errors after upgrade. The hook `getSingleFieldClass` is removed altogether.
fatal errors after upgrade. The hook `getSingleFieldClass` has been removed altogether.
Changed user functions and hooks
--------------------------------
* TCA: If format of type none is set to user, the configured userFunc no longer gets an instance of FormEngine
as parent object, but an instance of NoneElement.
* TCA: If format of type `none` is set to `user`, the configured userFunc no longer gets an instance of `FormEngine`
as parent object, but an instance of `NoneElement``.
* TCA: Wizards configured as "userFunc" now receive a dummy FormEngine object with empty properties instead
* TCA: Wizards configured as `userFunc` now receive a dummy `FormEngine` object with empty properties instead
of the real instance.
* Hooks no longer get the key `form_type`. Use `type` instead.
* Hook `getSingleFieldClass` is dropped and no longer called.
* Hook `getSingleFieldClass` has been dropped and no longer called.
Breaking interface changes
--------------------------
* The type hint to `FormEngine` as `$pObj` had to be removed on the `DatabaseFileIconsHookInterface`.
This hook is no longer given an instance of FormEngine.
* The type hint to `FormEngine` as `$pObj` has been removed on the `DatabaseFileIconsHookInterface`.
This hook is no longer given an instance of `FormEngine`.
* Method `init()` of `InlineElementHookInterface` was removed. Classes that implement this interface will
* Method `init()` of `InlineElementHookInterface` has been removed. Classes that implement this interface will
no longer get `init()` called.
......@@ -68,17 +68,17 @@ Affected installations
======================
For most instances, the overall impact is rather low or they are not affected at all. Some very
rarely used TCA and TSconfig options are dropped, those will not harm. Instances are usually only affected
rarely used TCA and TSconfig options have been dropped, those will do no harm. Instances are usually only affected
if loaded extensions do fancy stuff with FormEngine with hooks or other related code.
TYPO3 CMS 7 installations with extensions using or hooking into FormEngine and its related classes are
likely to break. TCA elements of type user may break. Instances using these parts will quickly show
fatal errors at testing. It may help to search for `FormEngine` or `t3lib_tceForms` below `typo3conf/ext`
fatal errors at testing. It may help to search for `FormEngine` or `t3lib_tceForms` below the `typo3conf/ext`
directory to find affected instances.
Migration
=========
Adapt the extension code. The majority of methods was for internal core usage only, but still public. Please
Adapt the extension code. The majority of methods were for internal core usage only, but still public. Please
use the existing API to solve needs on FormEngine.
......@@ -11,13 +11,16 @@ The ``IdentityMap`` class and its usage has been removed from the Extbase persis
Impact
======
Upgraded installations will throw a ``ReflectionException``. Accessing the previously existing ``IdentityMap`` properties within ``DataMapper`` and ``Repository`` will now fail. Creating ``IdentityMap`` instances is not possible anymore.
Upgraded installations will throw a ``ReflectionException``. Accessing the previously existing ``IdentityMap``
properties within ``DataMapper`` and ``Repository`` will now fail. Creating ``IdentityMap`` instances is not possible
anymore.
Affected Installations
======================
All installations, especially extensions using the ``IdentityMap`` class directly or accessing the properties within ``DataMapper`` or ``Repository``.
All installations, especially extensions using the ``IdentityMap`` class directly or accessing the properties within
``DataMapper`` or ``Repository``.
Migration
......@@ -25,7 +28,8 @@ Migration
The Extbase reflection cache of existing installations needs to be cleared once.
Existing code can be migrated to the persistence ``Session`` class which provides a drop-in replacement for the ``IdentityMap``.
Existing code can be migrated to the persistence ``Session`` class which provides a drop-in replacement for the
``IdentityMap``.
Usage example
=============
......
......@@ -12,18 +12,18 @@ The openid form has been extracted and is now using the new API as well.
Impact
======
All former member variables of the ``LoginController`` class have been removed or made protected, together with some, now pointless, hooks
and their related classes.
All former member variables of the ``LoginController`` class have been removed or made protected, together with
some, now pointless, hooks and their related classes.
The deleted hooks are:
- $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['typo3/index.php']['loginScriptHook']
- $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['typo3/index.php']['loginFormHook']
- ``$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['typo3/index.php']['loginScriptHook']``
- ``$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['typo3/index.php']['loginFormHook']``
The removed class and its alias:
- TYPO3\CMS\Rsaauth\Hook\LoginFormHook
- tx_rsaauth_loginformhook
- ``TYPO3\CMS\Rsaauth\Hook\LoginFormHook``
- ``tx_rsaauth_loginformhook``
Affected Installations
......
......@@ -7,7 +7,7 @@ Description
The `RenderingContextAwareInterface` allowed objects to get the `RenderingContext` set while being
accessed from inside a Fluid template. This makes optimization of variable access in Fluid difficult
and seems to be an unused feature. Therefore it should be removed.
and seems to be an unused feature. Therefore it has been removed.
Impact
======
......
......@@ -33,7 +33,8 @@ of ``[BE][loginSecurityLevel]`` or ``[FE][loginSecurityLevel]``, will not work a
Affected Installations
======================
Any installation having set ``[BE][loginSecurityLevel]`` or ``[FE][loginSecurityLevel]`` to an empty string or to either of "superchallenged" or "challenged".
Any installation having set ``[BE][loginSecurityLevel]`` or ``[FE][loginSecurityLevel]`` to an empty string or to
either of "superchallenged" or "challenged".
Migration
......
......@@ -5,20 +5,26 @@ Breaking: #67027 - Removed FLOW-compatibility from PackageManager
Description
===========
The Package Manager has been simplified and trimmed down to fit the needs of the TYPO3 extensions and typical Composer packages. All shipped code backported from Flow was removed or refactored to be included in the TYPO3 Core natively. Loading classes are done with the Composer class loader or by the conventions of extension namings. All default Composer packages can still be included as usual, however the custom Flow-logic has been removed.
The Package Manager has been simplified and trimmed down to fit the needs of the TYPO3 extensions and typical
Composer packages. All shipped code backported from Flow was removed or refactored to be included in the TYPO3
Core natively. Loading classes are done with the Composer class loader or by the conventions of extension namings.
All default Composer packages can still be included as usual, however the custom Flow-logic has been removed.
Impact
======
It is not possible to add custom Package.php loaders into TYPO3 extensions anymore to be called during runtime. It is not possible to configure extensions with custom Classes/ directories and custom composer.json locations anymore.
There is no special handling for "typo3-flow" packages anymore. The typo3conf/PackageStates.php file now only contains the parts that are necessary for the TYPO3 system.
It is not possible to add custom Package.php loaders into TYPO3 extensions anymore to be called during runtime. It is
not possible to configure extensions with custom `Classes/` directories and custom composer.json locations anymore.
There is no special handling for "typo3-flow" packages anymore. The typo3conf/PackageStates.php file now only contains
the parts that are necessary for the TYPO3 system.
Affected Installations
======================
All installations using custom functionality of the PackageManager not in use with the TYPO3 Core, or installations trying to use Flow packages natively in the TYPO3 Core.
All installations using custom functionality of the PackageManager not in use with the TYPO3 Core, or installations
trying to use Flow packages natively in the TYPO3 Core.
Migration
......
......@@ -12,15 +12,18 @@ If the specified field is not present in the database result an ``InvalidArgumen
Impact
======
This change will affect only broken usages of ``DatabaseConnection::exec_SELECTgetRows()`` with an invalid last parameter.
This change will affect only broken usages of ``DatabaseConnection::exec_SELECTgetRows()`` with an invalid last
parameter.
It is very unlikely that existing code affected by this change, since using the method in a wrong way had the consequence that it only returned the last row from the result.
It is very unlikely that existing code affected by this change, since using the method in a wrong way had the
consequence that it only returned the last row from the result.
Affected Installations
======================
Any code using the ``DatabaseConnection::exec_SELECTgetRows()`` method with ``$uidIndexField`` being set to a field name not present in the queried result set.
Any code using the ``DatabaseConnection::exec_SELECTgetRows()`` method with ``$uidIndexField`` being set to a field
name not present in the queried result set.
Migration
......
......@@ -19,11 +19,13 @@ These class information files are located in the typo3temp/autoload/ directory a
if they do not exist.
Non-namespaced classes with Tx\_ naming convention like Tx_Extension_ClassName are only resolved through
the aforementioned class map, but not dynamically. This means that extension authors need to re-generate the class map files
when introducing new classes. Thus it is highly recommended to use a Classes folder with PSR-4 standard class files in there.
the aforementioned class map, but not dynamically. This means that extension authors need to re-generate the class map
files when introducing new classes. Thus it is highly recommended to use a Classes folder with PSR-4 standard class
files in there.
When installing TYPO3 with composer, it also means that all extensions need to bring their own composer.json file with class loading information,
or the class loading information of all extensions need to be specified in the root composer.json for class loading to work properly.
When installing TYPO3 with composer, it also means that all extensions need to bring their own composer.json file with
class loading information or the class loading information of all extensions need to be specified in the root
composer.json for class loading to work properly.
Affected Installations
......@@ -36,5 +38,16 @@ Migration
=========
No migration is needed during upgrade if TYPO3 is installed in the classic way.
If TYPO3 is installed in a distribution via composer, missing class loading information need to be provided in root composer.json
for all extensions which do not bring their own composer.json manifest.
If TYPO3 is installed in a distribution via composer, missing class loading information need to be provided in root
composer.json for all extensions which do not bring their own composer.json manifest.
.. code-block::
{
"autoload": {
"psr-4": {
"GeorgRinger\\News\\": "typo3conf/ext/news/Classes/",
"MyAwesomeNamespace\\IncrediExt\\": "typo3conf/ext/incredible_extension/Resources/PHP/Libraries/lib/"
}
}
}
......@@ -6,13 +6,13 @@ Breaking: #67229 - FormEngine related classses
Description
===========
With the further development of FormEngine, some minor changes on ``PHP`` level were applied:
With the further development of FormEngine, some minor changes on PHP level have been applied:
* Class ``TYPO3\CMS\T3editor\FormWizard`` is removed
* Class ``TYPO3\CMS\T3editor\FormWizard`` has been removed
* Class ``TYPO3\CMS\Rtehtmlarea\Controller\FrontendRteController`` is removed
* Class ``TYPO3\CMS\Rtehtmlarea\Controller\FrontendRteController`` has been removed
* Method signature of class ``TYPO3\CMS\Utility\BackendUtility`` method ``getSpecConfParts`` changed
* The method signature of class ``TYPO3\CMS\Utility\BackendUtility`` method ``getSpecConfParts`` has changed
Impact
......
......@@ -19,5 +19,5 @@ implement own ``__wakeup()`` methods. Those methods are no longer called.
Migration
=========
Move initialization code from ``__wakeup()`` to ``initializeObject()``. As bonus, dependency
injection was executed at this time already.
Move initialization code from ``__wakeup()`` to ``initializeObject()``. As a bonus, dependencies have been injection at
this point already.
......@@ -18,7 +18,7 @@ Using ``config.classFile`` option will throw a deprecation message.
Affected Installations
======================
Installations which use a userdefined DBAL database-handler.
Installations which use a user-defined DBAL database-handler.
Migration
......
......@@ -5,14 +5,15 @@ Deprecation: #63453 - Deprecate renderMode attribute of FlashMessagesViewHelper
Description
===========
Deprecated renderMode in favor of a flexible deferred rendering of flash messages in the Fluid template.
This means that flash messages should no longer contain HTML, but the HTML output can and should be adjusted in the Fluid template.
Deprecated ``renderMode`` in favor of a flexible deferred rendering of flash messages in the Fluid template.
This means that flash messages should no longer contain HTML, but the HTML output can and should be adjusted in the
Fluid template.
Impact
======
Using renderMode on FlashMessage output will throw a deprecation warning.
Using ``renderMode`` on FlashMessage output will throw a deprecation warning.
Affected Installations
......
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