Upgrade Instructions 8.3 → 9.0

The page linked below describes a migration from Neos 8.3 to 9.0. 

Depending on the amount of PHP code dealing with nodes in your code, the migration will require additional effort.

Make sure to read this first, then come back here as needed!

To ensure the smoothest possible upgrade path, we offer a migration for use with Rector. 

The Rector migration is applied to your custom packages and rewrites the PHP source code, Fusion and YAML configurations to Neos 9 accordingly.

The rector migration should take care of most code changes. 

Have a look at the different pages below to see an overview of the different parts that have changed. 

Due to the change of the Content Repository implementation, a number of signals have been removed in Neos 9. Below you will find a list of all removed signals.

With the changes in the Content Repository there were some small changes to the fusion syntax. All changes should also be covered by the rector migration.

Node migrations have also undergone significant changes. In addition to structural modifications to the migration file, new functionalities have been introduced, reflecting updates to the content repository.

Depending on how extensive the PHP Node API was used, the changes in the code have to be extensive. 

One of the most obvious changes in the new Content Repository configuration is the changes to the dimensions. Next to that, there are also some minor changes and features that have been introduced in our Node Type Configuration. 

The feature to enable or disable nodes based on time has been moved into a dedicated package neos/timeable-node-visibility. This allows to decide on a project basis, if this feature is used. Install the package before data migration to ensure all timings get migrated too.