support to relationship in views 2
yaron24 - October 25, 2008 - 12:45
| Project: | Node Hierarchy |
| Version: | 6.x-1.2 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | jpsalter |
| Status: | needs review |
Description
Relationship support would really come in handy.
For example if i want to display all parent nodes of user who own the children nodes.

#1
i thought i can go around it by i can't
whats the different between those 2 only arguement the module supplies:
Node Hierarchy: Ancestor Node ID
Use this if you want to display any descendant of the given node
Node Hierarchy: parent
The parent id of the node.
They both do the same!!
I want to display parents details of given children NID's via argument
#2
1) Views 2 Relationships are on the cards. I didn't want to mess with that while the views api was in flux, but now that there's a stable release I'll put it on the todo.
2) The difference between the arguments is that while Parent ID will only show immediate children, Ancestor will show grandchildren, great-grandchildren etc. If you only have 1 level of decedents on a given node they will be the same.
#3
I am trying the latest version of nodehierarchy the Sep-29 dev and I can't get the grandchildren to show up. It only displays the children
#4
I think I'm starting to need this very badly. I have some complex sites that have been using node references (and a bunch of other stuff) to artificially create hierarchical relationships between nodes. Nodehierarchy looked like a much better solution and was working great for so many things that I just removed all of those node references throughout my sites in favor of Nodehierarchy.
I just assumed the Views relationships were in there and then, just after it was too late to turn back, learned that all of the options I initially had to use relationships in views were no longer available to me. Help!
No, this issue is not currently affecting a live site but my development on at least one site is totally stalled until I find a solution for this. Is there any other way to filter a node based on content in its parent node?
A temporary workaround for this would be really helpful. I don't want to have to rebuild these sites the old way just for this. I'm going to start playing with calculated fields to see if I can present the parental relationship. Any ideas would be greatly appreciated.
Thx.
BTW, great work on the module. I'm looking forward to using "restrict parent-child relationships by type".
Note: It may be helpful to put "(Relationships not yet implemented)" after "Optional Views integration" on the Nodehierarchy project page. This really caught me off guard.
#5
I had a need for this too. Here is the patch to add views relationship support.
#6
Forgot to set to "needs review".
#7
Thanks! This is encouraging. I'll try this when I get a chance.
I have since switched over to using Node Relativity which had this from the get go. Node Relativity has a simple implementation that makes it very easy to setup access to parent, grandparent, and great-grandparent nodes.
Unfortunately, when I switched I had to give up the nice menu integration of Node Hierarchy which I found very helpful. Maybe I can switch back or at least consider it again for future projects.
#8
I am also in need of a grandchildren View.