Details
-
New Feature
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
We have detected some external tools can introduce some changes in the version history nodes, leaving it inconsistent. The main problems we detected were:
- Some version nodes are left empty, instead of removing the node completely. Leaving empty nodes that will trigger ConstraintViolations when they are traversed.
- The primaryType of the node is changed incorrectly from nt:versionHistory to nt:version.
I have created a script to traverse the versionHistory and detect if the NodeStore is affected by this issues.