I'm attempting to use the filter "Nodequeue queue: (is none of) (queue name)". I can't seem to get it to remove the nodes from the list that are in the queue I specify. All the view consist of is a filter for content type and a sort of updated time. Any suggestions would be helpful.
Thank you!
Comments
Comment #1
ezra-g commentedCan you export the view and paste it in here inside of code tags?
Comment #2
mnapier commentedSure can. Thank you!
Comment #3
mnapier commentedDid this help any?
Thank you!
Comment #4
yelvington commentedChanging from "user interface" to "code."
Here is the actual example that Mike and I are looking at right now.
Filters:
Nodequeue: Queue "is none of" "lead: story"
Node: Published Equals "Yes"
Node:type "Is One of" Editorial Node
Node: Distinct is distinct
We had to add the distinct select because the query was returning multiple instances of the same node.
With or without that filter, the query returns a node that is CLEARLY in the "Lead: Story" nodequeue.
Here is the generated SQL:
SELECT DISTINCT(node.nid), node.changed AS node_changed_changed FROM {node} node LEFT JOIN {nodequeue_nodes} nodequeue_nodes ON node.nid = nodequeue_nodes.nid WHERE ((nodequeue_nodes.qid NOT IN ('24') OR nodequeue_nodes.qid IS NULL)) AND (node.status = '1') AND (node.type IN ('editorial')) GROUP BY node.nid, node_changed_changed ORDER BY node_changed_changed DESC
Note this: ((nodequeue_nodes.qid NOT IN ('24') OR nodequeue_nodes.qid IS NULL))
Comment #5
yelvington commentedUpdate: Here's where the generated code fails. If a node is in more than one nodequeue, the test evaluates to TRUE even though that's not what was requested in the filter UI.
Not knowing anything about the internals of the module, it's hard to tell if this is specifically a nodequeue issue, or a core Views code-generator issue.
Comment #6
joachim commentedI'm seeing this bug too.
I'm guessing that views can't form the query that would be needed.
What DOES work is the next filter down, "is not in a queue" which I always thought meant "not in ANY queue" but gives a list to choose from.
So reallly, the "is none of" option should be removed. So should "is any of", as it's a single selector so you can't select several things to be in anyway!
Comment #7
OpenChimp commentedI agree that the is none of option is confusing. There's an older issue that demonstrates this same confusion - http://drupal.org/node/247314. If there's no reason to use it, it should be removed so that users will try the "Nodequeue: not in a queue" option.
Comment #8
ezra-g commentedDrupal 5 is no longer a supported core version.