NodeBasedForm: UI duplication and disappearing "furtherPages" when form is rendered without ContentCollection #157
Description
NodeBasedForm: UI duplication and disappearing "furtherPages" when not using ContentCollection
Description
We are experiencing inconsistent backend UI behavior with Neos.Form.Builder:NodeBasedForm when the form is placed inside a node that does not use a Neos.Neos:ContentCollection (e.g. main), but instead renders its child nodes directly.
Our project architecture does not rely on a default main ContentCollection.
Elements are added as direct child nodes and rendered via:
content = Neos.Fusion:Loop {
items = ${q(node).children()}
itemName = 'node'
itemRenderer = Neos.Neos:ContentCase
}
When the same form is placed inside a regular ContentCollection (e.g. main or inside a grid column), the issue does not occur.
content = Neos.Neos:ContentCollection {
nodePath = 'main'
}
Observed Behavior
When a NodeBasedForm is placed inside a node that renders children directly:
Adding a page under furtherPages works initially.
After saving:
The UI representation of the newly added page appears duplicated.
The duplication is only visible in the Neos backend UI.
The nodes are not duplicated in the database.
Sometimes, the furtherPages child node temporarily disappears after saving.
After a full backend reload, the structure appears normal again.
Important:
This is purely a backend rendering issue.
The content repository does not contain duplicate nodes.
The issue only occurs when not using ContentCollection.
Expected Behavior
NodeBasedForm should behave consistently regardless of whether it is placed:
Inside a ContentCollection
Or inside a custom node that renders its children directly
The form builder UI should not depend on the presence of a ContentCollection to function correctly.
Additional Observations
The issue does not occur when the form is placed inside:
The default page main content collection
A column grid that uses Neos.Neos:ContentCollection
The issue appears immediately after saving.
It resolves visually after a backend reload.
This suggests a backend UI / projection synchronization issue rather than a content repository duplication.
Maybe a Neos UI bug?