Fix moving nodes to a different parent node #5561
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrade instructions
Currently, when moving nodes to a different parent node, the publishing fails, as the referenced shadow node can not be found. This happens, because
NodeData::move()
method tries to find the node data by the source node instead of themovedTo
-property.Review instructions
Try to move a node to a different parent node (move page inside another page for example) without this PR. Then try it again with this fix (mainly replace
findOneByMovedTo($sourceNodeData)
withfindOneByMovedTo($sourceNodeData->getMovedTo())
).Checklist
FEATURE|TASK|BUGFIX
!!!
and have upgrade-instructions** Thanks **
Thanks to @robinroloff for also digging into this.