Upgrade Instructions 2.1 → 2.2
By using composer, you can update an existing installation to a specific version, without having to create a new project.
See the release notes for a list of breaking changes.
For further information on what changed please take a look at the release notes and the changelog.
As always, before doing substantial changes, make sure you create a backup of the database and files!
# Update the core package dependencies
composer require --no-update "typo3/neos:~2.2.0"
composer require --no-update "typo3/neos-nodetypes:~2.2.0"
# Update optional package dependencies (if installed)
composer remove --no-update "typo3/neosdemotypo3org"
composer require --no-update "neos/demo:~2.2.0"
composer require --no-update "typo3/neos-kickstarter:~2.2.0"
# New optional packages
composer require --no-update "neos/redirecthandler-neosadapter:~1.0"
composer require --no-update "neos/redirecthandler-databasestorage:~1.0"
If you have development packages in your composer manifest, update them to match as well:
# Update development packages (if installed)
composer require --no-update --dev "typo3/buildessentials:3.2.x-dev"
composer require --no-update --dev "phpunit/phpunit:~4.8 || ~5.2.0"
Now do the actual update:
# Update the packages
# Flush the caches
./flow flow:cache:flush --force
# Ensure you have correct database charset/collation to prevent issues with foreign key constraints
# Run code migrations (all or specific ones)
# Run database migrations
# Publish resources
You may have some legacy dependencies and configuration entries in your composer manifest. Feel free to check if the following is needed in your setup:
# Remove the following line from composer.json (if present)
# Remove unneeded dependencies
composer remove --no-update "typo3/flow"
composer remove --no-update "doctrine/migrations"
# Remove deprecated packages
composer remove --no-update "typo3-ci/typo3flow"
If you run into trouble with Neos content or resources, the following may help:
# If you experience issues with pages not working, try
# If you experience issues with resources, thumbnail or assets, try