I have implemented a tab system with the new pagination feature just like @tarahoover has explained above, and it seems to be working, at least in the Designer. I have a page of resources (one dynamic content collection) that my client wants filtered by 4 categories (tabs), and under each category they want to show only 12 dynamic content items at a time. Pagination allows them to add up to hundreds of additional items, creating a new “page” within each category tab for every 12 items.
My problem is that when published, there is a weird bug where the pages within tabs are not functioning properly. I figured out that has to do with whatever tab is set as the “active tab” when I’m in the Designer. So for example, say “Tab 1” is set as the active tab in the Designer. On the published site, if I go to tab 3 and click the more/next pagination button, this should take me to the second page of items within that tab (as it does in the Designer). But it actually shows the first page of tab 1, the “active tab.” Clicking one of the other tab menu buttons and back to tab 3 “refreshes” it, so that the proper page shows. The same thing happens based on whatever tab is set as the “active tab,” even if that is “none” (shows a blank page when I click the more pagination button).
Tab 3 on published site:
After clicking more/next pagination button on Tab 3, shows first page of Tab 1:
Clicking away from and back to Tab 3 fixes:
@aaronocampo Any idea on what might be causing this and how to fix? I’m also using the pjax “seamless pagination” script (Seamless pagination with "pjax"), but this doesn’t seem to make a difference either way. Mixitup looks like it would have been an ideal solution but alas not really a viable option at this point.
Edit: I should say it’s not exactly like the examples above, as I’m not looking to filter by all/specific categories; just using pagination within tabs.
Read Only Link (page in question is /youth-resources/relationships)