-
Notifications
You must be signed in to change notification settings - Fork 753
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tablesorter unable to filter externally on some columns. #1177
Comments
Hi @Mottie , Thanks for all of your work, very appreciated. I am experiencing the same/similar issue that Manoj is, and it is even happening in your external search demo page https://mottie.github.io/tablesorter/docs/example-widget-filter-external-inputs.html. Try changing the select box to first or last name, then typing in something. If I try to filter on a single column instead of 'all', then it throws errors at jquery.tablesorter.widgets.js:1419 Cheers |
Hi @jwrichard! Thanks for that extra bit of info, it helped me find the bug! I will have it fixed here shortly. @Manoj999, please let me know if this fixes your issue. The fix will be available in the master branch in the |
@Mottie Perfect! I'm excited to see that you were able to fix it. I just tested it out and it is working for me now. Thank you very much 👍 |
Hi @jwrichard and @Mottie, Hope you are doing well. I have that issue previous later I added the property *filter_columnAnymatch: On Thu, Mar 24, 2016 at 8:33 PM, jwrichard [email protected] wrote:
Thanks And Regards, |
Hi @jwrichard and @Mottie, Hope you are doing well.
To solve above issue I used filter_functions option in the following way.
|
So @Manoj999, has this issue been resolved? Can I close it? |
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. |
try {
This is my code.
I have one column with data is like this :1:20:30, this column I am unable to filter from external search input.
Please help me.
The text was updated successfully, but these errors were encountered: