I am playing with the latest views, but do not quite understand new logic behind 'Relationships' and 'Arguments'. I am trying to use cck nodereference to show nodes (in parent) that are referring to the current node (sort of reverse node referral). Although I use approach that worked in 5.x-1.6, I still have no luck. I see a lot of potential there, but nothing seems to work.
Any documentation coming soon?

Comments

merlinofchaos’s picture

merlinofchaos commented

If you're using the -dev version, there should already be documentation on relationships. Is that documentation insufficient? I admit it may not be well written, but your post sounds as though you haven't read it at all.

encho’s picture

encho commented

I know, but it does not explain all the options, especially using relationships with arguments and all the possibilities you have with arguments combined. I was not able to do reverse reference, whatever I did, but I can see possibility IS there.

merlinofchaos’s picture

merlinofchaos commented

I can't list all the options, as each relationship is pretty much its own thing. I suppose I can give a few examples, but 'explain all the options' isn't possible, because they are so varied. All I can do is explain what relationships do at their core.

Let's say I have node type 'alpha' and it has a node reference (single, so only one) named 'beta' and set it so that it can only reference nodes of type 'beta'.

If I create a 'node' view and set up a relationship with the 'beta' nodereference, There will be two 'nodes' in the query. The 'default' relationship will be the alpha node, and the 'beta' relationship will be the beta node. If I set the reference to 'required' and no other filters, I will get, essentially, a list of all beta nodes and their corresponding alpha node, so alpha nodes will be repeated for every beta node.

If I set a 'nid' argument on the default relationship, I can get a list of all 'beta' nodes that reference a particular alpha node. If I set a 'nid' argument on the 'beta' relationship, I can get a 1 entry view that will list the alpha node for a particular beta node.

Does this help?

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed
encho’s picture

encho commented

Thanks, this kind of documentation I would like to see :-)

Although argument did not work for me in this case, I will have to investigate it further. What I am trying to do is to have all the referring 'alpha' nodes displayed when viewing the 'beta' node. So 'beta' is basically the parent with many 'alpha' children :-) Maybe I just need to dig into this deeper.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

finex’s picture

finex commented

I'm looking to find a solution to this problem too. But I've found nothing useful on the net. :-(