Mastering TYPO3 v13: The Essential Guide for Upgrades and Migrations

Published on : 28 Jan 2025

Sanjay Chauhan

Development

Mastering TYPO3 v13: The Essential Guide for Upgrades and Migrations

Curious to harness TYPO3 v13’s cutting-edge improvements? Our comprehensive upgrade guide unveils every must-know tweak—from crucial breakpoints to future-proof deprecations—ensuring your site smoothly enters the next-gen TYPO3 CMS era with confidence!

TYPO3 v13: The Essential Upgrade Guide

TYPO3 v13 delivers a powerful upgrade, modernizing the platform and removing legacy cruft. As with any major version jump, new coding standards, internal class changes, and restructured hooks will impact your projects. Below, we break down Breaking Changes (which require immediate code updates), Important Changes (which might affect behavior or dependencies), and Deprecations (available now but removed in v14).

Use this reference to streamline your migration to TYPO3 v13 and ensure a smooth path forward. Before we start, if you are interested in more about TYPO3 v13 features, Take a look at our TYPO3 feature series release as below.

Major Changes in TYPO3 CMS v13

These changes will break your site if not addressed before or during your TYPO3 v13 upgrade. Carefully review and fix any code references outlined below.

1. ExpressionBuilder Changes

The signature of the following methods has been modified.

ExpressionBuilder::literal(string $value) strictly requires a string.
ExpressionBuilder::trim() requires \Doctrine\DBAL\Platforms\TrimMode enum instead of integers.

// Before v13
$queryBuilder->expr()->comparison(
    $queryBuilder->expr()->trim($fieldName, 1), // integer usage
    ExpressionBuilder::EQ,
    $queryBuilder->createNamedParameter('', Connection::PARAM_STR)
);

// Before v13
$queryBuilder->expr()->comparison(
    $queryBuilder->expr()->trim($fieldName, 1), // integer usage
    ExpressionBuilder::EQ,
    $queryBuilder->createNamedParameter('', Connection::PARAM_STR)
);

// After v13
use Doctrine\DBAL\Platforms\TrimMode;
$queryBuilder->expr()->comparison(
    $queryBuilder->expr()->trim($fieldName, TrimMode::LEADING),
    ExpressionBuilder::EQ,
    $queryBuilder->createNamedParameter('', Connection::PARAM_STR)
);

// After v13
use Doctrine\DBAL\Platforms\TrimMode;
$queryBuilder->expr()->comparison(
    $queryBuilder->expr()->trim($fieldName, TrimMode::LEADING),
    ExpressionBuilder::EQ,
    $queryBuilder->createNamedParameter('', Connection::PARAM_STR)
);

2. QueryBuilder Changes

Removed methods: add(), getQueryPart(), getQueryParts(), resetQueryPart(), resetQueryParts(), execute(), getQueryParts(), setMaxResults() etc.
Use ->executeQuery() (SELECT) or ->executeStatement() (INSERT/UPDATE/DELETE).
(int)0 no longer means “unlimited” in setMaxResults(). Use null.

// Before v13
$queryBuilder->add('select', ['uid', 'title']);
$result = $queryBuilder->execute(); // was used for SELECT
$queryBuilder->setMaxResults(0); // unlimited

// Before v13
$queryBuilder->add('select', ['uid', 'title']);
$result = $queryBuilder->execute(); // was used for SELECT
$queryBuilder->setMaxResults(0); // unlimited

3. Convert LoginType to Native Backed Enum

\TYPO3\CMS\Core\Authentication\LoginType is now a native PHP enum.
Old constants LoginType::LOGIN, LoginType::LOGOUT etc. are gone; use ->value or tryFrom().

// Before v13
if ($loginType === \TYPO3\CMS\Core\Authentication\LoginType::LOGIN) {
    // ...
}

// Before v13
if ($loginType === \TYPO3\CMS\Core\Authentication\LoginType::LOGIN) {
    // ...
}

// After v13
use TYPO3\CMS\Core\Authentication\LoginType;

if (LoginType::tryFrom($value ?? '') === LoginType::LOGIN) {
    // login
}

// After v13
use TYPO3\CMS\Core\Authentication\LoginType;

if (LoginType::tryFrom($value ?? '') === LoginType::LOGIN) {
    // login
}

4. Page Doktype “Recycler” Removed

Doktype 255 for “Recycler” pages no longer exists.
Use the Recycler module for soft-deleting instead.

5. Mark PageTsBackendLayoutDataProvider as final

\TYPO3\CMS\Backend\View\BackendLayout\PageTsBackendLayoutDataProvider is final.
You can’t extend it anymore; implement a custom provider.

// Before v13
class MyProvider extends PageTsBackendLayoutDataProvider {
    // ...
}

// Before v13
class MyProvider extends PageTsBackendLayoutDataProvider {
    // ...
}

// After v13
class MyProvider implements c {
    // ...
}

// After v13
class MyProvider implements c {
    // ...
}

6. Fallback Removal for CKEditor removePlugins

String-based fallback for removePlugins in YAML is removed.
Must specify plugins as an array.

// Before v13
editor:
  config:
    removePlugins: image

// Before v13
editor:
  config:
    removePlugins: image

// After v13
editor:
  config:
    removePlugins:
      - image

// After v13
editor:
  config:
    removePlugins:
      - image

7. Declare Indexed Search as Content Type

EXT:indexed_search is recognized as a content element rather than a plugin.
An upgrade wizard helps migrate old plugin references to content types.

// Before v13
tt_content.indexed_search = COA

// Before v13
tt_content.indexed_search = COA

// After v13
Use the wizard “Migrate Indexed Search plugins to content elements.”
Handled as a standard CType in TCA.

// After v13
Use the wizard “Migrate Indexed Search plugins to content elements.”
Handled as a standard CType in TCA.

8. getAllPageNumbers() in PaginationInterface

getAllPageNumbers() has been removed/changed.
If you need page arrays, rely on SimplePagination, SlidingWindowPagination, or custom logic.

// Before v13
$pages = $pagination->getAllPageNumbers();

// Before v13
$pages = $pagination->getAllPageNumbers();

// After v13
This method is gone.
Use getFirstPageNumber(), getLastPageNumber(), or create your own iteration logic.

// After v13
This method is gone.
Use getFirstPageNumber(), getLastPageNumber(), or create your own iteration logic.

9. Continuous Array Keys in intExplode()

When removeEmptyEntries = true, GeneralUtility::intExplode() returns continuous numeric keys (no gaps).

// Before v13
GeneralUtility::intExplode(',', '1,,3', true);
// Result: [0 => 1, 2 => 3]

// Before v13
GeneralUtility::intExplode(',', '1,,3', true);
// Result: [0 => 1, 2 => 3]

// After v13
GeneralUtility::intExplode(',', '1,,3', true);
// Result: [0 => 1, 1 => 3]

// After v13
GeneralUtility::intExplode(',', '1,,3', true);
// Result: [0 => 1, 1 => 3]

10. Use BIGINT for Datetime TCA Fields

The TCA attribute 'type' => 'datetime' used to create table columns as signed integers by default, unless explicitly specified otherwise in ext_tables.sql or exempted (e.g., starttime, endtime, tstamp, crdate).
Avoid 2038 problem and allow larger timestamp ranges.

// Before v13
crdate INT(11) DEFAULT '0'

// Before v13
crdate INT(11) DEFAULT '0'

// After v13
crdate BIGINT(20) DEFAULT '0'

// After v13
crdate BIGINT(20) DEFAULT '0'

11. Removed ContentObject stdWrap Hook

The hook $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['stdWrap'] is removed.
Use PSR-14 events for manipulating stdWrap.

// Before v13
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['stdWrap'][] = 
   \Vendor\Extension\Hooks\StdWrapHook::class;

// Before v13
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['stdWrap'][] = 
   \Vendor\Extension\Hooks\StdWrapHook::class;

// After v13
Implement the relevant PSR-14 event.
Remove the old hook reference.

// After v13
Implement the relevant PSR-14 event.
Remove the old hook reference.

12. Removed Hook for Overriding Icon Overlay Identifier

Hook
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['TYPO3\CMS\Core\Imaging\IconFactory']['overrideIconOverlay'] is gone.
Replaced by
\TYPO3\CMS\Core\Imaging\Event\ModifyRecordOverlayIconIdentifierEvent.

// Before v13
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['TYPO3\CMS\Core\Imaging\IconFactory']['overrideIconOverlay'] =
    \Vendor\Extension\Hooks\IconOverlayHook::class;

// Before v13
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['TYPO3\CMS\Core\Imaging\IconFactory']['overrideIconOverlay'] =
    \Vendor\Extension\Hooks\IconOverlayHook::class;

// After v13
Use the new PSR-14 event approach.

// After v13
Use the new PSR-14 event approach.

13. Removed Hook for Manipulating getData Result

$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['getData'] is removed.
Migrate to \TYPO3\CMS\Frontend\ContentObject\Event\AfterGetDataResolvedEvent.

// Before v13
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['getData'][] =
    \Vendor\Extension\Hooks\GetDataHook::class;

// Before v13
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['getData'][] =
    \Vendor\Extension\Hooks\GetDataHook::class;

// After v13
Implement the new PSR-14 event.

// After v13
Implement the new PSR-14 event.

14. Removed Hook for Manipulating ContentObjectRenderer

$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['postInit'] is removed.
Use \TYPO3\CMS\Frontend\ContentObject\Event\AfterContentObjectRendererInitializedEvent.

// Before v13
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['postInit'][] =
    \Vendor\Extension\Hooks\MyHook::class;

// Before v13
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['postInit'][] =
    \Vendor\Extension\Hooks\MyHook::class;

// After v13
Implement the new PSR-14 event.

// After v13
Implement the new PSR-14 event.

15. Disable External Linktypes by Default (EXT:linkvalidator)

EXT:linkvalidator no longer checks external links by default.
You must explicitly enable them.

// Before v13
External link checks might be on by default.

// Before v13
External link checks might be on by default.

// After v13
mod.linkvalidator.linktypes = db,file,external

// After v13
mod.linkvalidator.linktypes = db,file,external

16. Removed TSFE->fe_user

$TSFE->fe_user property is removed.
Use the Context API or request attributes to access user data.

// Before v13
if ($GLOBALS['TSFE']->fe_user->user['username']) {
    // ...
}

// Before v13
if ($GLOBALS['TSFE']->fe_user->user['username']) {
    // ...
}

// After v13
Context API Example:
use TYPO3\CMS\Core\Context\Context;

public function __construct(
        private readonly Context $context,
    ) {}	


$username = $this->context->getPropertyFromAspect('frontend.user', 'username', '');

// After v13
Context API Example:
use TYPO3\CMS\Core\Context\Context;

public function __construct(
        private readonly Context $context,
    ) {}	


$username = $this->context->getPropertyFromAspect('frontend.user', 'username', '');

Extbase Request Example:

$frontendUser = $this->request->getAttribute('frontend.user');
$username = $frontendUser->user['username'] ?? '';

$frontendUser = $this->request->getAttribute('frontend.user');
$username = $frontendUser->user['username'] ?? '';

17. Use Strict Types in Extbase

Extbase controllers now enforce strict type declarations for properties and methods.
Overriding them incorrectly will cause errors.

// Before v13
class MyController extends ActionController
{
    public string $errorMethodName = 'myAction';
}

// Before v13
class MyController extends ActionController
{
    public string $errorMethodName = 'myAction';
}

// After v13
class MyController extends ActionController
{
    public function __construct()
    {
        $this->errorMethodName = 'myAction';
    }

    // All methods properly typed
}

// After v13
class MyController extends ActionController
{
    public function __construct()
    {
        $this->errorMethodName = 'myAction';
    }

    // All methods properly typed
}

18. Removed TypoScript Setting showForgotPasswordLink in ext:felogin

plugin.tx_felogin_pi1.showForgotPasswordLink is removed.
Use showForgotPassword instead.

// Before v13
plugin.tx_felogin_pi1.showForgotPasswordLink = 1

// Before v13
plugin.tx_felogin_pi1.showForgotPasswordLink = 1

// After v13
plugin.tx_felogin_pi1.showForgotPassword = 1

// After v13
plugin.tx_felogin_pi1.showForgotPassword = 1

19. Remove Items from New Content Element Wizard

The wizard is now automatically derived from TCA.
Instead of show := removeFromList(...), use removeItems := addToList(...).

// Before v13
mod.wizards.newContentElement.wizardItems.<group>.show := removeFromList(html)

// Before v13
mod.wizards.newContentElement.wizardItems.<group>.show := removeFromList(html)

// After v13
mod.wizards.newContentElement.wizardItems.<group>.removeItems := addToList(html)

// After v13
mod.wizards.newContentElement.wizardItems.<group>.removeItems := addToList(html)

Important Updates in TYPO3 version 13

These Important TYPO3 v13 changes might not break your code outright but can significantly impact behavior or dependencies. Make sure to address them for a smoother project experience.

A. Updated Dependency: Symfony 7

TYPO3 v13 requires Symfony 7 components.
If your extension depends on older Symfony versions, check for compatibility.

B. Updated Dependency: Doctrine DBAL 4

Doctrine DBAL upgraded to version 4.
Affects QueryBuilder method usage (some removed or changed).
Coordinates with the Breaking Changes for QueryBuilder and ExpressionBuilder.

C. Changed Default Value for twitter_card Field

The twitter_card default field value changed from “summary” to “summary_large_image.”
Impacts how pages are rendered in social previews if you rely on defaults.

D. Unused DB Fields from tt_content Removed

Some legacy columns in tt_content are now removed.
If your extension references them, you’ll have errors or missing data.

F. Database table cache_treelist removed

“cache_treelist” table is removed.
If you had references to it, remove them.

20+ Must Know TYPO3 CMS v13 Deprecations

These features or methods are still present in TYPO3 v13 but will be removed in v14. Update them now to future-proof your code!

ExtensionManagementUtility::addPageTSConfig()
DuplicationBehavior Class
AbstractFile::FILETYPE_* Constants
DataProviderContext Getters/Setters)
TypoScriptFrontendController and $GLOBALS['TSFE']
Fluid Standalone Methods
Table-Dependent Definition of columnsOnly
Namespaced Shorthand Validator Usage in Extbase
Custom Fluid Views & Extbase
renderStatic() for Fluid ViewHelpers
Instantiation of IconRegistry in ext_localconf.php
INCLUDE_TYPOSCRIPT Syntax
Plugin Content Element & SubTypes
@typo3/backend/wizard.js
Renamed Page Tree Navigation Component ID (
GeneralUtility::hmac()
Fluid Variables: true, false, null

In-Depth Deprecation Snippets

Below are quick highlights; see official docs for full details and migration steps.

1. ExtensionManagementUtility::addPageTSConfig()

Deprecated method; use Configuration/page.tsconfig for your Page TS.
Will be removed in v14.

2. DuplicationBehavior Class

Old class is deprecated; use \TYPO3\CMS\Core\Resource\Enum\DuplicationBehavior.

// Before
$behavior = \TYPO3\CMS\Core\Resource\DuplicationBehavior::RENAME;

// Before
$behavior = \TYPO3\CMS\Core\Resource\DuplicationBehavior::RENAME;

// After
$behavior = \TYPO3\CMS\Core\Resource\Enum\DuplicationBehavior::RENAME;

// After
$behavior = \TYPO3\CMS\Core\Resource\Enum\DuplicationBehavior::RENAME;

3. AbstractFile::FILETYPE_* Constants

Using \TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_* constants is now deprecated.

// Before v13
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_UNKNOWN	\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_TEXT	\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_IMAGE	\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_AUDIO	\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_VIDEO	\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_APPLICATION

// Before v13
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_UNKNOWN	\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_TEXT	\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_IMAGE	\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_AUDIO	\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_VIDEO	\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_APPLICATION

// After v13
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_UNKNOWN -> \TYPO3\CMS\Core\Resource\FileType::UNKNOWN->value
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_TEXT -> \TYPO3\CMS\Core\Resource\FileType::TEXT->value
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_IMAGE -> \TYPO3\CMS\Core\Resource\FileType::IMAGE->value
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_AUDIO -> \TYPO3\CMS\Core\Resource\FileType::AUDIO->value
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_VIDEO -> \TYPO3\CMS\Core\Resource\FileType::VIDEO->value
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_APPLICATION -> \TYPO3\CMS\Core\Resource\FileType::APPLICATION->value

// After v13
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_UNKNOWN -> \TYPO3\CMS\Core\Resource\FileType::UNKNOWN->value
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_TEXT -> \TYPO3\CMS\Core\Resource\FileType::TEXT->value
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_IMAGE -> \TYPO3\CMS\Core\Resource\FileType::IMAGE->value
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_AUDIO -> \TYPO3\CMS\Core\Resource\FileType::AUDIO->value
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_VIDEO -> \TYPO3\CMS\Core\Resource\FileType::VIDEO->value
\TYPO3\CMS\Core\Resource\AbstractFile::FILETYPE_APPLICATION -> \TYPO3\CMS\Core\Resource\FileType::APPLICATION->value

4. DataProviderContext Getters/Setters

In TYPO3 v13.4, the \TYPO3\CMS\Backend\View\BackendLayout\DataProviderContext class has been updated to use public constructor property promotion (PCPP). All setX() and getX() methods are now deprecated and will be removed in TYPO3 v14.0. The class will be declared readonly and enforce PCPP instantiation in v14.0. Additionally, it has been made final to ensure it remains unchangeable, and its constructor arguments will become non-optional in TYPO3 v14.0.

Use the properties instead of the setter, example:

// Before v13
$dataProviderContext = GeneralUtility::makeInstance(DataProviderContext::class);
$dataProviderContext
    ->setPageId($pageId)
    ->setData($parameters['row'])
    ->setTableName($parameters['table'])
    ->setFieldName($parameters['field'])
    ->setPageTsConfig($pageTsConfig);

// Before v13
$dataProviderContext = GeneralUtility::makeInstance(DataProviderContext::class);
$dataProviderContext
    ->setPageId($pageId)
    ->setData($parameters['row'])
    ->setTableName($parameters['table'])
    ->setFieldName($parameters['field'])
    ->setPageTsConfig($pageTsConfig);

// After v13
$dataProviderContext = new DataProviderContext(
    pageId: $pageId,
    tableName: $parameters['table'],
    fieldName: $parameters['field'],
    data: $parameters['row'],
    pageTsConfig: $pageTsConfig,
);

// After v13
$dataProviderContext = new DataProviderContext(
    pageId: $pageId,
    tableName: $parameters['table'],
    fieldName: $parameters['field'],
    data: $parameters['row'],
    pageTsConfig: $pageTsConfig,
);

- Use the properties instead of the getters, example:

// Before
$pageId = $dataProviderContext->getPageId()

// Before
$pageId = $dataProviderContext->getPageId()

// After
$pageId = $dataProviderContext->pageId

// After
$pageId = $dataProviderContext->pageId

5. TypoScriptFrontendController and $GLOBALS['TSFE']

The \TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController class and its global instance, $GLOBALS['TSFE'], are deprecated and scheduled for removal in TYPO3 v14.
Use request attributes or Context API.

// Before v13
$feUser = $GLOBALS['TSFE']->fe_user->user;

// Before v13
$feUser = $GLOBALS['TSFE']->fe_user->user;

// After  v13
use TYPO3\CMS\Core\Context\Context;

$feUser = GeneralUtility::makeInstance(Context::class)
	->getPropertyFromAspect('frontend.user', 'user');

// After  v13
use TYPO3\CMS\Core\Context\Context;

$feUser = GeneralUtility::makeInstance(Context::class)
	->getPropertyFromAspect('frontend.user', 'user');

6. Fluid Standalone Methods

Some methods like TYPO3Fluid\Fluid\Core\ViewHelper\AbstractTagBasedViewHelper->registerUniversalTagAttributes() and AbstractTagBasedViewHelper->registerTagAttribute() are deprecated.
Check Fluid docs for updated usage patterns.

7. Table-Dependent Definition of columnsOnly

When linking to the edit form it's possible to instruct the EditDocumentController to only render a subset of available fields for relevant records using the columnsOnly functionality, by adding the fields to be rendered as a comma-separated list.

The fields to be rendered must be provided as an array under the respective table name.

// Before v13

$urlParameters = [
    'edit' => [
        'pages' => [
            1 => 'edit',
        ],
    ],
    'columnsOnly' => 'title,slug'
    'returnUrl' => $request->getAttribute('normalizedParams')->getRequestUri(),
];

GeneralUtility::makeInstance(UriBuilder::class)->buildUriFromRoute('record_edit', $urlParameters);

// Before v13

$urlParameters = [
    'edit' => [
        'pages' => [
            1 => 'edit',
        ],
    ],
    'columnsOnly' => 'title,slug'
    'returnUrl' => $request->getAttribute('normalizedParams')->getRequestUri(),
];

GeneralUtility::makeInstance(UriBuilder::class)->buildUriFromRoute('record_edit', $urlParameters);

// After v13

$urlParameters = [
    'edit' => [
        'pages' => [
            1 => 'edit',
        ],
    ],
    'columnsOnly' => [
        'pages' => [
            'title',
            'slug'
        ]
    ],
    'returnUrl' => $request->getAttribute('normalizedParams')->getRequestUri(),
];

GeneralUtility::makeInstance(UriBuilder::class)->buildUriFromRoute('record_edit', $urlParameters);

// After v13

$urlParameters = [
    'edit' => [
        'pages' => [
            1 => 'edit',
        ],
    ],
    'columnsOnly' => [
        'pages' => [
            'title',
            'slug'
        ]
    ],
    'returnUrl' => $request->getAttribute('normalizedParams')->getRequestUri(),
];

GeneralUtility::makeInstance(UriBuilder::class)->buildUriFromRoute('record_edit', $urlParameters);

8. Namespaced Shorthand Validator Usage in Extbase

In Extbase, you can use namespaced shorthand notation to add validators to properties or arguments. For example:
- TYPO3.CMS.Extbase:NotEmpty maps to \TYPO3\CMS\Extbase\Validation\Validator\NotEmptyValidator.
- Vendor.Extension:Custom maps to \Vendor\MyExtension\Validation\Validator\CustomValidator.

// Before v13
/**
 * @Extbase\Validate("TYPO3.CMS.Extbase:NotEmpty")
 */
protected $myProperty1;

/**
 * @Extbase\Validate("Vendor.Extension:Custom")
 */
protected $myProperty2;

// Before v13
/**
 * @Extbase\Validate("TYPO3.CMS.Extbase:NotEmpty")
 */
protected $myProperty1;

/**
 * @Extbase\Validate("Vendor.Extension:Custom")
 */
protected $myProperty2;

// After v13
/**
 * @Extbase\Validate("NotEmpty")
 */
protected $myProperty1;

/**
 * @Extbase\Validate("Vendor\Extension\Validation\Validator\CustomValidator")
 */
protected $myProperty2;

Or

#[Extbase\Validate(['validator' => \TYPO3\CMS\Extbase\Validation\Validator\NotEmptyValidator::class])]
protected $myProperty1;

#[Extbase\Validate(['validator' => \Vendor\Extension\Validation\Validator\CustomValidator::class])]
protected $myProperty2;

// After v13
/**
 * @Extbase\Validate("NotEmpty")
 */
protected $myProperty1;

/**
 * @Extbase\Validate("Vendor\Extension\Validation\Validator\CustomValidator")
 */
protected $myProperty2;

Or

#[Extbase\Validate(['validator' => \TYPO3\CMS\Extbase\Validation\Validator\NotEmptyValidator::class])]
protected $myProperty1;

#[Extbase\Validate(['validator' => \Vendor\Extension\Validation\Validator\CustomValidator::class])]
protected $myProperty2;

9. Custom Fluid Views & Extbase

\TYPO3\CMS\Fluid\View\StandaloneView, TemplateView, etc., are deprecated.
Use \TYPO3\CMS\Core\View\ViewFactoryInterface instead.

10. renderStatic() for Fluid ViewHelpers

The use of renderStatic() in Fluid ViewHelpers is deprecated. Additionally, the traits \TYPO3Fluid\Fluid\Core\ViewHelper\Traits\CompileWithContentArgumentAndRenderStatic and \TYPO3Fluid\Fluid\Core\ViewHelper\Traits\CompileWithRenderStatic are also marked as deprecated.

// Before v13 
class MyViewHelper extends AbstractViewHelper
{
	use CompileWithRenderStatic;

	public static function renderStatic(array $arguments, \Closure $renderChildrenClosure, RenderingContextInterface $renderingContext): string
	{
	    	return $renderChildrenClosure();
	}
}

// Before v13 
class MyViewHelper extends AbstractViewHelper
{
	use CompileWithRenderStatic;

	public static function renderStatic(array $arguments, \Closure $renderChildrenClosure, RenderingContextInterface $renderingContext): string
	{
	    	return $renderChildrenClosure();
	}
}

// After v13 
class MyViewHelper extends AbstractViewHelper
{
	public function render(): string
	{
    	return $this->renderChildren();
	}
}

// After v13 
class MyViewHelper extends AbstractViewHelper
{
	public function render(): string
	{
    	return $this->renderChildren();
	}
}

11. Instantiation of IconRegistry in ext_localconf.php

Previously, extension authors registered icons manually by instantiating \TYPO3\CMS\Core\Imaging\IconRegistry in their ext_localconf.php files. This approach is now deprecated.

// Before v13
EXT:example/ext_localconf.php
<?php
$iconRegistry = \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance(\TYPO3\CMS\Core\Imaging\IconRegistry::class,);
$iconRegistry->registerIcon(
	'example',
	\TYPO3\CMS\Core\Imaging\IconProvider\SvgIconProvider::class,
	[
    	'source' => 'EXT:example/Resources/Public/Icons/example.svg'
	],
);

// Before v13
EXT:example/ext_localconf.php
<?php
$iconRegistry = \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance(\TYPO3\CMS\Core\Imaging\IconRegistry::class,);
$iconRegistry->registerIcon(
	'example',
	\TYPO3\CMS\Core\Imaging\IconProvider\SvgIconProvider::class,
	[
    	'source' => 'EXT:example/Resources/Public/Icons/example.svg'
	],
);

// After v13
EXT:example/Configuration/Icons.php
<?php
return [
	'example' => [
    		'provider' => \TYPO3\CMS\Core\Imaging\IconProvider\SvgIconProvider::class,
	    	'source' => 'EXT:example/Resources/Public/Icons/example.svg',
	],
];

// After v13
EXT:example/Configuration/Icons.php
<?php
return [
	'example' => [
    		'provider' => \TYPO3\CMS\Core\Imaging\IconProvider\SvgIconProvider::class,
	    	'source' => 'EXT:example/Resources/Public/Icons/example.svg',
	],
];

12. INCLUDE_TYPOSCRIPT Syntax

The old TypoScript syntax for importing external TypoScript files using <NCLUDE_TYPOSCRIPT: is deprecated in TYPO3 v13 and will be removed in v14.

// Before v13
<INCLUDE_TYPOSCRIPT: source="FILE:EXT:my_extension/Configuration/TypoScript/myMenu.typoscript">

// Before v13
<INCLUDE_TYPOSCRIPT: source="FILE:EXT:my_extension/Configuration/TypoScript/myMenu.typoscript">

// After v13
@import 'EXT:my_extension/Configuration/TypoScript/myMenu.typoscript'

// After v13
@import 'EXT:my_extension/Configuration/TypoScript/myMenu.typoscript'

13. Plugin Content Element & SubTypes

Check official documentation for new ways to register plugin-based content types.

14. Deprecate @typo3/backend/wizard.js

The @typo3/backend/wizard.js module, used for simple wizards in the backend, is deprecated. It will be replaced by the more feature-rich
@typo3/backend/multi-step-wizard.js, which offers improved functionality for creating multi-step wizards.

// Before v13
import Wizard from '@typo3/backend/wizard.js';
Wizard.addSlide(
 	'My-slide-identifier',
 	'Slide title',
 	'Content of my slide',
 	SeverityEnum.notice,
 	function () {
	     	// callback executed after displaying the slide
 	}
);

// Before v13
import Wizard from '@typo3/backend/wizard.js';
Wizard.addSlide(
 	'My-slide-identifier',
 	'Slide title',
 	'Content of my slide',
 	SeverityEnum.notice,
 	function () {
	     	// callback executed after displaying the slide
 	}
);

// After 
import MultiStepWizard from '@typo3/backend/multi-step-wizard.js';
MultiStepWizard.addSlide(
 	'my-slide-identifier',
 	'Slide title',
 	'Content of my slide',
 	SeverityEnum.notice,
	'My step',
 	function () {
	     	// callback executed after displaying the slide
 	}
);

// After 
import MultiStepWizard from '@typo3/backend/multi-step-wizard.js';
MultiStepWizard.addSlide(
 	'my-slide-identifier',
 	'Slide title',
 	'Content of my slide',
 	SeverityEnum.notice,
	'My step',
 	function () {
	     	// callback executed after displaying the slide
 	}
);

15. Renamed Page Tree Navigation Component ID

In TYPO3 v13, the page tree navigation component ID has been renamed from @typo3/backend/page-tree/page-tree-element to @typo3/backend/tree/page-tree-element. Using the old ID will trigger a PHP deprecation warning. To migrate, update the navigationComponent setting in your Modules.php configuration to the new name.

// Before v13 

'mymodule' => [
	'parent' => 'web',
	...
	'navigationComponent' => '@typo3/backend/page-tree/page-tree-element',
],

// Before v13 

'mymodule' => [
	'parent' => 'web',
	...
	'navigationComponent' => '@typo3/backend/page-tree/page-tree-element',
],

// After v13

'mymodule' => [
    'parent' => 'web',
    ...
    'navigationComponent' => '@typo3/backend/tree/page-tree-element',
],

// After v13

'mymodule' => [
    'parent' => 'web',
    ...
    'navigationComponent' => '@typo3/backend/tree/page-tree-element',
],

16. Deprecate GeneralUtility::hmac()

The method GeneralUtility::hmac() is deprecated in TYPO3 v13 and will be removed in v14. It should be replaced with the hmac() method from HashService. The new approach uses HashService either through dependency injection or by instantiating it with GeneralUtility::makeInstance().

// Before v13
$hmac = GeneralUtility::hmac('some-input', 'some-secret');

// Before v13
$hmac = GeneralUtility::hmac('some-input', 'some-secret');

// After v13 
use TYPO3\CMS\Core\Crypto\HashService;
$hashService = GeneralUtility::makeInstance(HashService::class);$hmac = $hashService->hmac('some-input', 'some-secret');

// After v13 
use TYPO3\CMS\Core\Crypto\HashService;
$hashService = GeneralUtility::makeInstance(HashService::class);$hmac = $hashService->hmac('some-input', 'some-secret');

17. Fluid Variables: true, false, null

In TYPO3 v13, Fluid no longer allows user-defined variables named true, false, or null due to Fluid v4's syntax. Using these names will cause an exception, and Fluid v2.15 will log a deprecation warning. To migrate, simply rename any conflicting variables.

// Before v13 
<f:variable name="true" value="someValue" />

// Before v13 
<f:variable name="true" value="someValue" />

// After v13 
<f:variable name="myTrue" value="someValue" />

// After v13 
<f:variable name="myTrue" value="someValue" />

Know TYPO3 Deprecation TYPO3 Deprecation Policy

Seeking TYPO3 Upgrade Partner?

Is your website still running on an older TYPO3 version? Looking for a reliable TYPO3 upgrade partner to improve your site's functionality? We are leading TYPO3 experts specializing in TYPO3 upgrade, our services improve performance, enhance security, and provide the latest features to ensure your website stays ahead of the competition.

Upgrade My Site

Wrap-up!

TYPO3 v13 is a giant leap forward, shedding outdated hooks, introducing modern coding standards, and updating core dependencies like Symfony and Doctrine DBAL. Here’s how to tackle your migration effectively:

1. Address Breaking Changes: Update code for changed method signatures, removed hooks, and TCA schema alterations.

2. Check Important Changes: Ensure your dependencies, default config changes, and removed DB fields don’t cause unexpected behavior.

3. Resolve Deprecations: Future-proof your project by removing or refactoring any deprecated usage—making your code ready for TYPO3 v14.

Recommended Steps

Run Upgrade Wizards: In the TYPO3 Install Tool, complete all recommended wizards.
Search Your Codebase: Look for references to removed hooks, old classes, or deprecated constants.Test Thoroughly: Double-check your front-end and back-end logic under v13.
Stay Updated: Watch official changelogs, Slack channels, or the TYPO3 community for any final clarifications or edge-case migrations.

By addressing these points now, your upgrade to TYPO3 v13 (and later v14) will be much smoother. Happy coding, and enjoy the exciting new features in TYPO3 v13!

If you found this guide helpful, share it with fellow TYPO3 developers and spread the word. Together, let’s make TYPO3 v13 the best yet!

Your One-Stop Solutions for Custom TYPO3 Development

A Decade of TYPO3 Industry Experience
350+ Successful TYPO3 Projects
87% Repeat TYPO3 Customers

TYPO3 Service

Sanjay Chauhan

CTO at T3Planet & NITSAN

Sanjay Chauhan, Co-Founder of NITSAN (Award winning TYPO3 agency) and Pioneer of T3Planet (first-ever TYPO3 Shop).

A true TYPO3 fanatic since 2010. I bring strong TYPO3 experience in building customer-business…

Mastering TYPO3 v13: The Essential Guide for Upgrades and Migrations

Recommended Steps

Your One-Stop Solutions for Custom TYPO3 Development

Sanjay Chauhan

5 Easy Steps to Start Your TYPO3 Blog - Download Now for Free!

Goodbye Manual, Hello Automated TYPO3 Installation

Post a Comment

You May Also Like

Goodbye Manual, Hello Automated TYPO3 Installation

How Is T3AI Built on TYPO3 Core Standards? (UI/UX and Code)

What Is Headless TYPO3? 10 Benefits and Best Practices