Translations
Info
All page names need to be in English.
en da  de  fr  it  ja  km  nl  ru  zh

TYPO3.CMS/Releases/7.6/Deprecation

From TYPO3Wiki
Jump to: navigation, search

Contents

Deprecation: #51482 - Script-based modules

Description

Pseudo-modules that are registered via ExtensionManagementUtility::addModulePath() and modules that are registered via ExtensionManagementUtility::addModule() using the fourth parameter as a custom script-path have been marked as deprecated.

The method ExtensionManagementUtility::addModulePath() itself has been marked as deprecated.

Impact

All existing modules which are not registered via Routing will trigger a deprecation entry on registration of the module and when calling the module directly.

Affected Installations

All third-party extensions registering a wizard, module or route without using routeTarget or Routes.php, which have been introduced with TYPO3 CMS 7.

Migration

Use Configuration/Backend/Routes.php (as documented here) to register wizards and use ExtensionManagementUtility::addModule() when registering a routePath option in the fifth parameter to use the proper PSR-7 compatible way of registering and calling modules. Make sure to use UriBuilder and BackendUtility::getModuleUrl() to link to these modules instead of hard-linking to the script names.

Deprecation: #60712 - DocumentTemplate->getDynamicTabMenu()

Description

Methods TYPO3\CMS\Backend\Template\DocumentTemplate::getDynamicTabMenu() and TYPO3\CMS\Backend\Template\DocumentTemplate::getDynTabMenuId() have been marked as deprecated.

Affected Installations

Instances with custom backend modules that use these methods.

Migration

Use TYPO3\CMS\Backend\Utility\ModuleTemplate::getDynamicTabMenu() instead.

Deprecation: #65728 - DocumentTemplate->issueCommand()

Description

Method TYPO3\CMS\Backend\Template\DocumentTemplate::issueCommand() has been marked as deprecated.

Affected Installations

Instances with custom backend modules that use this method.

Migration

Use TYPO3\CMS\Backend\Utility\BackendUtility::getLinkToDataHandlerAction() instead.

Deprecation: #69369 - Use property text instead of data

Description

The FORM elements TEXTAREA and OPTION currently use "data" as property name to define default "values" which are used as human readable "labels" inside the specific tag. Furthermore, the TEXTBLOCK element uses the "content" property to define custom text. All other FORM elements use "value". Since "data" implies the possibility to use computed values, this patch deprecates "data" and adds a new property called "text".

Impact

Using the property "data" will trigger a deprecation log entry.

Affected Installations

Any TYPO3 installation using TEXTAREA, OPTION and TEXTBLOCK elements which use the property "data".

Migration

Remove usage of the "data" property and use "text" instead. Opening a specific form with the form wizard and storing the form again will also migrate from "data" to "text".

Deprecation: #69822 - Deprecate TCA settings of select fields

Description

Using the TCA field type select without specifying a valid renderType has been marked as deprecated.

Additionally the usage of renderMode for select fields has been marked as deprecated.

These renderType settings are available:

Key
renderType
Datatype
string
Description
This setting specifies how the select field should be displayed. Available options are:
  • selectSingle - Normal select field for selecting a single value.
  • selectSingleBox - Normal select field for selecting multiple values.
  • selectCheckBox - List of checkboxes for selecting muliple values.
  • selectMultipleSideBySide - Two select fields, items can be selected from the right field, selected items are displayed in the left select.
  • selectTree - A tree for selecting hierarchical data.
Scope
Display

'renderType' => 'selectMultipleSideBySide', 'renderType' => 'selectCheckBox', 'renderType' => 'selectSingle', 'renderType' => 'selectSingleBox', 'renderType' => 'selectTree',

note

If a field has no renderType set but maxitems is set, the migration will set renderType to selectSingle in case of maxitems is <= 1 otherwise renderType is set to selectMultipleSideBySide

Impact

The old TCA settings can still be used. A migration handles the update of the settings.

Affected Installations

All installations with extensions that configure TCA select fields in the old format.

Migration

Extension authors need to add the correct renderType setting to their select field definitions.

Deprecation: #69877 - Use ModuleTemplate API for ext:filelist

Description

Method getButtonsAndOtherMarkers of class \TYPO3\CMS\Filelist\FileList has been marked as deprecated.

Impact

The method should not be used any longer and will be removed with TYPO3 CMS 8.

Affected Installations

All third party extensions using the mentioned method.

Migration

Use the ModuleTemplate API instead.

Deprecation: #70052 - TCA Display condition EXT LOADED

Description

In TCA the EXT:anExtension:LOADED display condition has been marked as deprecated.

Affected Installations

Extensions that use LOADED display conditions. Those can be located by searching for LOADED in the backend module Configuration TCA section, example match from rtehtmlarea:

'static_lang_isocode' => array(
    'displayCond' => 'EXT:static_info_tables:LOADED:true',
    'config' => ...
    ...
),

Migration

Do not use any longer. TCA works additive, so the extension that is referenced in EXT:LOADED:extensionName should instead add columns definition instead of the referring extension defining the TCA conditional. In the example above, the column definition of static_lang_isocode was removed from extension rtehtmlarea and moved to extension static_info_tables, adding the field in an Configuration/TCA/Overrides file to the affected table. To ensure the load order of extensions is correct, static_info_tables could set a suggest dependency rtehtmlarea.

Deprecation: #70138 - Flex form language handling

Description

TCA flex fields had an own language handling that allowed to store field localization within the flex data itself and not within the usual database driven overlay records. This was mainly introduced for TemplaVoila and usually only used in this context.

The whole flex form specific language handling has been moved from core extensions to extension compatibility6 and will not be delivered with TYPO3 CMS 7 LTS anymore.

The following flex XML data structure keys have been marked as deprecated and are supported by compatiblity6 only:

  • <meta><langDisable>
  • <meta><langChildren>
  • <meta><currentLangId>

The following PageTSConfig options have been dropped and are ignored if compatibility6 is not loaded:

  • TCEFORM.[tableName].[field].[dataStructureKey].langDisable
  • TCEFORM.[tableName].[field].[dataStructureKey].langChildren

The following UserTSConfig options have been dropped and are ignored if compatibility6 is not loaded:

  • options.checkPageLanguageOverlay

The following LocalConfiguration value has been marked as deprecated, will be removed by the install tool and is set by compatibility6 to TRUE:

  • $GLOBALS['TYPO3_CONF_VARS']['BE']['flexFormXMLincludeDiffBase']

The following method has been marked as deprecated and is cloned by compatibility6 in an XCLASS:

  • TYPO3\CMS\Core\Configaration\FlexForm\FlexFormTools->getAvailableLanguages()

The following property has been marked as deprecated:

  • TYPO3\CMS\Core\DataHandling\DataHandler->clear_flexFormData_vDEFbase

Impact

If this feature is needed, the compatibility6 extension must be loaded to keep compatibility with older versions after upgrading from TYPO3 CMS 6.2. If the extension is not loaded, flex form fields can no longer be localized on flex data level.

Affected Installations

All multi language installations that use flex form with meta field langDisable not set to 1 in their data structure definition and that make active use of the flex localization feature. This is the case if records with flex form fields show flex forms multiple times with different language flags.

Migration

Load extension compatibility6 for a compatibility layer in TYPO3 CMS 7, or migrate affected features to use the record based localization feature. The flex field based language handling will most likely vanish with TYPO3 CMS 8 altogether. In case the feature is needed for a longer time the code from compatibility6 could be used as a kick start for an implementation within an own extension.

In case compatibility6 is loaded, some core content elements may start showing flex field language overlays since the langDisable meta definition has been removed from their data structure XML. This can be suppressed with this PageTSConfig snippet:

TCEFORM.tt_content.pi_flexform.table.langDisable = 1
TCEFORM.tt_content.pi_flexform.login.langDisable = 1
TCEFORM.tt_content.pi_flexform.media.langDisable = 1

Deprecation: #70477 - Deprecate SpriteIcon classes

Description

The following classes have been marked as deprecated.

\TYPO3\CMS\Backend\Sprite\AbstractSpriteHandler
\TYPO3\CMS\Backend\Sprite\SimpleSpriteHandler
\TYPO3\CMS\Backend\Sprite\SpriteBuildingHandler

Impact

Any usage of these classes will trigger a deprecation log entry.

Affected Installations

Extensions that use these PHP classes.

Migration

Use the IconRegistry to register icons.

Deprecation: #70494 - DocumentTemplate->wrapClickMenuOnIcon()

Description

Method TYPO3\CMS\Backend\Template\DocumentTemplate::wrapClickMenuOnIcon() has been marked as deprecated.

Affected Installations

Instances with custom backend modules that use this method.

Migration

Use TYPO3\CMS\Backend\Utility\BackendUtility::wrapClickMenuOnIcon() instead.

Deprecation: #70514 - dynamicConfigFile is deprecated

Description

The TCA configuration dynamicConfigFile within the ctrl section of a table has been marked as deprecated and must not be used any longer.

Impact

Using dynamicConfigFile within the ctrl section of a table will trigger a deprecation log entry.

Migration

The setting is typically used in ext_tables.php files of extensions. The table configuration (TCA) must be moved to an own file in Configuration/TCA/<table_name>.php. The dynamicConfigFile setting isn't needed anymore since the whole TCA array definition is in this file.

Furthermore, any other TCA manipulation of third party tables must be moved to Configuration/TCA/Overrides and no TCA setting must remain in ext_tables.php. This is highly encouraged since TYPO3 CMS 6.2 already for performance reasons. If this change is not applied to extensions, extension compatibility6 must be loaded or further migration may not be applied to this portion of TCA leading to all sorts of possible issues.

Deprecation: #71153 - DocumentTemplate->spacer()

Description

Method TYPO3\CMS\Backend\Template\DocumentTemplate::spacer() has been marked as deprecated.

Affected Installations

Instances with custom backend modules that use this method.

Migration

Add the needed margin as HTML / CSS.

Deprecation: #71249 - Deprecate render method of FlashMessage class

Description

Method TYPO3\CMS\Core\Messaging\FlashMessage::render() has been marked as deprecated.

Affected Installations

Instances with custom backend modules that use this method.

Migration

Use custom render code, the <f:flashMessage /> ViewHelper or the ModuleTemplate for backend modules to render FlashMessages. It is suggested not to include HTML in flash messages. Flash messages should be short notifications on user interactions. If you need more elaborate or persistent messages, use <f:be.infobox /> view helper or HTML similar to that.