TYPO3 Upgrades - An overview

The complexity of a TYPO3 upgrade depends on the number of major version steps. An upgrade from TYPO3 version 12.4 to TYPO3 version 13.4, for example, is less complex than an upgrade from TYPO3 version 8.7 to TYPO3 version 13.4. The more versions are skipped, the more extensive the necessary adjustments to extensions, templates and individual functions become.

You can easily see which TYPO3 version your project is currently using in the backend. You will find the version number at the top left below the name of your installation.

As part of the upgrade check, we also check the installation method. Is your website implemented as a Composer installation or a classic installation with symlinks? This information influences the approach.

You can easily check which method is used for your installation in the "Extensions" backend module.

To display the "Extensions" module, the authorizations for an administrator or system maintainer are required.

A blue info box labeled "Composer mode" above the extension list indicates that this is a Composer installation. Otherwise, the classic installation method with symlinks was used.

The templating method and the content rendering method of your TYPO3 website have a major influence on the upgrade process. Currently, Fluid and Fluid Styled Content are the standards. However, if your website is still based on the outdated content rendering method CSS Styled Content, the content elements must be migrated to Fluid Styled Content during the upgrade. The effort involved is minimal if no adjustments have been made to the standard elements. Otherwise, changes to the individual templates are necessary.

Since Fluid Styled Content uses different CSS classes than CSS Styled Content, we have to adapt the frontend CSS in this case to ensure that the display remains consistent.

In addition, some features of CSS Styled Content have not been adopted in Fluid Styled Content. For example, the "image effects" no longer exist, and certain database fields have been renamed, such as "section_frame" to "frame_class". Such changes must be taken into account, especially if adjustments have been made with TSConfig.

If you are still using subparts or markers in your templates, these must be converted to Fluid templates. The same applies if you are using old extensions such as templavoila, rlmp_tmplselector or automaketemplate. These extensions are no longer compatible and must be replaced.

To check the templating method

Log into the TYPO3 backend with admin access and switch to the "Template" module (from TYPO3 v12 "TypoScript"). Select the root page in the page tree (recognizable by the globe symbol) and open the "TypoScript Object Browser" (from TYPO3 v12 "Active TypoScript") in the top drop-down menu. Search for the "Page" object in the "Setup Root" section. If a "FLUIDTEMPLATE" is defined there, it is Fluid. However, if you find entries such as "workOnSubpart = DOCUMENT" or properties such as "marks" or "subparts", markers are still being used.

You can view the content rendering method in the "Template" module under "Info/Modify". There, click on "Edit the whole template record" and check which static templates are included under the "Includes" tab. An entry "Fluid Content Elements" means that Fluid Styled Content is used. CSS Styled Content" is the outdated method.

In the "Extensions" module, you can also check whether old templating extensions such as templavoila, rlmp_tmplselector or automaketemplate are installed. These should be replaced as part of the upgrade.

If you use additional TypoScript or TsConfig on your website, compatibility problems may occur after an upgrade. This may be because, for example, the syntax of conditions has changed or certain objects are no longer supported. In such cases, adjustments are necessary to ensure the functionality of your website.

Older TypoScript configurations in particular, which are based on outdated standards, should be checked in advance.

For the body text field of content elements, either HTMLArea or CKEditor is generally used in TYPO3. As of TYPO3 version 9, however, HTMLArea is no longer available and must be replaced by CKEditor. This change is often uncomplicated, but can be more complex with heavily customized configurations of HTMLArea.

How to find out which text editor you are using:

Log in to the TYPO3 backend with admin access and switch to the "Extensions" module. In the list there, you can see whether HTMLArea or CKEditor is installed. This will give you clarity as to whether a changeover is necessary during an upgrade.

The effort required for a TYPO3 upgrade depends largely on the extensions installed. While the TYPO3 core can usually be updated smoothly, the upgrade becomes more complex the more extensions are used.

Challenges with extensions

1. Unavailable extensions: Some extensions are not available for the target version and need to be replaced. This may require a new selection and configuration of new extensions or, if possible, the elimination of the affected functionality.

2. Individually developed extensions: For self-developed extensions that are not available in the TYPO3 Extension Repository (TER), a customization or a complete upgrade is necessary. This requires either the support of the original developer or a separate order.

How to check your extensions

Log into the TYPO3 backend with admin access and go to the "Extensions" module. There you will find a list of all installed extensions. Filter by "Local Extensions" ("Local") to display all third-party extensions that have also been installed from the TYPO3 Extension Repository or have been specially developed for your installation. You can check the availability in the TYPO3 Extension Repository (TER) at https://extensions.typo3.org. Search there for the respective extension key that is specified in the "Key" column. If an extension is not listed, it is an individually developed extension.

To ensure a clean and future-proof upgrade of your TYPO3 website, all template files should ideally be organized in a site package, similar to extensions. In older installations, however, these files are often located in the fileadmin directory.

Challenges with older storage locations

If your templates are located in the fileadmin directory, several steps are required:

1. Creating a site package: all template files must be transferred to a new site package.

2. Restructure files: Subdirectories must be organized and existing file paths must be adjusted in the configuration.

3. Make adjustments: Additional files may need to be created and existing file extensions adapted.

How to check the storage location of your template files:

Log into the TYPO3 backend as an administrator and switch to the "Template" module. Select the "TypoScript Object Browser" in the select box at the top. Enter the term fileadmin in the search field. All references to the fileadmin directory are displayed in the search result. If TypoScript or HTML files are located under these paths, a new site package is required.

Even if your website already uses Fluid as a templating method, adjustments may be necessary after an upgrade. Some ViewHelpers provided by extensions or their arguments are no longer available in newer TYPO3 versions and must be replaced by alternative solutions.

Challenges with Fluid templates

1. Outdated ViewHelpers: We check whether the ViewHelpers used are still compatible. If not, alternative solutions must be found.
2. Adapt template logic: Changes in newer TYPO3 versions can lead to the existing logic within templates having to be adapted. This often concerns changed arguments of ViewHelpers or new requirements for the structure of Fluid templates.

How to check your Fluid templates

Log in to the backend as an administrator and navigate to your template files (if they are located in the fileadmin directory), or use SFTP or SSH access if the template files are located in a site package in the typo3conf/ext/ directory to check the Fluid templates specifically for incompatibilities.

An upgrade of your TYPO3 website offers the opportunity to adapt your site to current standards in the areas of accessibility, search engine optimization (SEO) and data protection. We integrate these features for you as standard as part of an upgrade:

1. XML sitemaps: An up-to-date and complete sitemap makes it easier for search engines to crawl your website and improves indexing.

2. Extended SEO fields: More modern TYPO3 versions offer improved options for optimizing your metadata, such as titles, descriptions and open graph tags, to increase website visibility.

3. Cookie consent manager: If there is relevant content on your website, an opt-in mechanism for consenting to the use of data is essential for GDPR compliance. We integrate modern cookie consent tools for you.

Additional effort

These adjustments involve technical effort, as configurations have to be made, existing content adapted and new functions implemented. However, it is worth carrying out this work directly as part of an upgrade in order to keep your website future-proof and competitive.