I upgraded from D4.6 to D6.12 last year. Site has been offline until now. Just noticed that anonymous gets errors (see below) when they click on a taxonomy term associated with a node. I updated views to 2.10 but that didn't resolve it. Since it is pre-D6.14, the distinct patch doesnt fit as a solution. I can't go to PHP5.x just yet and D6.16 doesnt seem to play nice on PHP4.x.
What I find interesting is, the taxonomy link should work without calling Views, right? So why is the views module being blamed?
Does anyone have any ideas or tips on how to resolve this?
* user warning: Unknown column 'node.nid' in 'on clause' query: SELECT COUNT(*) FROM (SELECT DISTINCT(node.nid) AS nid FROM node node WHERE (node.status <> 0 OR (node.uid = 0 AND 0 <> 0) OR 0 = 1) AND (node.vid IN ( SELECT tn.vid FROM term_node tn INNER JOIN node_access na ON na.nid = node.nid LEFT JOIN node n ON node.nid = n.nid WHERE (na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 0 AND na.realm = 'og_public'))) AND ((n.moderate != 1)) AND ( tn.tid = 11 )) )) count_alias in /home/foo/bar.com/html/sites/all/modules/views/includes/view.inc on line 745.
* user warning: Unknown column 'node.nid' in 'on clause' query: SELECT DISTINCT(node.nid) AS nid, node.sticky AS node_sticky, node.created AS node_created FROM node node WHERE (node.status <> 0 OR (node.uid = 0 AND 0 <> 0) OR 0 = 1) AND (node.vid IN ( SELECT tn.vid FROM term_node tn INNER JOIN node_access na ON na.nid = node.nid LEFT JOIN node n ON node.nid = n.nid WHERE (na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 0 AND na.realm = 'og_public'))) AND ((n.moderate != 1)) AND ( tn.tid = 11 )) )ORDER BY node_sticky DESC, node_created DESC LIMIT 0, 10 in /home/foo/bar.com/html/sites/all/modules/views/includes/view.inc on line 771.
Comments
I just did a test. I disabled
I just did a test. I disabled (not uninstalled) views on my site. Now the link to the taxonomy term works. What does views do to the taxonomy module such that when you click on a node taxonomy term, you get a view error?
HELP!
part of the issue identified
Thanks to Jody from Zivtech - the following issue was revealed.
Apparently there is a view that is typically disabled called taxonomy_term. Somehow that got enabled and it has a problem. If enabled, it will override what taxonomy.module shows. So, disabling it solves the immediate issue.
Next step, find out why it isnt working. Could be an upgrade legacy issue - more work ahead.
Hi, I got this by updating to
Hi,
I got this by updating to latest 3. rc2 views. May be views is becoming stricter?
greetings, Martijn