Open mhsdesign opened 11 months ago
For current 9.0 projects without a homepage the same steps have to be applied. Otherwise this error will appear:
After updating to the latest neos dev commit you can add
Vendor.Site:MyHomePage:
superTypes:
Neos.Neos:Site: true
to your DEDICATED homepage like we did in the neos demo: https://github.com/neos/Neos.Demo/pull/182
@kitsunet wrote about neos/neos-development-collection#4563
Currently the legacy migration would fail in attempt to migrate such site directly:
In this issue i want to document our further discussions.
Anke and Bernhard agreed with me that in order to upgrade your Neos 8 page needs to have a distinct nodetype for the homepage. This is a fair assumption to make as this is currently good practice. With neos 9 we will enforce this behavior.
For projects without a distinct site nodeType we want to document the steps one has to take to achieve this:
Vendor.Site:MyHomePage
and extend your previous page nodetype.After completing these steps, you can upgrade the codebase to Neos 9 and add the
Neos.Neos:Site
as supertype to your homepage node before running the escr legacy importer.