Reference lookup fails when Node was moved

[neos-bot]

Jira issue originally created by user @Weissheiten:

Creating a Node in the tree and moving the node afterwards (e.g. creating it in the root and moving it further up the tree under a page) results in the node not being found in my current demo Installation/project. (even after Publishing, force Clearing the Cache on CLI and super refreshing the browser or using other browser)

Issue is unconfirmed yet - would need to be reproduced on another Installation to be confirmed.

Occured while working on Community.News (under heavy dev atm https://github.com/Flow-Community/Community.News) - introduced reference for News <-> Author (see NodeTypes.yaml)

Attached is a zip with a database dump at the time the reference was failing to be found and 2 screenshots for visualisation.

Atachements:

Jira-URL: https://jira.neos.io/browse/NEOS-965

[neos-bot]

Comment created by @dimaip:

Can't test ATM, but does the reference break in inspector too, or is it only not being found by our custom FQ operation?

[neos-bot]

Comment created by @Weissheiten:

This issue is related to the inspector (when setting the reference - see screenshots)

[neos-bot]

Comment created by phanebrink:

The issue is easy to reproduce:

1. Create a page
2. Move Page somewhere else
3. Try to link the page in a selectbox or call the service manually -> page is not found for this user anymore Do not publish during these steps. This issue can not be resolved by publishing, because the shadow nodes for the user who moved the page are not removed after publishing. This might be another bug.

Problem: The node search service calls the NodeDataRepository to get the result set. The repository then proceeds to reduce the result set by workspace/dimensions including(!) the removed nodes. This may lead to the "real" nodes beeing removed and the shadow nodes being returned. Then it filteres the removed (shadow) nodes and the node is no longer in the result set.

This can be easily fixed by switching the order of the filter methods but I need some more eyes on that ;-) I commited a change to gerrit, please review.

[mhsdesign]

• Create a page
• Move Page somewhere else
• Try to link the page in a selectbox or call the service manually -> page is not found for this user anymore Do not publish during these steps. This issue can not be resolved by publishing, because the shadow nodes for the user who moved the page are not removed after publishing. This might be another bug.

yes i could reproduce this. Reloading the Ui after these steps doesnt help - this does seems to be an issue in the Node service