Global Filter does not filter when a Views relationship is used

Hi CountZero,

Thanks for your interest in Views Global Filter.

Sorry to hear it's not working for you.

You say "The bloc is OK, the links work as expected (appending ?myfield=xxx to the URL)". That suggests to me that you've chosen to use the hyperlinks widget (rather than, say, a drop-down selector) and that you also chose to UNTICK on the Global Filter configuration the option Suppress URL parameters in the links of the links widget. That's ok. It should work with box ticked or unticked, i.e. both cases.

In the Global Filter block, for the driver selection and Views, for the Contextual Filter selection DO NOT PICK "Content: Has taxonomy term ID". You need to pick the taxonomy FIELD. Then all should be fine.

I'm also a little worried about this "Relationship" drop-down in your screenshot.... I don't normally see that... what else is in play on your site...?

Rik

Global Filter is based on Views' contextual filters. Have you tried your setup using a plain contextual filter with a default value or value taken from URL?
Also have you switched to another GF widget, the mechanism is different for hyperlinks.
Rik

Well admittedly I have never tested Global Filter with relationships. I'm just not aware that the format for passing contextual values is different in that case....
Or what the difference is between Preview and live Views...

Guess I'll have to fire up the debugger, create a relationship and look under the hood...

So the reason that the Global Filter Views plugin filters by 'all' (i.e. no filtering) is that as a result of the relationship, the name of the filtering Views field does not match that of the field selected in the global filter block.
I'll see what I can do...

Wrong generated SQL query with relationship.

Original:

SELECT taxonomy_term_data.name AS taxonomy_term_data_name, taxonomy_term_data.vid AS taxonomy_term_data_vid, taxonomy_term_data.tid AS tid, taxonomy_vocabulary.machine_name AS taxonomy_vocabulary_machine_name, taxonomy_term_data_taxonomy_term_hierarchy.tid AS taxonomy_term_data_taxonomy_term_hierarchy_tid
FROM 
{taxonomy_term_data} taxonomy_term_data
LEFT JOIN {node} node_taxonomy_term_data ON (/*inner query*/SELECT nodeINNER.nid AS nidINNER
FROM 
{node} nodeINNER
LEFT JOIN {taxonomy_index} taxonomy_indexINNER ON nodeINNER.nid = taxonomy_indexINNER.nid
LEFT JOIN {taxonomy_term_data} taxonomy_term_data_nodeINNER ON taxonomy_indexINNER.tid = taxonomy_term_data_nodeINNER.tid
/*place for code */
WHERE (( (taxonomy_term_data_nodeINNER.tid = taxonomy_term_data.tid ) ))
ORDER BY nodeINNER.nid DESC
LIMIT 1 OFFSET 0) = node_taxonomy_term_data.nid
LEFT JOIN {taxonomy_term_hierarchy} taxonomy_term_hierarchy ON taxonomy_term_data.tid = taxonomy_term_hierarchy.tid
LEFT JOIN {taxonomy_term_data} taxonomy_term_data_taxonomy_term_hierarchy ON taxonomy_term_hierarchy.parent = taxonomy_term_data_taxonomy_term_hierarchy.tid
LEFT JOIN {taxonomy_vocabulary} taxonomy_vocabulary ON taxonomy_term_data.vid = taxonomy_vocabulary.vid
//---
LEFT JOIN {field_data_field_gorod} node_taxonomy_term_data__field_data_field_gorod ON node_taxonomy_term_data.nid = node_taxonomy_term_data__field_data_field_gorod.entity_id AND (node_taxonomy_term_data__field_data_field_gorod.entity_type = 'node' AND node_taxonomy_term_data__field_data_field_gorod.deleted = '0')
WHERE (( (node_taxonomy_term_data__field_data_field_gorod.field_gorod_value = '1' ))
--//
AND(( (taxonomy_vocabulary.machine_name IN  ('catalog')) )))

Code inside //-- --// must be in the inner query.

Right SQL query:

SELECT taxonomy_term_data.name AS taxonomy_term_data_name, taxonomy_term_data.vid AS taxonomy_term_data_vid, taxonomy_term_data.tid AS tid, taxonomy_vocabulary.machine_name AS taxonomy_vocabulary_machine_name, taxonomy_term_data_taxonomy_term_hierarchy.tid AS taxonomy_term_data_taxonomy_term_hierarchy_tid
FROM 
taxonomy_term_data taxonomy_term_data
INNER JOIN node node_taxonomy_term_data ON (SELECT nodeINNER.nid AS nidINNER
FROM 
node nodeINNER
LEFT JOIN taxonomy_index taxonomy_indexINNER ON nodeINNER.nid = taxonomy_indexINNER.nid
LEFT JOIN taxonomy_term_data taxonomy_term_data_nodeINNER ON taxonomy_indexINNER.tid = taxonomy_term_data_nodeINNER.tid
//--
LEFT JOIN field_data_field_gorod node_taxonomy_term_data__field_data_field_gorod ON taxonomy_indexINNER.nid = node_taxonomy_term_data__field_data_field_gorod.entity_id AND (node_taxonomy_term_data__field_data_field_gorod.entity_type = 'node' AND node_taxonomy_term_data__field_data_field_gorod.deleted = '0')
WHERE (node_taxonomy_term_data__field_data_field_gorod.field_gorod_value = '1' )
--//
AND (taxonomy_term_data_nodeINNER.tid = taxonomy_term_data.tid ) 
ORDER BY nodeINNER.nid DESC
LIMIT 1 OFFSET 0) = node_taxonomy_term_data.nid
LEFT JOIN taxonomy_term_hierarchy taxonomy_term_hierarchy ON taxonomy_term_data.tid = taxonomy_term_hierarchy.tid
LEFT JOIN taxonomy_term_data taxonomy_term_data_taxonomy_term_hierarchy ON taxonomy_term_hierarchy.parent = taxonomy_term_data_taxonomy_term_hierarchy.tid
LEFT JOIN taxonomy_vocabulary taxonomy_vocabulary ON taxonomy_term_data.vid = taxonomy_vocabulary.vid
WHERE (taxonomy_vocabulary.machine_name IN  ('catalog') )

To repair it u can use another view to generate the relationship subquery. And use global filter inside subquery view instead main view.

Thanks for this great module. I have come across this same issue and i am really looking forward to some alternate solution or patch for this issue.I am really struck here..So any pointers will be helpful.

Set to major issue, if you don't mind.

Have you tried the workaround by @divined in #12?

Patches based on the observation in #8 welcome! I have little time at the moment.

Patch anyone?