This module is able to work only with one pager at a time. In an event when there are two or more pagers on a single page, only the first one will be usable.

Widgets generated for all other pagers will control the first pager only.

Comments

wuinfo - bill wu’s picture

wuinfo - bill wu commented

Core pagination has same problem.

Testing case 1:
Set home page to /node
Enable frontpage default view. -> Add block view and show title of nodes with full pager. Disable ajax of the view.
Add the block to front page.

Now we have 2 pagers on home page. Change page on one pager will affect the other pager.

Testing case 2:
Have home page set to /node
Enable frontpage default view. -> Add block view to just show title of nodes with full pager. Enable ajax of the view.
Add the block to front page.

Change page on view block with Ajax, (Works Fine)
Change page on main pager, view block pager was change too.(Problem here)

20th’s picture

20th commented

There is this thing called "pager id", determined, for example, by the third parameter to the pager_default_initialize() function.

By default, all pagers that you place on a page have ID 0, as the result, all widgets indeed control the same pager. The problem here is that there is no API to automatically give different IDs to different pagers.

However, with Views it is possible to manually set ID of a pager if you know that there will be more that one on a page. Here is a description of how you can do it.

But this module still does not work even if you manually give different IDs to pagers.

wuinfo - bill wu’s picture

wuinfo - bill wu commented
Status: Active » Needs review

It is fixed and committed.

wuinfo - bill wu’s picture

wuinfo - bill wu commented
Version: » 7.x-1.0-rc1
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.