Namespace migrator Version 1.01.00 has a problem.
When the namespace to be migrated involves multivalued child nodes, it changes the order of those nodes.
We have two cases among many where the content may contain any number of html blocks. The node order is used to display these blocks on a page.
When the namespace migrator is run, on one page, which had 3 fields, the result was the 3 nodes ordered as 3, 1, 2.
In another case, there were 7 html fields and the resulting order was reversed (7, 6, 5, 4, 3, 2, 1).
Running the migrator again with just the primary node type changing did not restore nor further disorder the nodes in question.
Does anyone have a workaround for this behavior?
Identifying everywhere the order was changed and important and manually restoring the order will be quite an undertaking.
We have a postgreSQL repository and are running Hippo under Red Hat.
-Paul Hammer