Archive navigation problem

Hello Chouby.

The problem with “/category/name/page/1” is still present on Polylang 0.9.5.5

Test case:
http://www.voiceoverportugal.com/pt/cat/video
http://www.voiceoverportugal.com/pt/cat/video/page/1

The second URL is not redirect to first one.
WordPress Multisite 3.4.2 / Polylang 0.9.5.5

Thank you and keep it up 🙂

No navigation plugins, just the good old default “paginate_links()” function in my archive.php template:
http://codex.wordpress.org/Function_Reference/paginate_links

This function generates those nice “prev,1,2,3,…next” buttons to navigate archive pages. When you go to “/category/name/page/2”, the link to the first page becomes “/category/name/page/1”. WordPress detects this and automatically redirects to “/category/name” (301 permanent)

I believe Polylang somehow avoids this redirection. Could it be the case?

We can avoid the “page/1” url with this simple trick:

$big = 999999999;
$nav_pages = paginate_links( array(
    'base' => str_replace( $big, '%#%', get_pagenum_link( $big ) ),
    'format' => '/page/%#%',
    'current' => max( 1, get_query_var('paged') ),
    'total' => $wp_query->max_num_pages,
    'prev_text' => '«',
    'next_text' => '»',
    ) );
$nav_pages = str_replace('/page/1', '', $nav_pages);
echo $nav_pages;

But it will still exist 2 URLs for the same page, which WordPress by default solves.
Try it: http://www.hipersuper.pt/category/producao/page/1/
This site doesn’t have Polylang and so the redirection takes place.

Thank you for looking into it.

Hello Chouby.

My “str_replace” fix doesn’t make any redirection, it only avoids the “page/1” link to be created. But all those who use these function in “archive.php” or “index.php” templates, will get the “page/1” link, unless they implement this simple workaround.

Slight improvement 😉

if(get_query_var('paged') > 1) $nav_pages = str_replace('/page/1', '', $nav_pages);

By the way, paginate_links() function has no hooks to make it other way…

Anyway, are you planning on looking how to make “/pt/category/name/page/1” links redirect to “/pt/category/name”, without this workaround?

It’s not such a big deal, but let me know if you can work on that. Maybe in the process you can find more WordPress automatic redirections that you missed.

Thank you Chouby 🙂

Still not working with Polylang 0.9.6.
Test: http://saraperes.com/pt/blog/trabalhos-recentes/page/1

Permalink structure: “/%year%/%postname%”

Category base: “blog”

Yes I’m using a static front page.

Polylang Settings:
– [checked] When the front page is visited, set the language according to the browser preference
– [checked] The language code, for example /en/, is added to all urls when using pretty permalinks.
– [checked] Remove /language/ in pretty permalinks. Example: http://saraperes.com/en/
– [unchecked] Hide URL language information for default language
– [checked] When using static front page, redirect the language page (example: http://saraperes.com/en/) to the front page in the right language
– [unchecked] Allow to synchronize categories, tags, featured image and other metas between translations of a post or page (What is this option for, by the way?)

Hope you can fix it with not too much trouble 🙂

Thank you!