vivomedia/neos-9-upgrade

VIVOMEDIA.Neos9.Upgrade

Maintainers

Details

github.com/VIVOMEDIA/neos-9-upgrade

Source

Issues

Installs: 6

Dependents: 0

Suggesters: 0

Security: 0

Stars: 0

Watchers: 1

Forks: 1

Open Issues: 0

Type:neos-package

1.1.0 2025-05-02 12:06 UTC

Requires

MIT fdeb4e9b1164b792f3598d7bbe596870695afc08

This package is auto-updated.

Last update: 2025-06-02 12:20:52 UTC

README

This package provides some tooling for a better upgrade path from Neos 8.3 to Neos 9.0.

Install

composer require --dev vivomedia/neos-9-upgrade

Tools

Detach variants if parents are not the same

In Neos 9 it is currently not possible to create nodes with variants, where a variant has a different parent that other variants.

As a workaround you can detach the variants, which have not the same parent and create dedicated nodes.

So in this scenario:

      Node A (DE, EN)
        /         \
 Node B (DE)     Node C (EN)
        \         /
      Node D (DE, EN)

Node D(EN) becomes Node E(EN) and is not connected to Node D(DE) anymore.

      Node A (DE, EN)
        /         \
  Node B (DE)   Node C (EN)
      /             \
Node D (DE)       Node E (EN)

(!) If you need the connection between the nodes for automated translations, this will not work anymore after the migration.

(!) If this hits documents nodes, the removed connection will break any language switcher, which depends on this information to switch between languages and stay on the same document.

(!) If you use fallback dimensions, this might lead to duplicated content, as the fallback might shine through.

Run the migration

./flow node:migrate 20241217200614

Detach variants if Node Type is different in other dimensions

In Neos 9 it is currently not possible for Nodes with the same identifier to have different Node Types in different dimensions.

As a workaround you can detach the variants in the other dimensions and create dedicated nodes.

(!) If you need the connection between the nodes for automated translations, this will not work anymore after the migration.

(!) If this hits documents nodes, the removed connection will break any language switcher, which depends on this information to switch between languages and stay on the same document.

(!) If you use fallback dimensions, this might lead to duplicated content, as the fallback might shine through.

Run the migration

./flow node:migrate 20250403150125

Thanks to pkallert for providing this migration