Description
Hello again Mottie! Hopefully seeing my name in an issue doesn't immediately fill you with dread now... :) Unfortunately I do have another AJAX-related issue to report.
Using all server-side options and your filter saving example, the pager addon makes two requests to the AjaxUrl when it initializes - one before filters have applied, and one after.
?page=0&size=25&filter&sort[0]=1
?page=0&size=25&filter[0]=1373781600&filter[1]=800&sort[0]=1
Each AJAX request performs a rather expensive database query in my application, so it's important for me to find a solution to this issue.
Digging around in the source leads me to believe that if the pager addon had a 'priority' value similar to the filter widget, it could initialize after filters have been applied.
Would it be possible for the pager to be rewritten as a proper widget? If not, how can I delay the pager's initial AJAX request until filters have been applied?
Once again, thank you very much for your assistance. I realize I'm using your plugin in an unusual manner (it's basically a view for my database), and I appreciate your extensive support.
EDIT: I've been thinking about this some more, and doesn't it make more sense for the AJAX options to be part of the core tablesorter code anyway? It's not really a pager-specific feature, and it would probably solve this and other problems.