Task #52020
clean up Node Structure between TYPO3 Neos and TYPO3.Neos.NodeTypes
| Status: | Accepted | Start date: | 2013-09-16 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Sebastian Kurfuerst | % Done: | 0% |
|
| Category: | Content Repository | Spent time: | - | |
| Target version: | 1.0 beta 1 |
Description
As discussed on 11.09. with the team, we found that some node types resided in TYPO3.Neos.NodeTypes, and others in TYPO3.Neos -- making it hard to understand for the implementor.
During the meeting, we came up with the following rules:
- TYPO3.Neos should work without TYPO3.Neos.NodeTypes
- all node types which TYPO3.Neos depend on (i.e. which are hardcoded in the source code somewhere) should be in TYPO3.Neos, all others in TYPO3.Neos.NodeTypes.
- All node types in TYPO3.Neos should be either abstract (meant to be extended) or final (not allowed to be extended). This means the average user does not have to deal with these node types.
As a result, this means the following node-type-changes:
- Page is migrated from TYPO3.Neos to TYPO3.Neos.NodeTypes
- Plugin is marked abstract, but stays in Neos
- Shortcut is moved to Neos.NodeTypes
- ContentCollection is marked final
Related issues
Associated revisions
[FEATURE] Support final flag for node types
Change-Id: Ia0887220d9f3de0f215f8331f9236167b4082fff
Migration: TYPO3.Neos.NodeTypes-201309111655
Related: #52020
Reviewed-on: https://review.typo3.org/23847
Reviewed-by: Sebastian Kurfuerst
Tested-by: Sebastian Kurfuerst
[TASK] Move Page from TYPO3.Neos to TYPO3.Neos.NodeTypes
This adjusts the generated data to comply with that change.
Change-Id: Ifc02aed15023fe0680151351522cb93c8e6aaa49
Depends: I35d0ee4eeff5096d9801445bf1c0dc69c6626d44
Depends: Id013f5788a1f11fd9e2c9174e1e0588de0100c39
Related: #52020
[!!!][BUGFIX] Move Page from TYPO3.Neos to TYPO3.Neos.NodeTypes
To update, run:
- ./flow core:migrate --package-key Your.SitePackage # updates your TypoScript and NodeTypes.yaml
- ./flow node:migrate live 20130911165510 # updates your Node structure
Technically, this change only deprecates TYPO3.Neos:Page not actually
removing it yet -- so rendering will still work as before for sites
which did not do the upgrade from above.
The footer below makes sure that this code migration is not applied anymore to
this package.
Make sure to apply the corresponding change of the TYPO3.Neos package as well,
which is I35d0ee4eeff5096d9801445bf1c0dc69c6626d44.
Change-Id: Id013f5788a1f11fd9e2c9174e1e0588de0100c39
Migration: TYPO3.Neos.NodeTypes-201309111655
Related: #52020
Reviewed-on: https://review.typo3.org/23846
Tested-by: Mr. Hudson
Reviewed-by: Adrian Föder
Tested-by: Adrian Föder
Reviewed-by: Tim Kandel
Tested-by: Tim Kandel
Reviewed-by: Bastian Waidelich
Tested-by: Bastian Waidelich
[!!!][BUGFIX] Move Page from TYPO3.Neos to TYPO3.Neos.NodeTypes
See the corresponding change in TYPO3.Neos.NodeTypes for
upgrade instructions.
Make sure to apply the corresponding change of the
``TYPO3.Neos.NodeTypes`` package as well, which is
Id013f5788a1f11fd9e2c9174e1e0588de0100c39.
Change-Id: I35d0ee4eeff5096d9801445bf1c0dc69c6626d44
Depends: Id013f5788a1f11fd9e2c9174e1e0588de0100c39
Migration: TYPO3.Neos.NodeTypes-201309111655
Related: #52020
Reviewed-on: https://review.typo3.org/23845
Reviewed-by: Tim Kandel
Tested-by: Tim Kandel
Reviewed-by: Christopher Hlubek
Tested-by: Christopher Hlubek
Reviewed-by: Bastian Waidelich
Tested-by: Bastian Waidelich
[TASK] Move Page from TYPO3.Neos to TYPO3.Neos.NodeTypes
This adjusts the Site.xml to the moved `Page` node type.
The Migration footer is added here to not let the
migration tool grab that change.
Depends: I35d0ee4eeff5096d9801445bf1c0dc69c6626d44
Depends: Id013f5788a1f11fd9e2c9174e1e0588de0100c39
Migration: TYPO3.Neos.NodeTypes-201309111655
Related: #52020
Change-Id: Ie85089aa2a3b00da3b317d5db320d601527ed9b0