Support the documentation
This documentation was written by volunteers. Please help support our effort:
Upgrade Instructions 3.1 → 3.2
By using composer, you can update an existing installation to a specific version, without having to create a new project.
Before doing substantial changes, make sure you create a backup of the database and files!
cd /installation-root/ # Update the core package dependencies composer require --no-update "neos/neos:~3.2.0" composer require --no-update "neos/nodetypes:~3.2.0" # Update optional package dependencies (if installed) composer require --no-update "neos/demo:~3.2.0" composer require --no-update "neos/site-kickstarter:~3.2.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 "neos/buildessentials:4.2.x-dev"
Now do the actual update:
# Update the packages composer update # Flush the caches ./flow flow:cache:flush --force # Run code migrations (as needed for any packages that need to be migrated) ./flow flow:core:migrate --package-key … # Run database migrations ./flow doctrine:migrate # Publish resources ./flow resource:publish
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) "minimum-stability": "dev", # Remove unneeded dependencies composer remove --no-update "neos/flow" composer remove --no-update "doctrine/migrations"
If you run into trouble with Neos content or resources, the following may help:
# If you experience issues with pages not working, try ./flow node:repair # If you experience issues with resources, thumbnail or assets, try ./flow resource:clean ./flow media:clearthumbnails