cannot exclude items based on taxonomy

i would say its the other way round - it works if your nodes have another term, else it doesn't.
so this seems to be a duplicate of this issue I created recently.

please test the patch from this issue and report if it fixes your problem too.

Hell, I'm getting this error too. Using "Is None Of" does nothing for me, and yes, the items I'm trying to exclude have terms in other vocabularies.

BTW... how can I find out what my view's resulting query looks like?

I tried the patch fago made for the other issue, BTW, and as yogadex predicted, it did nothing to fix this problem.

Yesterday I put in a fix that might fix the exclusion issue.

I agree, this is still not working correctly.

I can take a look on this during the next days.

Hi,

I don't want to teach grandma to suck eggs - but that SQL looks completely wrong to me. Surely it should look something like :

SELECT node.title, node.nid, count(node.nid) as num_nodes FROM node node
WHERE (node.type IN ('ocp_project'))
AND NOT EXISTS
(
SELECT 1
FROM term_node
WHERE term_node.nid = node.nid
AND term_node.tid = '1025'
)
GROUP BY node.nid LIMIT 0, 5

Of course I have no idea how to get the code to generate this ... :-)

Cheers

David.

attached a patch, whitch should fix it. please test

I removed the option of "depth", because I can't see any use for it. If we already filter for term ids, what should the additional depth setting do? Any term id has a fixed depth generated by it's position in the tree, so what should this additional depth filter do!?
Or is there any use case I missed?

Views doesn't do sub-selects.

No, the depth option is very important.

If I have a taxonomy hierarchy that looks something like this:

plants -->
flowers -->
petunias
marigolds
dandilions
trees
oak
maple

And I want to get all 'trees' I can search for 'tree' with a depth of 1; then anything with 'oak' or 'maple' will get hit. (Yes, this is probably going to suck when using exclusion).

In this case, depth really means 'find any node with term tree, or any node with a term that is 1 step down from tree'.

ah right, a really useful feature.

Here is a new patch which keeps the depth option. However there is still no support for using the depth option with the NOR operator, because this is not possible without doing subqueries.

please test :)

Seems to work. Thanks for the fix!

adding depth exclusion does not fix the original problem outlined this issue, right?

depth exclusion isn't implemented. It's quite difficult to accomplish.

sorry, i'm lost. patch above suggest depth exclusion existed or was implemented in the patch.

depth exclusion was not the original point of this (fixed) issue, and that's what i'm asking about.

if you create a view that includes a filter of 'is none of [vocab]', it simply won't exclude content that has additional vocab applied to it. i understand that views does not support sub-selects, but i was wondering if there were some other way to achieve the goal of completely excluding nodes with tags from a certain vocab.

i think the author of this post would be interested too.

i'm reviewing http://drupal.org/node/42609 to see if i can achieve this within a module that uses the views api, but it seems like i'm limited to small fragments of queries and can't insert a subselect "manually".

hrmmm...

I thought about the vocabulary & NOR filter, when I wrote this patch. But I wasn't able to find a way to do it without subqueries. If you can think of an sql statement which does it, post it..

So the NOR filter with vocabulary is not totally correct. NOR and depth filtering is also not possible without subqueries.