search

Mottie / tablesorter

Github fork of Christian Bach's tablesorter plugin + awesomeness ~
https://mottie.github.io/tablesorter/docs/
2.61k stars 754 forks source link

filter-select no longer exact match? #1556

Closed mtgtnt closed 6 years ago

mtgtnt commented 6 years ago

I have had to add: filter_excludeFilter: { 0: 'range', 1: 'range', 2: 'range', 3: 'range', 4: 'range', 5: 'range', 6: 'range', 7: 'range', 8: 'range', 9: 'range' }, today to deal with the "space dash space" thinking there is a range filter set. I do not recall this happening before after you set it to be exact match many many versions ago.

Mottie commented 6 years ago

Hi @mtgtnt!

There were some adjustments made to the select behavior last year (in v2.28.12) to get the filter to properly work with jQuery UI selectmenu.

You don't need to target every column. The filter_excludeFilter can target the header class name as well:

$(function() {
  $("table").tablesorter({
    widgets: ["filter"],
    widgetOptions: {
      filter_excludeFilter: {
        ".tablesorter-header": "range"
      }
    }
  });
});

Related to issue #1520... I can look at the code again and see if I can fix it to use the "exact" filter type directly instead of only using it when a user includes an "or" or "and" in the query.

mtgtnt commented 6 years ago

Thanks for the '.tablesorter-header': 'range' tip. For now this works fine, just caught me off guard. Was using a previous version where it was working so I didnt think anything about it till a user informed me something was a miss when using the filters. Took a bit to figure out it was the dash (range).

Mottie commented 6 years ago

I'm guessing this issue has been resolved, so I'm going to close it. If you continue to have problems, please feel free to continue the discussion in this thread.