Neos Backend crashes if newReferenceNodePath points to non-existing node

[lorenzulrich]

If a newReferenceNodePath is configured, but the referenced node is not available, the backend crashes without providing a meaningful message.

Message in developer console:

Error: Please provide either a string, an array or an object containing a contextPath to the FlowQuery API.

A speaking error would be nice to have.

[paavo]

Hey @lorenzulrich
Does your problem still exist?

I found a similar Problem when trying to use FlatNav with Content-Nodes (instead of Document-Nodes).
We try to fix this Issue (with a little help from @dimaip).

Maybe we can disable Node Creation too, if the referenced node in newReferenceNodePath is not available.

[lorenzulrich]

@paavo Yes, this problem still exists. Thanks for looking into it. I'm interested to learn about a solution for content nodes.