Thread

Hi all,

I’ve got a problem with the {auto_path} variable in my multi-post pagination pages. The “next” link includes an extra “/” for page 2 onwards, which although looks wrong with “//” in the url, still does navigate ok. You can see this happening at:

http://www.ipcn.co.uk/en/news/P1

The main problem I’m having is that on a deeper page where I’m running the “archives” and “category” requests through the “news” index page, pagination behaves differently, in that the “next” links work fine, but “previous” links leave the “/” out entirely! So that the url page segment e.g. “P0” or “P1”, merges with the previous segment. You can see this happening at:

http://www.ipcn.co.uk/en/news/archives/2011/P1

In fact, clicking “next” and “previous” several times turns the last segment into something like “2011P1P0P0P0P0P0”!

Can anyone help figure out what is wrong?

One possible clue is that the site is bilingual, and I amended the index.php pages according to the following:
http://expressionengine.com/wiki/Multi_language_site_alternative/

Thanks,

Mark

Hi Mark,

Which version and build of EE are you using? Can you please test this with your .htaccess rewrite rules disabled?

Cheers

Greg

Hi Greg,

I’m using v2.1.3, Build:  20101220 (which I believe is the latest stable version).

I disabled the .htaccess rewrite rules, and then tried deleting all the contents of the .htaccess file, but it still acts the same. What I can say is that it’s something in the changes made to make it bilingual as per the expression engine wiki link, as if you look at the page without the language url segment (below), the pagination works perfectly:

http://www.ipcn.co.uk/news/archives/2011/P3

Could there be a fix in the index.php files? (the 2 in the additional language folders?)

Thanks in advance for any help!

Mark

Mark ,

After disabling your htaccess. Add index.php back into your General Configuration. Then test

Also try adding paginate_base= parameter to see if that makes a difference

Hi John,

I’d never seen the parameter ‘paginate_base=’ before so gave that a go and managed to make that work! (My bad - should have looked it up, although I only checked the paginate tags in the manual.)

It does what it says in that it sets the base template, but I had initial problems since I needed to put in the segments “archive”, “category” or nothing at all based on the url, into the pagination links (whether the user was looking at the index page or a dynamic filter of archives or categories.

However, it seems ‘paginate_base=’ can also include segment variables and conditionals too.

Superb - thanks again John!

Glad John was able to help. Don’t hesitate to post again as needed.