When I click on the nodequeue tab I get this message:
"No valid queues for this node? You shouldn't even be here if this is true."
Watchdog reports these 2 errors:
-->implode(): Bad arguments. in /modules/nodequeue/nodequeue.module on line 114.
Line 114 is "$qids = implode(",", $qidlist);" and I think @qidlist is empty or NULL, since (I guess) $roles is empty or NULL. If I hardcode $roles to a certain id it works.
-->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 ') GROUP BY nq.qid ORDER BY nq.title' at line 1 query: SELECT nq.qid, nq.title, nq.size, count(nqn.nid) AS numnodes FROM nodequeue_queue nq LEFT JOIN nodequeue_types nt ON nt.qid = nq.qid LEFT JOIN nodequeue_nodes nqn ON nqn.qid = nq.qid WHERE nt.type = 'blog' AND nq.qid IN () GROUP BY nq.qid ORDER BY nq.title in /includes/database.mysql.inc on line 120.
I guess it is the "nq.qid IN ()" which is the error, an error which follows from error 1.
So what is the problem here?
I am using Drupal 4.7.0 and I am also using the module Simple Access.
Comments
Comment #1
bengt commentedIs seems to work if I am logged in as *not* UID 1 (isn't this issue already fixed?)
Comment #2
merlinofchaos commentedOh nuts, I fixed the UID 1 thing incorrectly. I'll try to get to this soon.
Comment #3
bengt commentedAlso, in function nodequeue_fetch_back this code is wrong: $size = db_result(db_query("SELECT size FROM {nodequeue_nodes} WHERE qid = $qid"));
It should be: $size = db_result(db_query("SELECT size FROM {nodequeue_queue} WHERE qid = $qid"));
But even if I change that, it wont work. If I have a size of 0, what does a $from value = -1 mean? And if I have 99 as size, but so far only have 1 node in the queue, what does a $from value = 98 mean? Anyway, the function nodequeue_fetch_back doesn't work, even if I change {nodequeue_nodes} to {nodequeue_queue}. But if I change the statement to $size = db_result(db_query("SELECT count(*) FROM {nodequeue_nodes} WHERE qid = $qid")); it works as expected.
Comment #4
rksubbu commentedIs there an interim solution for this? Thanks.
Comment #5
merlinofchaos commentedThis has been fixed, but I never marked this issue. My apologies.
Comment #6
(not verified) commentedComment #7
sethcohn commentedCurrent 4.7 code (and others?) has the wrong line in fetch_back, causing the SQL error.
Fix in comment #3 (whcih works) needs to be applied.
Comment #8
merlinofchaos commentedFixed in 4.7-dev.
Comment #9
(not verified) commented