PubsubPersistenceManager does not load nodes properly if the hierarchy has more than two levels.
Description
The loading of nodes on startup incorrectly tries to create a parent/child hierarchy on collection nodes before all nodes are created. Thus causing lookups of parent nodes to return nothing and then not reproducing the hierarchy correctly. It will only work if the node id's happen to be in the right alphabetical order such that parents get ordered before their children.
Fix is pretty trivial, simply create hierarchy after creating all the collection nodes.
The loading of nodes on startup incorrectly tries to create a parent/child hierarchy on collection nodes before all nodes are created. Thus causing lookups of parent nodes to return nothing and then not reproducing the hierarchy correctly. It will only work if the node id's happen to be in the right alphabetical order such that parents get ordered before their children.
Fix is pretty trivial, simply create hierarchy after creating all the collection nodes.