I’ve got a news content element, with a ContentCollection (‘details’) as a childNode.
If this element was copied it leads to an unstable identifier.
node:repair --dry-run says:
Dry run, not committing any changes. Run integrity checks related to Neos features Checking for nodes with missing URI path segment in dimension "language=de_DE" Checking for nodes with missing URI path segment in dimension "language=en_US,de_DE" Checking for nodes with missing URI path segment in dimension "language=fr_FR,de_DE" Checking for root and site nodes with content dimensions set ... Run checks for basic node integrity in the content repository Checking for nodes with abstract or undefined node types ... Checking for orphan nodes ... Checking for disallowed child nodes ... Checking for undefined properties ... Checking for broken entity references ... Checking for nodes with invalid dimensions ... Checking for nodes with invalid workspace ... Checking for missing child nodes ... Child node "details" in "/sites/website/node-57c5a7ea2058e/node-57e3928b6091b/main/node-57e3acc3bf220" does not have a stable identifier 1 identifiers of child nodes need to be updated
Including several new news elements works fine.
If one copy and paste a content element with ContentCollections, like ‘TYPO3.Neos.NodeTypes:TwoColumn’,
the second columns are considered having unsable identifiers.
Is there a bug, copying ContentColections?
Is there any thing I can do about it?