tablesorter

Pager plugin

Flexible client-side table sorting

NOTE! The following are not part of the original plugin:

• This pager plugin can be applied to the original tablesorter, but there is one exception - setting the removeRows option to false will break the sort.
• There have been lots of changes made in version 2.1, please check out the change log below.

Triggered Events

• Pager events will appear here.
•  
•  

Demo

10 20 30 40

10 20 30 40

Javascript

CSS

/* pager wrapper, div */
.pager {
  padding: 5px;
}
/* pager wrapper, in thead/tfoot */
td.pager {
  background-color: #e6eeee;
}
/* pager navigation arrows */
.pager img {
  vertical-align: middle;
  margin-right: 2px;
}
/* pager output text */
.pager .pagedisplay {
  font-size: 11px;
  padding: 0 5px 0 5px;
  width: 50px;
  text-align: center;
}

/*** loading ajax indeterminate progress indicator ***/
#tablesorterPagerLoading {
  background: rgba(255,255,255,0.8) url(icons/loading.gif) center center no-repeat;
  position: absolute;
  z-index: 1000;
}

/*** css used when "updateArrows" option is true ***/
/* the pager itself gets a disabled class when the number of rows is less than the size */
.pager.disabled {
  display: none;
}
/* hide or fade out pager arrows when the first or last row is visible */
.pager img.disabled {
  /* visibility: hidden */
  opacity: 0.5;
  filter: alpha(opacity=50);
}

HTML

<table class="tablesorter">
<!-- view page source to see the entire table -->
</table>

<!-- pager -->
<div id="pager" class="pager">
  <form>
    <img src="first.png" class="first"/>
    <img src="prev.png" class="prev"/>
    <span class="pagedisplay"></span> <!-- this can be any element, including an input -->
    <img src="next.png" class="next"/>
    <img src="last.png" class="last"/>
    <select class="pagesize">
      <option selected="selected" value="10">10</option>
      <option value="20">20</option>
      <option value="30">30</option>
      <option value="40">40</option>
    </select>
  </form>
</div>

Pager Change Log

Version 2.1.6 (3/22/2012)

• Updated pager css. It wasn't targeting the pager block correctly.
• Moved pager into the thead and/or tfoot in the pager ajax demo.
• The pager plugin ajax method should now only target the header column text (not the pager) and first footer row when updating the header text.

Version 2.1.3.1 (3/17/2012)

• Rozwell contributed some bug fixes that occur when cssPageSize is not set. Thanks for sharing!

Version 2.1

• Ajax:
  • The pager plugin will now interact with a database via JSON. See demo here.
  • Added ajaxUrl option which contains the variables {page} and {size} which will be replaced by the plugin to obtain that data.

    ajaxUrl : "http:/mydatabase.com?page={page}&size={size}"

  • Another option named ajaxProcessing was included to process the data before returning it to the pager plugin. Basically the JSON needs to contain the data to match the example below. An additional required variable is the total number of records or rows needs to be returned.

    // process ajax so that the data object is returned along with the total number of rows
    // example: { "data" : [{ "ID": 1, "Name": "Foo", "Last": "Bar" }], "total_rows" : 100 }
    ajaxProcessing: function(ajax){
      if (ajax && ajax.hasOwnProperty('data')) {
        // return [ "data", "total_rows" ];
        return [ ajax.data, ajax.total_rows ];
      }
    }

  • I tried to make the plugin interact with a database as flexible as possible, but I'm sure I haven't covered every situation. So any and all feedback is welcome!
  • Also, much thanks to kachar for the enhancement request and willingness to help test it!
• Removed positionFixed and offset options.
• Added fixedHeight option which replaces the positionFixed and offset options.
  • If true, it should maintain the height of the table, even when viewing fewer than the set number of records (go to the last page to see this in action).
  • It works by adding an empty row to make up the differences in height.
  • There were some issues of the height being incorrect when this option is true. The problems occurred if you add/remove rows + change pager size, or just destroy/enable the pager. I think I fixed it, but if you should find a problem, please report the issue and steps on how to duplicate it.
• The pager container option will now accept class names. So you can add multiple container blocks to control the pager, just as this page now has two, one above and one below.
• The pager now adds all of its options to the table configuration options within an object named "pager". Basically what this means is that instead of add all of the pager options to be mixed in with the tablesorter options, the pager options have been isolated and can be found by typing this into the browser console: $('table')[0].config.pager.

Version 2.0.21.2

• Added "disable.pager" and "enable.pager" methods added to make it easier to add or delete rows from the table.

Version 2.0.16

• Reduced the number of rows in the demo from 1022 to 50, so you don't have to scroll forever (when the pager is destroyed) to see the code below the table.
• Added "destroy.pager" method will reveal the entire table, remove the pager functionality, and hide the actual pager.
• Added a new addRows method to allow adding new rows while the pager is applied to a table. Using "update" would remove all non-visible rows.

Version 2.0.9

• Added cssDisabled and pagerArrows options which controls the look of the pager and arrows when the pager is on the first or last page.
• Updated pager functions, removed "separator" option, and added output string formatting (e.g. "1 to 10 (50)").

Version 2.0.7

• Added "pagerChange" and "pagerComplete" events in version 2.0.7.