error on with fused view
Sharique - October 30, 2007 - 18:34
| Project: | Views Fusion |
| Version: | 5.x-1.2 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I have two views
1. is school listing
fields
node id
node title
Arguments
node id
2 is user listing
fields
Usernode: Name
Usernode: Picture
Arguments
Nodefamily: Parent ID
Node fusion
school_listing school_user nodefamily relation: parent - child
I'm getting following error
user warning: Unknown column 'v14node.nid' in 'field list' query: SELECT v14node.nid, v14usernode_users.name AS v14usernode_users_name, v14usernode_users.uid AS v14usernode_users_uid, v14usernode_users.uid AS v14usernode_users_picture FROM node node INNER JOIN usernode v14usernode ON v14node.nid = v14usernode.nid LEFT JOIN users v14usernode_users ON v14usernode.uid = v14usernode_users.uid LIMIT 0, 10 in E:\Install\xampp\htdocs\haiti\includes\database.mysqli.inc on line 151.also I'm not able to use " summery sorted as view" in school listing view for node id argument.
-
#1
I am having the same problem. I tried disabling modules one at a time, and simplifying nodes and views to bare essentials, but the problem did not go away.
Here is the error message:
user warning: Unknown column 'v8node_created_created' in 'order clause' query: SELECT node.nid, node.created AS node_created_created, v8node.nid AS v8node_nid, v8node.created AS v8v8node_created_created 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 WHERE (node.status = '1') AND (node.type IN ('test1')) AND (node.uid = '1') AND (v8node.status = '1') AND (v8node.type IN ('test2')) AND (v8node.uid = '1') ORDER BY node_created_created DESC, v8node_created_created DESC LIMIT 0, 10 in /home/xxx/public_html/yyy/includes/database.mysql.inc on line 172.The query seems to be looking for data in a non-existent table, "v8node".
Here is a possible clue.
In the "views_view" table, the vid for the parent-view is 9, and the vid for the child-view is 8. So perhaps that's where the "v8" prefix is coming from.
CONFIGURATION DETAILS
=====================================
Database
----------
The "views_fusion" table contains the following row:
vid ........ mvid ....... uses9 ........ 8 ........nodefamily_parent
Installed Modules
-----------------
Views Fusion: 5.x-1.2
Views: 5.x-1.6
Node Family: 5.x-1.4
Node Profile: disabled
Advanced Profile Kit: disabled
imagefield: disabled
pageroute: disabled
(I have other modules installed as well, but these are the ones that I guessed might be relevant.)
Node Types
------------
test1:
contains a single text field
maximum population: 1
test2:
contains a single text field
maximum population: 1
Node Family
-----------
test1 is parent of test2
Views
------
view1:
- fields: none
- arguments: none
- filters: nodetype IS ONE OF test1
view2:
- fields: none
- arguments: none
- filters: nodetype IS ONE OF test2
Views Fusion:
- primary view: view1
- fused view: view2
- using: nodefamily relation: parent - child
Any thoughts as to what the problem might be?
Thanks much!
Mindy
#2
I had a similar problem, and found that removing arguments and sorting from the second view made it work (actually, I cloned the second view, removed the arguments, renamed it, and used that, to preserve the second view on its own). In my case, I didn't really need arguments in the second view when fusing them, as the parent of the node relations was in fact the argument in the second view. In other cases, I can easily imagine needing to apply arguments to the second view, and I don't know how to get around that.