Multiple Pagers on Quicktabs Views blocks [#2352187]

If I change the Pager ID to be unique for each view that is in quicktabs, should this fix content breaking when load more is pressed? I have seen other issues saying this is known that multiple pagers in quicktabs breaks everything; however, I am curiuos if this fixes the issue?

I have tried to change the Pager ID to 1, 2, 3, 4, etc. for each of the views I am showing in quicktabs. It seems to work for two of the views, but then it does not for others.

Also, changing the Pager ID prevents waypoint from triggering infinite scroll. Do I need to add custom js to trigger the waypoint infinite scroll for these custom Pager IDs?

Thanks, this module is awesome and I'm having better luck using it than Views Infinite Scroll.

Comments

Comment #1

cthshabel commented 9 October 2014 at 05:51

Okay, this question was somewhat premature. I don't think I was asking the right questions. To clarify for any future readers, I was able to have multiple pagers by increasing the Pager ID. The reason two of the views were not working was because of a views access callback that I was using. The ajax apparently was not processing the access correctly and it would never load more content.

That brings me to the real issue. This module has been rolled out with a new dev release. I see a lot of activity on the three issues regarding the Pager selector. My question then is: If I define a specific Pager selector for each block in the view, then will waypoints know to trigger the individual blocks separately? I have been trying different options, but everything breaks (loads exponentially more content)