Compatibility with contextual filter defaults on Search API Views

hi,

i'm changing the issue title, hope this is more accurate as its about compatibility with https://drupal.org/project/global_filter

i haven't used this module but if it uses HTTP POST for setting filter values this might reset the pretty path.

to narrow down the problem, have you tried if everything works for you without the global filter?

So, I did some research into this...

The problem has little to do with Views Global Filter.
It is because Facets Pretty Paths is unable to honour CONTEXTUAL FILTER DEFAULTS. Instead Facets Pretty Paths obliterates any contextual DEFAULT arguments that may be present in the URL.
If Facets Pretty Paths can be made to accept contextual filter defaults, then this also solves the issue with Views Global Filter, because Views Global Filters ARE contextual default filters.

Steps to reproduce.
You may uninstall Views Global Filter, as it has nothing to do with the issue.
Create in the search View (let's say at path /src) a contextual filter for Taxonomy Term field_city and provide a Fixed default value of, say, 2 (e.g. London).

Without Facets Pretty Path, the URL: /src?f[0]=field_category:5 WORKS (taxonomy term will be used as the 2 is the default contextual argument set up in the View)
With Pretty Path URL switched on: /src/category/Cinema Tickets-5 DOES NOT WORK: the word 'category' will be interpreted by the View as the first contextual argument, i.e as the value to be used for field_city, to contextually filter on. 'category' is of course not a valid taxonomy term id for field_city.

To try and get around this I introduced Global:Null filter and "Indexed Node: Category" as contextual filters preceding the field_city contextual filter, so as to cover the 3 elements of the URL path generated by Facets Pretty Paths. But this doesn't seem to work on Facets Pretty Path URLs like /src/category/Cinema Tickets-5 except for the URLs /src/category, /src/category/all or /src/category/all/term_id (the taxonomy term field_city is the final contextual argument, defaulting to 2).

To solve this the Views contextual filter for "Indexed Node: Category" needs to be made to understand the "Cinema Tickets: 5" format.
I guess this is best implemented in one of the Search API or Facet API (sub)modules.

thanks for looking into this rik!

so this boils down to the fact that pretty path aren't compatible with views contextual filters as both are passed as arguments right?

obviously this causes conflicts between the path logics of views contextual filters + facet api pretty paths. you still can use any GET paramenter based filters. (this might be a good candidate for an FAQ :) )

i think we might even want to remove "defaults" and "search api views" from the issue title, as this should be valid for any contextual filter being used with views.

@dasjo, #7

Yes, Josef, your summary of the issue is correct except for the the bit "this should be the case for any contextual filter being used with Views".

If I remember correctly, it handles contextual filters that are present in the URL correctly: it appends the contextual filter to the URL first and then appends the "/category/Cinema Tickets-5 bit after that -- so that's fine.
It's just where the contextual filter is omitted (defaulted), the Pretty Path takes its place and thus destroys the contextual filter default. That's why I tried the approach in #6, introducing a "dummy" contextual filter to skip the /category part and then have the original contextual filter default applied as the last (third) in the list. But unfortunately the second contextual filter /Cinema Tickets-5 is not understood in that case.

Rik

ok thanks. i'd like to provide some more background info for anybody interested in fixing this problem:

pretty paths tries to remove any path segment that can be detected and then leaved the remainder to views as its base path.
we have had quite some attempts to get this right, see #1861786: Fix base path issues

also see the logic for path processing in pretty paths

I just re-read the comment from #10

It's just where the contextual filter is omitted (defaulted), the Pretty Path takes its place and thus destroys the contextual filter default. That's why I tried the approach in #6, introducing a "dummy" contextual filter to skip the /category part and then have the original contextual filter default applied as the last (third) in the list. But unfortunately the second contextual filter /Cinema Tickets-5 is not understood in that case.

This interference can't really be avoided within the module, so updating the status.

Feel free to report if you have further ideas.

etc