Category pagination issue with Polylang

  • Resolved ecstoreweb

    (@ecstoreweb)


    2 weeks, 5 days ago

    We use Polylang Pro and Polylang for WooCommerce and we have issues with pagination in the product category archive.

    If we set the category slug to “WooCommerce Default,” pagination works correctly in all languages. If we use the “Category Slug” option from tour plugin, pagination only works in the site’s primary language.

    In other languages, the URLs for the product category archive pages include the page number in the slug (e.g., http://www.mysite.com/en/categoryname/page/15/), but the page displayed is always the first page and the Polylang alternative URL doesn’t include the pagination part.

    Since pagination works fine when we use the default WooCommerce slug for product categories and not when we use the plugin’s slug, I wanted to know if there are any known compatibility issues with Polylang and if there is a fix.

    Thanks

Viewing 2 replies - 1 through 2 (of 2 total)
  • Robert Fortaleza

    (@robfrtlz)

    2 weeks, 4 days ago

    Hi @ecstoreweb,

    Thanks for the detailed explanation, that really helps clarify what’s going on.

    What you’re experiencing is, unfortunately, a known limitation when using custom category slugs from our plugin together with Polylang (and Polylang for WooCommerce). Pagination handling in multilingual setups can be quite sensitive, and Polylang doesn’t always fully recognize or translate custom rewrite rules introduced by third-party plugins.

    That’s why things work as expected when using the default WooCommerce category base, but break when switching to the plugin’s custom slug, especially on paginated URLs in secondary languages.

    At the moment, we don’t have a built-in fix for this specific compatibility issue. As a workaround, we recommend sticking with the default WooCommerce category slug if multilingual pagination is critical for your setup.

    That said, I’ll log this with our team as a compatibility improvement request so we can further evaluate it.

    Thanks again for reporting this, really appreciate the thorough testing on your end!

    Thread Starter ecstoreweb

    (@ecstoreweb)

    2 weeks, 4 days ago

    Thanks for your reply

    I hope this incompatibility will be resolved in the future.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.