Which works fine, until a previously added fragment, stays lingering around after its deletion.
Basically I can see the content id using content viewer plugin.
But it does not show up in the list of related content in content studio.
If I try to rearrange the order of the fragments in the list of related content, the order sorta gets randomized and the ghost fragment is still there in content viewer.
Would a reindex fix this?
I guess I could edit the blob directly (since this is happening on my laptop) but thats not a good solution for our production cluster (if it where ever to happen there…).
But when I try to import I get the following importErrors:
Could not import node in folder Node already exist
com.enonic.xp.node.NodeIdExistsException: Node already exist
You will be happy to know we have polished the contentSelectors to handle “ghost” items better in 6.7 - so hopefully this will never be a problem again!