Upgrade
This chapter lists, for each upgrade path, the steps for academic_base in the order to take them. Each step links the changelog entry with the detail.
| Installed version | Target version | Page |
|---|---|---|
| 2.3 | 2.4 | Upgrading from 2.3 to 2.4 |
Before you start
- Make a copy of the database and of
fileadmin/, so the upgrade can be repeated or rolled back. - Run the upgrade on a staging copy first, and on the live installation once the staging copy works.
- Upgrade all academic extensions of an installation together, in one deployment, to the same release.
- academic_base requires no other academic extension.
Installations outside these paths
The upgrade chapters of the academic extensions start at 2.3. An installation that starts elsewhere takes these steps first, then follows the page of its path in the upgrade chapter of each extension:
- TYPO3 v12
- Versions 2.3 and 2.4 run on TYPO3 12.4 from 12.4.22 on and on TYPO3 13.4. The path from 2.3 to 2.4 covers both. Update an older TYPO3 v12 to 12.4.22 or later first.
- A release older than 2.3
- Read the Breaking and Important entries of each minor version after the installed one, up to and including 2.3, in the changelog of each extension, and apply them in that order. Then follow the path from 2.3.
- An unreleased revision
- An installation that requires
dev-,2 2.orx- dev 2.runs a revision between two releases. It carries the version of the release it leads to,4. x- dev 2.in4. 0 ext_, and only part of its changes.emconf. php composer.names the installed commit. Follow the path from the last release before it, 2.3, and skip a step that does not apply.lock - A development constraint of an earlier version
2.,0. x- dev 2.and1. x- dev 2.were aliases of the branch3. x- dev main, which is3.now, so Composer no longer resolves them.0. x- dev 2.resolves to the branch2. x- dev 2., which receives no changes any more. Replace such a constraint, or2 2., withx- dev ^2.. Which steps apply follows from the installed revision, as described above.4