You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you apply both the sortList and headers options, you get an error right after the page loads.
When you add the sortList option, if I remember correctly, the form sorts itself once the page is loaded. When you add the headers option, you decide which of the colums are sortable.
When you add them both, and set it up so that the list is sorted on some of the unsortable columns specified in headers, you get an Cannot read property 'addClass' of undefined error. This error stems from a rather weird implementation in the setHeadersCss method.
Hope you can fix this somehow :)
The text was updated successfully, but these errors were encountered:
This may not be a bug per-se. In my case I had headers defined for columns 0 and 1. I was sorting on columns 0 and 1 also. Then when I deployed to test (instead of dev) the table that was being sorted had an additional column added (because of some other setting) which did not have a header defined. This led to tablesorter not having a sorter and failing.
When you apply both the
sortList
andheaders
options, you get an error right after the page loads.When you add the
sortList
option, if I remember correctly, the form sorts itself once the page is loaded. When you add theheaders
option, you decide which of the colums are sortable.When you add them both, and set it up so that the list is sorted on some of the unsortable columns specified in
headers
, you get anCannot read property 'addClass' of undefined
error. This error stems from a rather weird implementation in thesetHeadersCss
method.Hope you can fix this somehow :)
The text was updated successfully, but these errors were encountered: