Can’t use URL parameters in category archive

Hi
Same problem here. We are using a lot of custom query parameters on our web sites. When we updated to 3.2.2 on category page it redirects to basic category.
We downgraded plugin to lower versions and it works ok

thanks

• This reply was modified 2 years, 6 months ago by Digital2.

We are facing an equivalent issue. After updating to version 3.2.2 and viewing on all category pages we are getting: ERR_TOO_MANY_REDIRECTS. The single posts are working fine. Where we can get Polylang 3.2.1?

Thanks

• This reply was modified 2 years, 6 months ago by mauki.

@mauki we used WP Rollback to quickly move between versions: https://it.www.ads-software.com/plugins/wp-rollback/

@andreabaino
Many thanks. We will roll back from one of the backups. Which type of Polylang are you using. Free or any of the paid ones?

On these 2 websites I linked we’re using the free version but we also use the Pro one (on WooCommerce websites) and I can confirm the problem is still there.

We are back to 3.2.1 and everything is working fine.

Hi All,

Ran into same issue in category archive when using string query parameter with date in (ex. en/2022/?cat=843) Polylang redirects(301) to the category page but shows all years instead of just 2022 and query string paramater disappears.

Anyone fixed this or still running on old polylang version?

Hello @lukasz, we are now using the current version (3.2.8) and everything works as expected.
Your URL does not seem to be a category URL but a archive url with a cat parameter: I think WP itself redirects to the category page due to the cat parameter.

Thanks for getting back @andreabaino !

It’s polyalng redirecting, even in the response header it states x-redirected-by: Polylang.

Also as soon as I disable Polylang it works 2022/?cat=843.

So I rollback to find which version this began in and found it started at 2.9

Now in the changelog the most suspect change is with the taxonmoy terms:

`= 2.9 (2020-12-07) =

* Fix canonical redirect for taxonomy terms

I’ll open another support thread as this sounds like different issue.