We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When tethered child documents are added to a site node without a default value for uriPathSegment, they will not get their own URI
uriPathSegments that are added later should also take effect
- Flow: 9.0-dev - Neos: 9.0-dev - PHP: 8.0
This happens because in DocumentUriPathProjection::550 and following:
$oldUriPath = $node->getUriPath(); // homepage -> TODO hacky? if ($oldUriPath === '') { continue; }
Instead of checking for empty string, we should check against the site node type introduced in #4563
The text was updated successfully, but these errors were encountered:
nezaniel
Successfully merging a pull request may close this issue.
Is there an existing issue for this?
Current Behavior
When tethered child documents are added to a site node without a default value for uriPathSegment, they will not get their own URI
Expected Behavior
uriPathSegments that are added later should also take effect
Steps To Reproduce
-> the tethered child will show up instead of the homepage on path '/'
Environment
Anything else?
This happens because in DocumentUriPathProjection::550 and following:
Instead of checking for empty string, we should check against the site node type introduced in #4563
The text was updated successfully, but these errors were encountered: