One of our customers are creating a huge load of nodes in their enonic XP installation. After a while they realized they were unable to publish the site because of an error message pointing towards nodes that had no parents.
After I ran XP doctor we got an overview over which nodes were affected and after talking to support we realized we had to solve this manually.
Solving it manually is not that easy either. The parent nodes needs to be created, then we need to wait for XP to pick up the change, and then we can delete trees of nodes using Data Toolbox.
This sounds like a bug in Content Studio to me. Its rather painful and timeconsuming to fix.
Are you aware of this, do you have any plan of fixing this?