Search

Has anyone else using this configuration come across a problem where you goto the print page, then hit the escape button to go back, and error is caused where you lose pagination. If you delete the cookie used to store the state save information, then it will be fixed temporarily, until you try and do that same set of steps again. Here is the actually Cookie itself. [code] {"iStart": 150,"iEnd": 75,"iLength": -1,"sFilter": "","sFilterEsc": true,"aaSorting": [ [0,'asc']],"aaSearchCols": [ ['',true],['',true],['',true],['',true],['',true],['',true],['',true],['',true],['',true],['',true],['',true],['',true]],"abVisCols": [ true,true,true,true,true,true,true,true,true,true,true,true]} [/code] Could the problem possibly be iLength = -1?

Think I needed more coffee :D

config. I updated my ajax test case to show

for me, even for ajax loaded columns

JSON object loaded from Ajax) would give better performance.

confusing. I only use ajax (candidate for rename in

DataTable API, runs a AJAX request manually to get

it work locally without ajax. I don't believe it

and can just use ajax to initially fetch all

Helpful discussion, server error handling in DataTables can be tricky. Using proper JSON responses and custom AJAX error handling really makes a difference.