I am trying to create a landing page that operates similarly to mashable.com, where there are multiple columns over multiple views that each have the load more waypoints infinite scroll. Right now the first view scrolls infinitely, but the other views don't. I see the ajax loader, but it doesn't append any more data from the views, and doesn't throw any errors. Is this something that is possible? I haven't unserialized the JSON yet to see what it's trying to post, but I was hoping for some insight.

Comments

dwilkinson’s picture

I managed to figure this out - it turns out that there was an issue with the markup in the view. Infinite scroll over multiple views is working perfectly now.

vitkuz’s picture

it turns out that there was an issue with the markup in the view

What was the issue?

pribeh’s picture

Yeah, what was the issue dwilkinson? I'm experiencing issues with multiple load more pagers.

dwilkinson’s picture

In my case, the issue was that I had some specific template overrides set in Views, and the id that this module targets wasn't available. Once I had my views markup solved, everything worked.

funana’s picture

Thank you very much for that hint @dwilkinson!

"views-row" class was missing in my view, using Semantic Views.
Added it there to the row class attribute field in display options, bingo!

Thx again man :)

nicholas.alipaz’s picture

Category: support » bug
Status: Active » Needs review
StatusFileSize
new1.2 KB

None of the aforementioned solutions worked for me. I found it was a bug in the js file. The issue was surrounding the variable view in the attach and detach behavior. What happened for me was that this variable was assigned the same data for each pager that was on the page. I had to change the code as in the attached patch to fix the issue.

queenvictoria’s picture

Nice work @nicholas.alipaz but this still didn't work for me. However $(this) is a reference to the pager link so I've updated your patch to use that instead.

queenvictoria’s picture

Fixing my own patch. Use this one if you've NOT applied the remove patch from 1889300.

nicholas.alipaz’s picture

queenvictoria, good catch on $(this), I suggest that rather than stacking your patch on mine, you make one that simply includes mine and your changes together, or was it that you didn't need my patch?

queenvictoria’s picture

@nicholas.alipaz actually yes I didn't need anything except $(this) so the patch in #8 is complete. #7 accidentally stacked the patch from 1889300 (destroy).

m4olivei’s picture

Status: Needs review » Closed (works as designed)

I believe this was fixed differently in recent commits. If this is still an issue, please reopen and reroll against 7.x-1.x.

Thanks!