Paginated toplists get a job done: they allow your users to page through very long lists in their entirity. For a full page list which is the primary page content, this is fine.

When the list people are paging is just a little box in a corner of the page, particularly if the box is below the scroll line, it's irritating that the entire page reloads to show the next toplist page. What we'd like to do is have a refeshless pager that just updates the toplist content quickly without affecting the rest of the page. That's what I've been working on this week.

In this sort of compact situation, a list of 10 different page numbers is usually less desirable than a simple previous/next navigation. Thus the initial type of navigation I've set up is two simple buttons, "Previous X" and "Next X" where X is the number per page. These buttons hide appropriately on the first and last page. I can add support for other forms of pagination on request.

To impliment using WSN 10.4.7 Beta 2, simply replace {TOPLIST1PAGINATION} with {TOPLIST1AJAXPAGINATION} in your template -- changing the number 1 to the applicable toplist number. I tested it out with the top 5 links box and it works fine there, except that it doesn't respect the sort top rated / most visited toggles since I haven't ajaxified those yet -- which I will do for the next beta, at which point I'll make the ajax version of the top links box be the standard template version.

This won't work on a toplist in the wrapper template at the moment, though if you need that let me know and it won't be too hard to support. It's uncertain whether it works on integrated templates from other scripts, if not then again let me know you need it. It's possible some advanced toplist options may not be compatible, if so let me know so I can look into it.