How to use global filters with other contextual filters?

Hi flbr,

I read my own README and found it is not very clear. So I've just checked into the repository a new version (7.x-1.x-dev) of the module with some code enhancements and this updated section of the README:

Make sure that under "Page Settings" the Path does NOT contain percent signs for arguments that you wish to apply a Global Filter to. In other words, the percent signs in the Path should stop at the first Global Filter. So, if you have one normal contextual filter, followed by one global filter, you'll have one percent sign. When typing the view's path in your browser address bar, append arguments for the normal contextual filters that precede the global filter. Use all to skip a filter: /your-view-with-contextual-filters/all. If you type a URL argument in the position of a global filter, you temporarily override the current global filter value without setting it.

In the context of your /taxonomy/term/% view this means that all you have to do is remove that last /% from the view's Path. This then opens up a slot for the global filter to do its thing.
Normally global filters should be the last ones in the list of contextual filters. However, the "Has taxonomy term ID depth modifier" contextual filter is special and can stay where it is.

BUT....
There is a second issue with the /taxonomy/term/% view... It doesn't use real fields as contextual filters. These "Has taxonomy term ID" contextual filters are kind of global... They operate on taxonomies, but they are not taxonomy fields attached to specific content types, which is what Views Global Filter needs.
So I've improved the code to also offer "Has taxonomy term ID" and "Has taxonomy term ID with depth" as options in a global filter block.

This should get you started with your /taxonomy/term view. Take Global Filter 7.x-1.x-dev for a spin. Only the textfield widget is available at the moment. I'd like to learn, through your testing ;-) whether the new extensions are functionally correct before I put effort in a drop-down select or autocomplete.

If you do not wish your users to type in term ids into the textfield, proceed as follows on the contextual filter configuration pane:

Under WHEN THE FILTER VALUE IS IN THE URL OR A DEFAULT IS PROVIDED
Tick: "Specify validation criteria"
Validator: "Taxonomy term"
Filter value type: "Term name converted to term ID"

Now you can type term NAMEs rather than numbers into the global filter box.

Rik

Hi Gert,
Yes access to your system would be good. And maybe a concrete example of what is supposed to happen when a user clicks/enters something where.
You can contact me personally for that if you wish and we can report a summary back here in this thread.
Rik