Handling multiple-value node references
| Project: | Views Fusion |
| Version: | 5.x-1.2 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Hi, I got the patch for nodereference.module to work -- thank you! It's interesting what happens when I have multiple instances of the node reference field: the fusion repeats the fields from the primary node for every instance of the secondary node. Example: I have a Publication type which references an Author type. When a single Publication has two Authors, I get this in list view:
- Publication title
The Science of Desire
Publication date
07/23/2002
Author title
Dean Hamer
Author quote
I'm a doctor, not a geneticist - Publication title
The Science of Desire
Publication date
07/23/2002
Author title
Peter Copeland
Author quote
A stitch in time saves nine
The Publication is shown twice, once for each Author. The same kind of thing happens in table view; it's just laid out differently.
I would like the Publication fields to display just once, but list each Author's fields in a sub-list. Like this:
- Publication title
The Science of Desire
Publication date
07/23/2002- Author title
Dean Hamer
Author quote
I'm a doctor, not a geneticist - Author title
Peter Copeland
Author quote
A stitch in time saves nine
- Author title
(This would probably be harder in table view.) Do you have any suggestions for how to do this? If this is not currently possible with Views Fusion, maybe I will make it a feature request.
Thank you!
#1
I don't see how this could be possible with views_fusion. Better use full node views and theme them appropraite.
#2
this is now an 'old' post, but I figured I'd weigh in for just a sec. This is *kinda* a VF issue, but i think should actually be a "feature request" rather than an "issue". in normal views, you can add a table, not specify a join (see taxonomy for an example) and have a secondary query pull only the related values out as a field handler. this works in conjunction with the 'group related values' option too.
my guess is that this poster is trying to get that same functionality to happen but between views. basically useing 'group related values' from the 2nd view into the 1st.
I think this could be resolved by having VF actually run the 2nd query, then index the related field, and provide the handler function for the first view to add the data in. (this might also already happen with the nodereference.module stuff anyways)
its always easier to suggest the work than to do it myself though :)
-Chris