Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

If documents are created as tethered nodes they often have no uriPathSegments. Currently this leads to incomplete document-uri-pathes. This is problematic for two reasons:

1. This allows to create empty path segments which is a feature we do not plan to support ATM
2. This cannot be fixed afterwards by setting UriPathSegments since on setProperties(uriPathSegment) only the last part of the path is ever changed.

Expected Behavior

The uriProjection should project a valid pathSegment for all documents below sites regardless wether the a uriPathSegment was defined during node creation.

It should be discussed wether this is done by creating the UriPathSegment in that case or by falling back to the nodeAggregateId as fallback.

Steps To Reproduce

Steps:

1. create a autocreated document "A" as child of the Site that has no defaut value for uriPathSegment.
2. that has another autocreated document "B" that has no default value for uriPathSegment.
3. Create a document below "B"

Verify:

1. The child Below "B" does not get a full uriPath
2. After manually setting the path for "A" and "B" the children only get an incomplete path without the segment for "A"

Environment

- Flow: 9
- Neos: 9
- PHP: 8.3

Anything else?

The Reason behind this behavior is the ambiguity of the meaning of "" in the UriPathProjection which on the one hand is path for a site-node but is also used as a fallback for the uriPathSegment. This leads to parent Nodes accidentally beeing treated like site-nodes.