Essential Preparations for the TYPO3 v13 Upgrade

Upgrading to TYPO3 v13 LTS involves more than just a simple update; it impacts extensions, custom code, and backend workflows. Misunderstanding it as a minor update can lead to complications. The TYPO3 v13 Upgrade Checklist offers essential pre-upgrade steps to help agencies, freelancers, and teams manage the transition smoothly and minimize risks.


Who Should Use This Checklist?

Ideal for:

  • Agencies and teams managing multiple client sites.

  • Freelancers managing TYPO3 installations.

  • In-house teams handling long-term TYPO3 projects.

When to Delay the Upgrade

Avoid upgrading if:

  • Extensions are no longer supported.

  • Your system lacks proper documentation.

  • A major system redesign is planned soon.


Key Changes in TYPO3 v13

TYPO3 v13 introduces several important changes compared to v12:

  • Removes outdated APIs and tightens extension compatibility.

  • Requires more stringent checks for extensions and configurations.

  • Focuses on stricter backend and template settings.

  • Highlights configuration errors previously ignored in earlier versions.

These changes mean more effort is required for a successful upgrade.


Preparation Steps

1. Take Inventory

Before starting the upgrade, gather the following information:

  • Current TYPO3 and patch versions.

  • The PHP version in use and the version needed for v13.

  • Differences between your local, staging, and production environments.

This baseline data helps you track progress and avoid unexpected issues.

2. Review Extensions

Check each extension you use:

  • Confirm compatibility with TYPO3 v13.

  • Ensure that the extension is actively maintained.

  • Look for deprecated API usage in custom extensions.

Extensions that aren’t supported or maintained will cause problems after the upgrade.

3. Assess Custom Code

Review custom code for:

  • Outdated patterns in site packages.

  • Deprecated functions and methods.

  • Decide whether to update, replace, or remove custom features.

Updating or removing deprecated code early saves time during the upgrade.

4. Clean Up Configuration

TYPO3 v13 has stricter configuration rules. Address any issues by:

  • Removing obsolete TypoScript and configuration settings.

  • Cleaning up backend layouts and FormEngine overrides.

  • Resolving environment-specific configuration mismatches.

A clean configuration ensures fewer errors during the upgrade.


Planning Your Upgrade

Upgrade Environment

Never upgrade directly on your live production system:

  • Set up a separate environment that mirrors the live setup.

  • Include all components like the database, PHP, and filesystem.

  • Have a rollback plan in case things go wrong.

Scope and Prioritization

Not all parts of your system need to be upgraded immediately:

  • High-value, low-effort tasks: update and keep.

  • High-value, high-effort tasks: consider refactoring.

  • Low-value, high-effort tasks: remove if possible.

  • Low-value, low-effort tasks: consider deferring.

Focus on the most critical updates first.


Frontend, Templates, and UI

TYPO3 v13 affects templates and frontend rendering:

  • Old Fluid ViewHelpers and templates may break.

  • Ensure custom rendering code is compatible with v13.

  • Check for rendering issues during content testing.

Testing these components early helps avoid frontend problems after the upgrade.


Backend and Editor Workflow Testing

After the upgrade, test the backend thoroughly:

  • Test login, content editing, publishing, and translation processes.

  • Look for workflow issues even if there are no error messages.

  • Check roles and permissions, as v13 has clearer definitions.


Common Upgrade Mistakes

Avoid these common pitfalls:

  • Relying on generic documentation without reviewing your system’s specifics.

  • Ignoring extension dependencies.

  • Skipping editorial acceptance testing.

  • Not documenting upgrade decisions for future reference.


Final Preparations

Before starting the upgrade, ensure:

  • Custom extensions built before TYPO3 v12 are still in use.

  • Extensions from the TYPO3 Extension Repository (TER) are maintained.

  • TypoScript and backend overrides are well-documented.

  • Editor workflows are tested regularly.

  • Past upgrades didn’t fail or require a rollback.

These steps ensure your upgrade is more predictable and easier to manage.


Conclusion

Upgrading to TYPO3 v13 requires careful preparation and a clear plan. By addressing custom code, reviewing extensions, and testing thoroughly, you can ensure a smooth and successful transition to the new version.

Comments

Popular posts from this blog

What is TYPO3? Ultimate CMS Solution

Adding CAPTCHA to TYPO3: A Comprehensive Setup Guide

Making Web Accessibility with TYPO3