I have a fused view which works just fine until I add the Image: Has image filter to one of the fused views. When I do, I get the following error when viewing the View:

    * user warning: Unknown column 'node_data_field_photo.field_photo_fid' in 'where clause' query: SELECT count(node.nid) FROM node node INNER JOIN nodefamily nodefamily_parent ON node.nid = nodefamily_parent.parent_nid LEFT JOIN node v8node ON nodefamily_parent.child_nid = v8node.nid INNER JOIN nodefamily nodefamily_parent2 ON node.nid = nodefamily_parent2.parent_nid LEFT JOIN node v7node ON nodefamily_parent2.child_nid = v7node.nid INNER JOIN nodefamily nodefamily_parent3 ON node.nid = nodefamily_parent3.parent_nid LEFT JOIN node v6node ON nodefamily_parent3.child_nid = v6node.nid INNER JOIN nodefamily nodefamily_parent4 ON node.nid = nodefamily_parent4.parent_nid LEFT JOIN node v12node ON nodefamily_parent4.child_nid = v12node.nid LEFT JOIN content_type_my_uploads v12node_data_field_photo ON v12node.vid = v12node_data_field_photo.vid WHERE (node.status = '1') AND (node.type IN ('talenteer_profile_basic')) AND (v8node.status = '1') AND (v8node.type IN ('talenteer_profil in /home/sites/bhunted.underdesign.co.uk/public_html/includes/database.mysql.inc on line 172.
    * user warning: Unknown column 'node_data_field_photo.field_photo_fid' in 'where clause' query: SELECT node.nid, v8node.nid AS v8node_nid, v7node.nid AS v7node_nid, v6node.nid AS v6node_nid, v12node.nid AS v12node_nid FROM node node INNER JOIN nodefamily nodefamily_parent ON node.nid = nodefamily_parent.parent_nid LEFT JOIN node v8node ON nodefamily_parent.child_nid = v8node.nid INNER JOIN nodefamily nodefamily_parent2 ON node.nid = nodefamily_parent2.parent_nid LEFT JOIN node v7node ON nodefamily_parent2.child_nid = v7node.nid INNER JOIN nodefamily nodefamily_parent3 ON node.nid = nodefamily_parent3.parent_nid LEFT JOIN node v6node ON nodefamily_parent3.child_nid = v6node.nid INNER JOIN nodefamily nodefamily_parent4 ON node.nid = nodefamily_parent4.parent_nid LEFT JOIN node v12node ON nodefamily_parent4.child_nid = v12node.nid LEFT JOIN content_type_my_uploads v12node_data_field_photo ON v12node.vid = v12node_data_field_photo.vid WHERE (node.status = '1') AND (node.type IN ('talenteer_pr in /home/sites/bhunted.underdesign.co.uk/public_html/includes/database.mysql.inc on line 172.

I am using Views module 1.166.2.45, Views Fusion module 1.7.2.7, imagefield 1.33.

As I say, the view works fine when that field is removed from its view, so I know that that is causing the problem. I do not know for certain however that this is a Views Fusion problem but it seemed logical to me, hence the post here. If it is an imagefield problem I will be happy to post there instead.

However, I do remember reading somewhere that Views Fusion will not necessarily work with custom filters?

Regards

Patrick

Comments

urbanarpad’s picture

Title: Views Fusion not compatible with imagefield filter? » Views Fusion not compatible with imagefield filter? (or maybe imagefield altogether)

I think this can be taken a little further. I think that Fusion is not compatible with the imagefield period. I'm no expert but it looks like image field is the only one that is stored by fid and not value??

I have a filter that merges a view of a "Image" content type that has an image field with usernode. I had a user profile (using nodeprofile) fused to the usernode and it worked fine. Now I just have the Image-type node fused and I get this:



    * warning: array_merge() [function.array-merge]: Argument #2 is not an array in /var/www/myfishingfacts/modules/views_fusion/views_fusion.module on line 404.
    * warning: array_merge() [function.array-merge]: Argument #2 is not an array in /var/www/myfishingfacts/modules/views_fusion/views_fusion.module on line 405.
    * warning: array_merge() [function.array-merge]: Argument #2 is not an array in /var/www/myfishingfacts/modules/views_fusion/views_fusion.module on line 407.
    * warning: array_merge() [function.array-merge]: Argument #2 is not an array in /var/www/myfishingfacts/modules/views_fusion/views_fusion.module on line 408.
    * warning: array_merge() [function.array-merge]: Argument #2 is not an array in /var/www/myfishingfacts/modules/views_fusion/views_fusion.module on line 409.
    * warning: Invalid argument supplied for foreach() in /var/www/myfishingfacts/modules/views/views_query.inc on line 584.
    * warning: Invalid argument supplied for foreach() in /var/www/myfishingfacts/modules/views/views_query.inc on line 584.
    * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AS node_nid FROM node node LIMIT 0, 4' at line 1 query: SELECT DISTINCT(node.nid), node.title AS node_title, node.changed AS node_changed, AS node_nid FROM node node LIMIT 0, 4 in /var/www/myfishingfacts/includes/database.mysql.inc on line 172.

I looked at this:

mysql> select * from views_fusion;
+-----+------+-------------------+
| vid | mvid | uses              |
+-----+------+-------------------+
|  25 |   26 | nodefamily_parent | 
|  27 |   34 | nodefamily_parent | 
+-----+------+-------------------+
2 rows in set (0.00 sec)

Where vid:27 is my usernode and vid:34 is my Image-type node.

Then this table:

mysql> select * from view_tablefield where vid in ( 25,26, 27,34);
+-----+-----------------------+-------------------+-------+-----------------------------------+----------+-------------+---------------------------+----------+
| vid | tablename             | field             | label | handler                           | sortable | defaultsort | options                   | position |
+-----+-----------------------+-------------------+-------+-----------------------------------+----------+-------------+---------------------------+----------+
|  34 | node_data_field_image | field_image_fid   |       | content_views_field_handler_group |        0 |             | profile_thumbnail_default |        0 | 
|  26 | node_data_field_state | field_state_value |       | content_views_field_handler_group |        0 | 0           | default                   |        2 | 
|  25 | usernode_users        | picture           |       |                                   |        0 |             |                           |        0 | 
|  26 | node_data_field_name  | field_name_value  |       | content_views_field_handler_group |        0 | 0           | default                   |        0 | 
|  26 | node_data_field_city  | field_city_value  |       | content_views_field_handler_group |        0 | 0           | default                   |        1 | 
|  27 | node                  | title             |       | views_handler_field_nodelink      |        0 | 0           | link                      |        1 | 
|  27 | node                  | nid               |       |                                   |        0 | 0           |                           |        0 | 
+-----+-----------------------+-------------------+-------+-----------------------------------+----------+-------------+---------------------------+----------+
7 rows in set (0.00 sec)

The only difference I see between the one working and the one not working is that the field column is field_image_fid instead of field_name_value. Maybe that's the issue?

In my merged view, the only field presented is the image field but I am filtering on Node type and Taxonomy term.

urbanarpad’s picture

EUREKA!

While this issue still seems like undesirable behavior, the obvious (obvious now) solution is to merge INTO the node with the image field. And it works. I now have a content type with a single imagefield field that has usernode fused in and then user profile is fused into usernode. Ahhh. Sweet Drupally goodness.

urbanarpad’s picture

Category: support » bug

I take it back: no "eureka" because with the image view on the left side, I can't display the fused view the way I want. The image view has to be on the right and that just doesn't work. I'm going to open a new issue as a bug.

urbanarpad’s picture

Category: bug » support