Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello
I don't know how to use this module, is there any tutorial ? thanks
Comment | File | Size | Author |
---|---|---|---|
#15 | views_field_view-addreadme-1171604-12.patch | 1.63 KB | beanluc |
#12 | README.txt | 162 bytes | jvns |
Comments
Comment #1
dawehnerFeel free to create a readme file. Every other user of this module managed to figure it out.
It's just a field in views.
Comment #2
core44 CreditAttribution: core44 commentedNot sure how someone asking how to use the module is able to write a readme?? Good luck with that freelylw.
My quick guide based on my usage would be: create a view (child) and a view (parent). In the child view add the fields you want to display and also add an argument (in my case NID). In the parent view add the fields you want to use and also add 'views field view' (under global category in add fields), select your child view in the drop down for the field settings. You can then choose from the available replacement tokens what data you want to pass back to the child view. In my case it was the data from a hidden field for NID. (EDIT: you have to update the 'views field view' once you've selected the view in the drop down, then edit it again before you get the argument options)
I used the module to display comments from each of the nodes in my parent view, I don't know if what I'm doing is standard usage but it solved my needs. Hope that's more helpful than "create your own readme file".
Comment #3
MBroberg CreditAttribution: MBroberg commentedI was thinking the same thing, filthypixel, and thanks for the tips. I had written myself some notes since I keep forgetting. Pretty much the same as yours, but I formatted it in steps and there are a few extra notes.
1. Create a Child View.
2. Add arguments to that child view. The parent view will be passing argument values to the child so that the child knows what to display. No other settings are necessary, but validators and "argument not present" could be set.
3. Create a Parent View.
4. Add Child View (Global field). Must be toward the bottom of the field list, or at least underneath the fields that are going to be used as arguments. (e.g "node id" might be used as an match between the parent and child views, so put "node id" before your global view field in the list.)
5. Select which View and Display to use for the child data (will require doing this in 2 steps - the field must be saved before the display selection is available)
6. Type the token replacements, in order, separated by a comma, as the arguments for that view field. These values will be passed to the child. Make sure each field you are passing as an argument is completely clean, as in: no label, no formatting, nothing that would pass into the argument other than the desired text or number.
Comment #4
Avalanche CreditAttribution: Avalanche commentedDereine, I respect your contributions to Drupal and the open-source community, but there's no reason to be a dick.
Thanks mbroberg and filthypixel, your advise helped me a lot. I'm working on a deadline and needed to access a field from Feeds to get it to work in Gmap with Location, and this helps tremendously.
Comment #5
dawehnerWell some days i try to help as much as possible and then there are issues like this.
At least from my perspective regardless whether there is someone provides a solution or not, there will be no response anymore.
Isn't
This module allows to embed a view as a field in a view.
already quite some information to start and ask a real question instead asking for a tutorial? Drupal is just not the best system to ask for a tutorial because it's so flexibleComment #6
misterT CreditAttribution: misterT commentedNo, it's not. This provides no information as to what kinds of relationships are allowed between views or how to pass information from one view to another, for example. Documentation would be very helpful, and I'm glad I found this page. Thank you for making this module. From the information on this page, it sounds like it might be what I'm looking for, so I'll go ahead and give it a try.
Comment #7
cdd23 CreditAttribution: cdd23 commentedWell, I hope it's not impolite to kick this issue up again, but I still don't fully understand how to employ this module. This may be in part to my incomplete understanding of Views. I've read through the documentation for Views (Relationships and Arguments trip me up a bit), but I'm still having trouble using this module.
I'm trying to make an events calendar view. There is a limited set of possible speakers for the events.
So I've got an "Event" content type and a "Speaker" content type. Each "Event" has one or more "Speakers" associated with it. I want my listing of Events to display all the Speakers in the same line as the event, e.g.:
Since Views in Drupal 6 doesn't allow for multiple items, I was directed to this module by other helpful folks. I have set up a child view as directed by the posts above, but I don't get any value displayed in the column for the Speakers. I've tried changing the settings for the Child view (like adding other arguments aside from Node ID) and the settings for the Global View but to no avail. I always get an empty last column, the views_field_view column I've added while I test this. That column should show the same as the "Speaker" column (which only displays the first speaker, since it's a normal field).
I'm wondering if it's my arguments that are the problem. I've set it to the same as the "Speaker" column, like so:
'arguments' => '[title_1]',
Anyone have any helpful ideas as to what I'm missing or doing wrong? Or suggestions to where I might read up more on this? My apologies if this case is too specific to be generally helpful, but it seems like a common enough scenario for this module.
Just to be thorough, here are the exports of the two views.
Child View:
=============================
Parent View:
Comment #8
sprice CreditAttribution: sprice commented@aceinthehole please see: http://drupal.org/dcoc#respect
The module is under heavy development, so please allow the maintainers to maintain before they create the documentation.
Comment #9
dawehnerThis issue is NOT about
This issue is about providing a good README file, everything else is not productive.
Comment #10
mototribe CreditAttribution: mototribe commentedthis is a great module. How about using the instructions from #3 and create a simple documentation page from it?
Comment #11
dawehnerJust do it :)
Comment #12
jvns CreditAttribution: jvns commentedHere are the instructions from #3 (more or less) copied into a README file.
Comment #13
damiankloip CreditAttribution: damiankloip commentedIsn't this the readme file from the sites/al/modules directory?
Comment #14
carvalhar CreditAttribution: carvalhar commentedversion 7 doesn't have a readme...thkz for #2 e #3
Comment #15
beanluc CreditAttribution: beanluc commentedHere's a proper patch containing a README substantially from #3 and the project page.
Comment #16
beanluc CreditAttribution: beanluc commentedComment #17
damiankloip CreditAttribution: damiankloip commented@beanluc, thanks! I will check this out later today. I have been refactoring alot of the token functionality, so hopefully, soon, it will be much better!
Comment #18
damiankloip CreditAttribution: damiankloip commentedThis has been committed to 7.x-1.x and 6.x-1.x branches. The patch wouldn't apply cleanly, so had to make a few adjustments :)
Comment #20
alibama CreditAttribution: alibama commentedhere's a brief tutorials with video attached http://blog.hsl.virginia.edu/drupalpress/views-field-view-what-works-and...