Namespace Migrator reordering nodes

[phammer]

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

[Unico Hommes]

Hi Paul,

This looks like a bug in the migrator. The nodes are migrated in the order they appear in the database which probably is the natural order between their UUIDs, although this may vary somewhat with the database that is used.

Are the disordered nodes named using the migrated namespace prefix? In that case the node is renamed but this has the side-effect of causing the node to become the last sibling. After the rename the migrator should move the node back into the position is was in before and it doesn't do that yet. (This can only be done if the parent node is orderable btw). I will create an issue for this. [1]

Unfortunately I don't see any way to automatically detect which nodes lost their proper ordering (except that probably they are all nodes with a name using the migrated namespace prefix and having a parent that is orderable) or what their ordering was prior to the migration in order to restore it. :-/

Apologies for this.

--

Unico

1. https://issues.onehippo.com/browse/REPO-1361

--
Hippo Community Group: The place for all discussions and announcements about Hippo CMS (and HST, repository etc. etc.)
 
To post to this group, send email to hippo-c...@googlegroups.com
RSS: https://groups.google.com/group/hippo-community/feed/rss_v2_0_msgs.xml?num=50
---
You received this message because you are subscribed to the Google Groups "Hippo Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hippo-communi...@googlegroups.com.
Visit this group at http://groups.google.com/group/hippo-community.
For more options, visit https://groups.google.com/d/optout.

[phammer]

Hi Unico,

Yes, the disordered nodes have, as their primary type, the namespace being migrated.  Additionally, they are the specific part under the namespace that is being modified and requiring the custom updater.

namespace:specifictarget.

-Paul