regarding this post at: http://drupal.org/node/100136
==============
PROBLEM AT HAND
===============
1) First i install the latest 1.2 views (i move the original older 'views' folder out of the modules directory. after extracting views 1.2 download, the new views ilives in a folder called 'views_1", so i rename it to 'views' and copy the folder into the modules directory. i make sure i go to admin/modules and uncheck views and check it again and then resubmit the the modules at the bottom of the page just to make sure it's picking up my 1.2 views - i hope/think???)
2) I create 2 CCK types (MyEvent & Venues) (again see the post for information of the problem at hand)
3) Then i relate them manually with nodefamily by admin/settings/nodefamily (i think that's what this is there for right? i don't have to use the API, this will probably create a lookup table on the backend - yes - unless i don't understand?)
4a) I go into admin/views and create 1 View for MyEvent called 'myevents". I enable a number of fields on it (some native to MyEvent CCK) and one is a nodereference field to my CCK Venue
4b) I go into admin/views and create 1 View for Venues called 'myvenues". I enable a number of fields on it native to the Venue CCK.
4c) I test 'myvenues' view. It works fine. I do the same for 'myevents'. It works fine but of course it doe NOT RELATE THE VENUES CORRECTLY BECAUSE THE 2 VIEWS HAVEN'T BEEN FUSED YET.
5) I go into admin/views/fusion. I make the 'myevents' parent and 'myvenues' child "Using --> 'node family relation'". I presume this is the nodereference field in MyEvent CCK linking to Venues CCK
6) I go back to admin/views and test 'myevents' view. It still works the old way. It does NOT pickup any of the Venues fields.
7) I've tried recreating the view and the fusion and the nodefamily a number of times to no avail.
Can you confirm i'm doing this right? Including the install of the latest views to support this functionality.
If not, let's fix it..
OK.
Comments
Comment #1
fagohm, do you also set the nodefamily relation in the same direction? events -> venues
then, nodefamily works in the background by comparing node authors, if the authors and the node types match, the relation will be set. it doesn't use the cck nodereference field if you think that.
otherwise it looks like being correct.
Comment #2
newdru commentedThe nodefamily relationship is: admin/settings/nodefamily is
Events (parent) -> Venues (child)
So that's in the right direction.
Also, i only have one user on the system and that's admin. All node content belongs to that author. So that shouldn't be an issue.
FWIW.. i just went back in to my "myevents" views to check all of the settings.. just to make sure the settings were being saved i hit save and when i do i get the following message at the top of the screen:
Warning: array_merge() [function.array-merge]: Argument #2 is not an array in C:\wamp\www\drupal474\modules\contrib\views_fusion\views_fusion.module on line 374
Which is quite odd because i don't have any arguments set on the view: the args block is completely blank and the url is simply set to "myevents"
Should i be pulling latest cvs on your pkgs instead of the latest greatest tarball from the modules page???
Comment #3
newdru commentedOne more thing..
After I try to save the view and it fails.. it adds 3 "blind" fields back to the view. What i mean by "blind" is that in the "fields" section of the form, it adds 3 extra fields with labels, but none of the other columns are populated (the most important being the actual target field itself!!!).
If i try to delete these "blind" fields, when i go to save the view, i get the same error as before:
Warning: array_merge() [function.array-merge]: Argument #2 is not an array in C:\wamp\www\drupal474\modules\contrib\views_fusion\views_fusion.module on line 374
and i can't reset the view back to the way it was. And i don't want to have to go in and recreate it from scratch again. i'm tired of doing that.
fwiw, it appears that the 3 "blind" fields appear to be coming from a previous version of this view where the view actually did have those "real fields" assigned to the view. I deleted those fields a long time ago but occasionally when editing a view, they randomly pop up and then i can't save the view.
Note, I've recreated this view from scratch and i've cloned it, etc. But somehow or another those "blind" fields have a way of popping up on the view. I'm not sure if there isn't some db trouble going on here. It appears that old versions or states of a given view are getting mixed with the current version so that fields from the old one that no longer exist get attached to a current view.
Comment #4
fagojust install views 1.2 and the latest views fusion 4.7.x tarball.
you shouldn't get such an error at this line if you are using the latest version.
to your other views problem:
I never ran over such a behavior. You could try a new clean install of views:
Deactivate the views module, remove its tables and its entry in the system table. then reinstall it and recreate your view. if it still occurs, it's a bug.
if you have only one user, nodefamily will relate all your events with all venues. Do you want that?
Otherwise I think you would need what I've described there:
https://more.zites.net/node/551
or a views_fusion integration for the cck nodereference field..
Comment #5
fagoComment #6
(not verified) commented