TYPO3 Major Upgrades

TYPO3

Description

A major TYPO3 upgrade involves three clearly defined phases: preparation before the upgrade, updating the Core via Composer, and completing follow-up tasks in the backend afterwards. Each phase contains specific steps that must be carried out in order to ensure a clean and stable result. The process applies to every major version jump and follows the same general pattern regardless of the versions involved.

Goals

• I know that a major upgrade is divided into pre-upgrade tasks, the Core update itself, and post-upgrade tasks.
• I know that before upgrading, all deprecation warnings from the current version must be resolved and all extensions must be checked for compatibility with the target version (see Deprecation Log).
• I know that a full backup of the database and all files must be created before starting the upgrade.
• I know that the Core is updated via Composer by adjusting the version constraints in composer.json and running composer update.
• I know that after the Core update, the Install Tool must be used to run database compare and apply any required schema changes.
• I know that the Upgrade Wizard in the Install Tool provides migration wizards that must be executed after a major upgrade to update existing data structures and configuration.
• I know that extension updates and custom code adjustments for removed or changed APIs are part of the post-upgrade phase.
• I know the modules “Scan Extension Files”, “Check TCA migrations”, “Check for broken extensions” and “Check TCA in ext_tables.php” and their purpose.
• I know that I can view the TYPO3 Core Changelogs to get information about changes in the TYPO3 Core.
• I know that I can find information about extensions for a TYPO3 version in the TYPO3 Extension Repository and packagist.org.
• I know: No backup, no sympathy!

Maintainer

Oliver Thiele Web Development Oliver Thiele