When using the "Node Hierarchy: Ancestor Node ID" argument:
1) On sort criteria, when using "Child Weight," all ancestors are sorted on the same level. Instead, I think it would help if level 2 ancestors still appeared below their parent
Examples. This would be ideal:
Ancestor 1 weight -49
Ancestor 2 weight -48
- Ancestor 2.1 weight -50
- Ancestor 2.2 weight -49
This is what is currently outputted:
Ancestor 2.1 weight -50
Ancestor 1 weight -49
Ancestor 2.2 weight -49
Ancestor 2 weight -48
Additionally, when outputting a list of fields, it would be nice to group level two ancestors so that we could indent them (similar to comment replies) or do some sort of visual differentiation to signal that they are level 2 ancestors
Comments
Comment #1
kmontyFail. I just got this to work by setting a relationship.
Comment #2
sansui commentedI am trying to achieve this depth as well - how did you set up your view so that a full display of the main parent node's children and sub children are displayed like you indicated?
Comment #3
sansui commentedComment #4
sansui commentedAh. For anyone else here looking for this information, the node hierarchy views handler for relationship is only in the dev version, not in 1.3. The links display in correct order using this (although I'm still trying to figure out how to indent the display)
Comment #5
dgorton commentedClosing per #4 - this is fixed in 2.x dev.
Comment #6
jonathan_hunt commentedI'd like to show all descendants of a node, but the sort order is incorrect. I have a view with a relationship configured on Ancestor Node ID and that relationship is used to map to the argument and the Child Weight for sort order. But the sort doesn't appear to be taking depth into account.
Is there any documentation or a working example of using a relationship to achieve a full tree of descendants?