'Filter to items that share all terms' doesn't do so

Hi suldan,
Did you get this working?

Thanks

Wow, I came here looking for a solution, but my problem both options filter to all.

I would like to reproduce the problem locally. Can you please guide how to set up the view and what is expected behavior and what we have instead?

@ygerasimov
You are doing really great work in the issue queue. Feel free to set the status to "postponed (needs more info)".
If noone responds for a long time we can close them all at once, which happens for many issues.

Are you sure you set the filter to 'and' not, 'or'? Check your settings in the filters.

I could reproduce the bug. Filter criteria is set to 'AND', same configuration as in comment #5. Any solution is highly appreciated.

Just ran into this myself. What you're missing is under the "More" tab on the contextual filter at the bottom of the modal window, select "allow multiple values".

Just for you to know, I yet have the same problem, both options do the same 'Filter to items that share all terms' and 'any terms'.

My workaround is setting two contextual filters, one for every vocabulary.

This is actually not working for me.

I have 'Filter to items that share all items' and 'allow multiple values' selected.

If I inspect the args in a preprocess_views_view function I see that the args have the following:
3,5,18

Unfortunately, it is matching any item instead of matching all.

Not trying to hijack the thread here, but both dbrouard and myself have the same issue.

When I select 'Filter to items that share all terms' and 'Allow multiple' it still shows items that match any (OR instead of AND).

My use case:

Taxonomy:

Automobile
- Car
- Sedan
- Coupe
- Truck

If I have my view block on a node with "Car, Sedan" selected my view will return results from nodes tagged with "Car", "Car, Coupe", etc. It does not limit to items with both "Car" AND "Sedan".

Attaching screenshots, here is the query:

SELECT DISTINCT node.promote AS node_promote, field_data_field_popularity.field_popularity_count AS field_data_field_popularity_field_popularity_count, node.nid AS nid
FROM 
{node} node
INNER JOIN {field_data_field_type} field_data_field_type ON node.nid = field_data_field_type.entity_id AND (field_data_field_type.entity_type = 'node' AND field_data_field_type.deleted = '0')
LEFT JOIN {field_data_field_categories} field_data_field_categories ON node.nid = field_data_field_categories.entity_id AND (field_data_field_categories.entity_type = 'node' AND field_data_field_categories.deleted = '0')
LEFT JOIN {field_data_field_popularity} field_data_field_popularity ON node.nid = field_data_field_popularity.entity_id AND (field_data_field_popularity.entity_type = 'node' AND field_data_field_popularity.deleted = '0')
WHERE (( (field_data_field_categories.field_categories_tid IN('3', '5', '18') ) )AND(( (node.status = '1') AND (node.type IN  ('poi')) AND (field_data_field_type.field_type_value = 'discover') )))
ORDER BY node_promote DESC, field_data_field_popularity_field_popularity_count DESC
LIMIT 5 OFFSET 0

As you can see, it is selecting any items in an array of IDs:
WHERE (( (field_data_field_categories.field_categories_tid IN('3', '5', '18')

Found the issue.

I was using a taxonomy field as my contextual filter (field_category).

By switching to a 'Has taxonomy term ID' contextual filter, this functionality worked fine.