RootNode query does not return the correct node (returns null)

[breadlesscode]

Hi,

first thanks for this great Package. I really like the idea of storing the nodes outside the normal node tree. ❤️

But in my current setup the query for finding the current root node doesn't work. Everytime the getRootNode() Method is called, a new root node is created. I found this code lines with the todo comment. Is it a known problem?

Sitegeist.Taxonomy/Classes/Service/TaxonomyService.php

Lines 134 to 141 in 6d6754b

	// return existing root-node
	//
	// TODO: Find a better way to determine the root node
	$taxonomyDataRootNodeData = $this->nodeDataRepository->findOneByPath(
	'/' . $this->getRootNodeName(),
	$context->getWorkspace()
	);

I'm looking for a better way to query the root node, but found nothing. Any ideas why this returns null?

I'm trying to fix it, but I don't know if I can.

Versions:
neos/neos 7.2.0
neos/neos-ui 7.2.1

And thanks again for the work :)

[breadlesscode]

One possible solution could be the use of findByPathWithoutReduce() instead of findOneByPath().

e.g.:

$taxonomyDataRootNodeData = $this->nodeDataRepository->findByPathWithoutReduce(
     '/' . $this->getRootNodeName(),
      $context->getWorkspace()
);
$taxonomyDataRootNodeData = current($taxonomyDataRootNodeData);

if ($taxonomyDataRootNodeData !== null && $taxonomyDataRootNodeData !== false) {
   …

But I have no idea which side effects this solution might have.

[jobee]

I've seen this too in Neos 7.2 (only in local dev environment, not in production)
@breadlesscode your described workaround works for me

[breadlesscode]

@jobee With my project, it's the other way around. Production has problems, dev not. And even if I import the live DB.

You can require the branch new-root-node-query-logic from my fork until we have fixed the error.

[mficzel]

Does #75 solve this?