wrong url arguments on pager

General close of issues over 6 months old without activity.

This issue is still present. It can be reproduced by creating a View with Term ID arguments with Allow multiple terms per argument option enabled. Enable Ajax paging. If we present arguments as 1+2+3+4+5, clicking on a pager takes us to 1 2 3 4 5?page=1, but clicking on next or previous page will take us to a blank page (because arguments became 1%202%203%204%205?page=1).
This issue appears only when ajax pager is enabled.

If this is still a problem, can you update to what your version is, what other modules you might be using in conjunction, etc?

I am using Views 2.11, CCK 2.8 and Views carousel 1.0

I haven't tested this but have you tried to use "," rather than "+" between each term ID? I seem to recall there was a difference but, for the life of my tired brain, I can't remember what it is. Anyone?

yaoweizhen,
did you try Shane Birley's suggestion?
closing from lack of activity. please feel free to reopen if you still need help.

this issue represent in my site. (views 6.x-2.12)

Shane Birley's suggestion can't apply to me, because I want to get list by using taxonomy OR(not AND).

Anyone has any idea to workaround?

I think this issue is caused by "double encode" of view_path.
When the issue is reproduced, I can saw double encoded argument like "1%202C2%202C3%202C4%202C5".

I attached patch for views-6.x-2.12, it works on me.

Thank you blauerberg, #9 fixed same problem in D7.

Sadly this patch doesn't apply anymore, but also manual changing of this lines made the wheel spinning into infinity,
no idea why...

@dereine

What version do you use?
I attached new patch for views-6.x-2.16, it works on me.

If patch does not work, please try to clear all cache before accessing page.

Bump up!

This is a really good thing to do - even for Views 3! I've been scratching my head on the following scenario:

1. AJAX pagination is enabled for a Views table result
2. View display accepts multiple taxonomy term id's as arguments for a Contextual Parameter
3. Initial "pick a page number" or "prev/next" and the pagination works...
4. ...but continued use of the pagination fails because the comma in the URL of the multiple term id list is encoded to %2C and and Views doesn't decode this as an argument before trying to use it. So the creation of the query fails and no result is returned.

I've created a trivial patch which should work for Views 3.

Ok, ignore that patch - use this one.

The patch in #15 works in our Views 7.x-3.0-rc3

The patch indents the line too much, but other than that I think this looks reasonable.

Patch revised to use space-based indenting instead of tab-based indenting (oops!)

Changing status to "needs review".

.

The patch so looks fine.

Is there something not quite right that is holding up the acceptance of this patch?

Well the only problem is the lazyness of the committer ....

Committed to 7.x-3.x and mark as to be ported for d8, because with the HTTP Kernel this might be different.

Music to my ears! Many thanks!

We haven't finished removing usage of $_REQUEST, might as well commit this as is now.

Sure this makes sense, committed to 8.x-3.x