The path to a TYPO3 LTS version: Major releases, minor releases and patches
TYPO3 distinguishes between major releases and minor releases. The first number of a version number indicates the major version, e.g. TYPO3 13 LTS stands for version 13.4. Major releases bring significant new features compared to the previous major version. The second number indicates the minor version. Before the stable LTS version, a new major version goes through several development phases in which new functions are added and bugs are fixed. The versions prior to the LTS version are referred to as sprint releases – in the case of TYPO3 v13, these are versions 13.0 to 13.3.
The first stable minor version is the LTS version (Long Term Support), which is maintained in the long term and integrates all new features and bug fixes from the sprint releases. An upgrade is therefore only recommended with the release of the LTS version, as this offers official support and long-term stability.
After the release of the LTS version, only patches marked by the third number in the version number are released. These updates mainly contain bug fixes and security updates. For example, the current TYPO3 13.4.5 (as of February 2025) represents the fifth patch version of TYPO3 13 LTS. Since many patches are often released in the first few months after the release of an LTS version, it is advisable to wait some time before updating an existing instance until the initial bug fixes have been implemented.
Difference between updates, upgrades and version jumps
- An update refers to the transition from one patch version to the next, e.g. from 13.4.4 to 13.4.5.
- An upgrade is the change between major versions, e.g. from TYPO3 12 to TYPO3 13.
- A version jump occurs when several major versions are skipped, e.g. when upgrading from TYPO3 10 to TYPO3 13. This process is more complex, as several intermediate steps are necessary to ensure downward compatibility.
Let's take a closer look at the process of a TYPO3 v13 upgrade – with basic steps that are relevant for every TYPO3 upgrade.
Preparations for a TYPO3 Upgrade
Backup
Upgrades should never be performed directly on a live instance. The reason for this is simple: every upgrade harbors potential risks, and not all problems can be foreseen in advance. To be on the safe side, you should first create a copy of the existing instance on which the upgrade will be performed. In addition, it is advisable to have a complete backup ready so that the original version can be restored quickly in the event of unexpected errors or data loss. A complete backup includes:
- all files of the TYPO3 installation (backed up via FTP, SCP, rsync or another method)
- entire database exported as SQL file
During the entire upgrade process, a content freeze should be maintained so that no content has to be entered twice - once before and once after the upgrade. Detailed information on this and other important steps can also be found on the official TYPO3 website. Before working with the copy, you should check whether the copy works in the same way as the live instance.
Check system requirements
Before the actual upgrade begins, the system requirements for the new TYPO3 version should be checked. In addition to the PHP version, the database, the web server and other server components must also be compatible. For TYPO3 v13, for example, PHP 8.2 is a minimum requirement. All system requirements for TYPO3 13 can be found at get.typo3.org. If necessary, these components should be updated before the TYPO3 upgrade to avoid compatibility problems.
Check & update extensions
A key step before the upgrade is to check the installed extensions for compatibility with the new TYPO3 version.
1. Use Deprecation Log & Extension Scanner
The extension scanner in the Install Tool helps to detect outdated or incompatible functions. The deprecation log should be activated for a few days in order to identify and then resolve obsolete code.
2. Update or replace extensions
All active extensions should be updated to the highest version available for the current TYPO3 version. If an extension is not compatible with the new TYPO3 version, there are three options:
- Search for an alternative extension.
- If it is your own extension, adapt it.
- Check whether it works despite the incompatibility warning (sometimes extensions are compatible even though they are not marked as such).
3. Remove extensions that are no longer required
Extensions that are no longer used should be deleted before the upgrade to reduce the effort involved. Some extensions must be deactivated before the upgrade and only updated and reactivated afterwards.
4. Check PHP compatibility of the extensions
Some extensions are compatible with the new TYPO3 version, but not with the required PHP version. In such cases, either an older PHP version must be used or the extension concerned must be dispensed with.
Check reference index
The global reference index manages links between content elements and files. This index can be checked and updated in two ways: either via the command line (CLI) or via the DB check module (system modules). As the process can take a lot of time, especially for large websites with many pages and files, and does not need to be carried out regularly, the method via the command line is recommended. The DB check is an alternative, especially for small websites with few subpages and files.
The global reference index manages links between content elements, pages and files. To avoid inconsistencies in the database, the index should be updated before the upgrade.
- via command line (CLI): This method is recommended for large websites as it is faster and more reliable.
- via backend module DB check (system modules): An alternative for smaller TYPO3 instances with few pages and files.
Regular updating of the reference index ensures that all internal links are correct and potential errors are detected at an early stage.
Check changelog & breaking changes
This step is optional, but it is advantageous to prepare an upgrade carefully. The changelog of a TYPO3 version contains important information on new features, bug fixes and potential breaking changes. Breaking changes in particular should be checked carefully before the upgrade, as they can affect existing functionalities. The changelogs can be viewed via the Extension Scanner or read on the official TYPO3 website. In the Extension Scanner, changes can be filtered by category and processed like a to-do list. It is recommended to view at least the Breaking Changes and the Important category in order to be able to plan necessary adjustments in good time.
Convert global extensions to local extensions
With TYPO3 v12 the support for global extensions has been removed. If global extensions are still used, these must be converted to local extensions.
- Uninstalling the global extension via the Extensions backend module.
- Delete the files of the extension from the
typo3/ext/
directory. - Reinstallation of the extension from the TYPO3 Extension Repository (TER), whereby it is stored in
typo3conf/ext/
.
The switch to local extensions ensures that the extensions remain compatible with future TYPO3 versions and can continue to be maintained.
TYPO3 Core Upgrade
To upgrade your TYPO3 installation to version 13, you can obtain the TYPO3 sources either via Composer or directly from the official TYPO3 website. The preferred method is to use Composer as it allows for better management of dependencies and future updates. All information about the TYPO3 v13 Core Update can also be found on the official documentation for version 13.
Important notes (see also Preparations): Make sure that the servers used meet the requirements of the new TYPO3 version, especially with regard to the PHP and database versions. It is also important to note the breaking changes for TYPO3 v13, which may require adjustments to the extensions or the setup. Before every upgrade, a complete backup of the installation and database should be created to enable recovery in the event of problems. With TYPO3 v12 the package typo3/cms-recordlist
was integrated into typo3/cms-backend
. With TYPO3 v13 the package typo3/cms-t3editor
was integrated into typo3/cms-backend
. So if you have installed either package, remove them from your composer.json
file before upgrading.
Execute the command composer info typo3/*
to list all currently installed TYPO3 packages. Each package must be upgraded to a different major version during the upgrade. Make a note of the installed packages, especially optional extensions that may not be included by default in the new version. To upgrade a Composer package, run composer require
with the package name and version number. An upgrade command can be easily created with the Composer Helper Tools. Please note that dependency errors occur during a typical installation, which must be resolved.
After the Core Upgrade
After successfully upgrading your TYPO3 installation to version 13, some follow-up work is required to ensure that the system works properly. All necessary steps that need to be performed after the TYPO3 core update can also be found on the official TYPO3 website.
Run Upgrade Wizard
After the TYPO3 core update, the Upgrade Wizard should be run in the Install Tool. The Install Tool can be accessed via your-domain.de/typo3/install.php
. There, navigate to the Upgrade section and select the Upgrade Wizard. This takes you through several steps, starting with the creation of missing database tables and fields. It is recommended that you carefully check all the steps suggested by the wizard and carry them out accordingly. Some wizards concern optional functions that may not be relevant for the current installation; these can be skipped.
All updates can also be carried out simultaneously via the command line (CLI), which can be particularly advantageous for extensive installations.
Analyze and adapt database
After completing the Upgrade Wizard, the database structure should be analyzed and adapted to the requirements of the new TYPO3 version. To do this, go to the Maintenance section in the Install Tool and select Analyze database. The system displays a list of changes that should be made to bring the database up to date. Particular attention should be paid to tables or fields that are marked as obsolete. TYPO3 first renames such elements with the prefix zzz_deleted_*
before they are finally removed. It is important to carefully check whether these elements are no longer needed before deleting them.
Reset backend user settings
It may be useful to reset the backend user settings to avoid possible incompatibilities after the upgrade. This can be particularly helpful if users have made individual settings that are no longer compatible with the new version. The option Reset user settings can be found in the Install Tool under Maintenance. Personal user settings may be lost in the process.
Empty caches and remove temporary files
After the upgrade, it is essential to clear all caches to ensure that no outdated data is used. In the backend, go to Admin tools > Maintenance and click on Empty cache. Temporary files should also be removed. In the same module, you will find the option Remove temporary assets, which allows you to delete temporary files that are no longer required. This ensures that the system works with the current data and prevents possible conflicts caused by old files.
Update language packs
After the upgrade, the language packs should be updated to ensure that all backend texts are available in the desired language. In the Install Tool under Maintenance you will find the Manage language packs section. The installed languages should be updated there to add missing translations and ensure that the backend can be used as usual.
By carefully carrying out this follow-up work, you can ensure that the TYPO3 installation runs stably and efficiently after the upgrade.
Comments