[Explained] No correct canonical and base urls after filtering

Hello

&cc=p exists only to allow our code to send 'can-cache' HTTP headers to proxies / browser
- so it must not be and does not NEED to be in re-canonical URLs

the contents with and without &cc=p (public) are the same !


&p=all (p is text-search word combination, all words, any words, etc)
should appear only if it is not the default value

With new code &p=* should not appear at all
- if it appears it means you have changed it default value, and in that case (yes it should appear in rel-canonical, since we allow searches to be indexed)

the above is not so important unless you create text-search URLs and add them in your views

Hello.
Ok, it's clear about &cc=p

But how to disable ?p=all ?

I open category and choose and filter (not text) and url becomes ?p=all&filter_24[]=0&cc=p

Hello

with the new code if you submit without change the
"word combination" selector

then it should not appear !


Also in most case you can skip/hide the "word combination"
because the default value "require ALL words" is good enough for 90% / 95% of searching cases

ggppdk wrote: Hello

with the new code if you submit without change the
"word combination" selector

then it should not appear !

Also in most case you can skip/hide the "word combination"
because the default value "require ALL words" is good enough for 90% / 95% of searching cases

Hello.

I don't know why it happens, but when I use any filters - URLs contains ?p=all

I configured global settings for that



See this short video

Hello

ok the recent fix / imporvement
works only when the "word combination" selector is shown

but when it is hidden, then it submits the value as a hidden input 'p' field that has as value the default value

Fixed this case too, by removing the not needed input 'p' field
also added 'p' to rel-canonical (when it is present in submit URL)

Now everything works as it should.
I have hidden "word combination" selector and ?p=all not displays!!!

Thank you very much!