I have forums that I'd like to "add" images to with Image nodes. I've
created a relation that forum is parent to image. I've tried with various
views but to test I've create two really simple views. Both views are
Table views, one only shows the Node Title (as link) and Node Type and
filters to show only Node Type Is One Of Forum and the other view shows
Node Title (as link), Image (Image with link) and Node Type and filters to
show only Node Type Is One Of Image. Both views works as expected by them
self but when fusion them it shows:

Forum name      Type      Image name               Image             Type
--------------------------------------------------------------------------
Forum1          Forum     Image1                                     Image
Forum1          Forum     Image2                                     Image
Forum2          Forum     Image3                                     Image

and the image names are links to the forums, not links to the images and no
image is shown. I've tried to do it the other way around, ie image-view as primary view
and reversed relations with similar result.

I'm running Drupal 5.1, Image 1.1, Node family 1.3, Views
1.6-beta5 and Views Fusion 1.2.
I have the develop module and can send SQL querys if that helps.

Comments

liquidcms’s picture

liquidcms CreditAttribution: liquidcms commented
Priority: Normal » Critical

check if the view is set to cacheable (last field in view_view table

i think i may have same issue... my view fuses to get images from another node (nodereferenced) and it was working ok, but then i did an update of the view and lost the images.

with a shitload of digging i found that the main view was being allowed to be cached.. not really sure but i think it displays the cahed one rather than letting the fusion occur and displaying that

when i go into the table and set caching to 0 - my images come back...

i am trying to sort out how to not have the view set caching allowed every time i update the view... i think i use to know a way to set something in args or arg handling code to prevent it from caching???

liquidcms’s picture

liquidcms CreditAttribution: liquidcms commented

ok, so i set an argument to be node id and just set to display all values.. which since i have no args basically should make it do nothing... and sure enough view will not be cached now and my images are back...

of course if you actually use args, then this wont work.. but then it also wouldnt be your problem then either

urbanarpad’s picture

urbanarpad CreditAttribution: urbanarpad commented

I was having the same problem... drove me up the wall. I have a usernode view (userlist) as a parent to an Advanced Profile node view (uprofile). What seemed like randomly, the Advanced Profile data wouldn't show up.

My solution was to delete the Fusion, clear the Views cache and then re-create the Fusion. That would fix it. However, any time I edited either view, the problem would return until I performed the delete/clear/re-create step again.

It turns out that the child view, uprofile, is cached in the database. I don't know if this is a bug or a feature request but I wish I would have known about and/or been able to control this before many hours of frustration.

As a feature request: expose the caching values to the user in a checkbox.
As a bug report: dunno. do something on each view edit associated with a fusion? seems far-fetched.
As a documentation request: Add a sentence to the docs about this.