[Explained] No correct canonical and base urls after filtering

Hello

Also we have issue with how many searched / filtered pages we will have in google index

Here are some discussions

moz.com/community/q/rel-canonical-for-filter-pages
moz.com/community/q/do-you-need-a-canoni...rch-and-filter-pages

About allowing this via configuration,
- we could just add 1 more option to the existing parameter 'Add rel-canonical'
- or we could add a configuration, add rel-canonical when only 1 filter is active and add 'No-index' (Google will not index the page) when more than 1 filter is active

ggppdk wrote: Hello

Also we have issue with how many searched / filtered pages we will have in google index

Here are some discussions

moz.com/community/q/rel-canonical-for-filter-pages
moz.com/community/q/do-you-need-a-canoni...rch-and-filter-pages

About allowing this via configuration,
- we could just add 1 more option to the existing parameter 'Add rel-canonical'
- or we could add a configuration, add rel-canonical when only 1 filter is active and add 'No-index' (Google will not index the page) when more than 1 filter is active

Hmmm...
I do not know how it will be more correct.

I use prefiltering by types: Android, Windows, macOS, iOS.
So I need rel-canonical for 1 active filter by type.

So, this way is good -

- we could just add 1 more option to the existing parameter 'Add rel-canonical'

When you can add this?

Helllo

i ll treat as bugfix, will add it in v3.2.1.13 , (yes we will have 1 more release for in v3.2.n.n)

but i will ask that you test this change (by using v3.2.13-dev) or v3.3.0-dev

I have already made an implementation for adding filters up to 1 or 2 to the url-canonical
- will test and commit today or on friday

also thinking to add configuration for adding "no-index" (Search engines will ignore not index the page) when more than 2 filters are active

Thanks.
I will test with v3.3.0-dev.

I have checked tag page with filter by type and without filter.
It displays error

0 __clone method called on non-object

Hello

Fixed it, please re-update to v3.3.x-stable branch