Vanilla install, activating smartqueue per user, activating the option "Display User Node Queues on User (profile) pages." This is an error from Views.
* 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 ') ) count_alias' at line 3 query: SELECT COUNT(*) FROM (SELECT DISTINCT(node.nid) AS nid FROM node node INNER JOIN nodequeue_nodes nodequeue_nodes_node ON node.nid = nodequeue_nodes_node.nid AND nodequeue_nodes_node.qid IN () ) count_alias in /var/www/smartqueue/modules/views/includes/view.inc on line 705.
* 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 ') ORDER BY ASC LIMIT 0, 10' at line 4 query: SELECT DISTINCT(node.nid) AS nid, position FROM node node INNER JOIN nodequeue_nodes nodequeue_nodes_node ON node.nid = nodequeue_nodes_node.nid AND nodequeue_nodes_node.qid IN () ORDER BY ASC LIMIT 0, 10 in /var/www/smartqueue/modules/views/includes/view.inc on line 731.
Comments
Comment #1
crashtest_ commentedI am also experiencing the same issue using the latest Nodequeue and Smartqueue Per User.
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 'ASC LIMIT 0, 10' at line 7 query: SELECT DISTINCT(node.nid) AS nid, position FROM node node INNER JOIN nodequeue_nodes nodequeue_nodes_node ON node.nid = nodequeue_nodes_node.nid AND nodequeue_nodes_node.qid = 1 LEFT JOIN nodequeue_subqueue nodequeue_nodes_node__nodequeue_subqueue ON nodequeue_nodes_node.sqid = nodequeue_nodes_node__nodequeue_subqueue.sqid WHERE nodequeue_nodes_node__nodequeue_subqueue.reference = '1' ORDER BY ASC LIMIT 0, 10 in /var/www/sites/all/modules/views/includes/view.inc on line 731.
Comment #2
ezra-g commentedAre you using the dev version or the latest RC?
Comment #3
crashtest_ commentedI am using the latest RC, not dev. Is this addressed in dev?
Comment #4
ezra-g commentedYes, please re-open if this issue is present in the dev release.
Comment #5
crashtest_ commentedI am updated to the latest dev version and am still experiencing this error.