Search

[code] $.fn.dataTableExt.afnFiltering.push( function( settings, aData, iDataIndex ) { if ( settings.nTable.id === 'example' ) { // filter example } else { // ... } } ); [/code]

Solved it by doing initial sort expressively on the column that the filter didn't work on until it was filtered - changed line 120 in above example to: [code] oTable.fnSort( [ [6,'asc'] ] );[/code]

[quote]Put your custom filter in place using standard DOM / jQuery techniques and then use fnFilter ( http://datatables.net/api#fnFilter ) to apply the filter to DataTables.[/quote] http://www.datatables.net/forums/discussion/6180/howto-add-custom-search-field/p1

default setting of the filter, that means an empty

Just upgraded the script to DataTables 1.9.4, and I still see the same problem. Can someone confirm that this is how it should work? How can I fix this behaviour, if I filter on "P 1" it shouldn't return "P10".

Sounds like an issue with the column filter plug-in. I'd suggest filing a bug report for that project. Allan

If you want to filter the table you can use fnFilter - or if you want to change the data source for the table you can use fnServerParams to send a different parameter, indicating the category, to the server-processing script. Allan

You could use a filter call of: [code] table.fnFilter( '^P\d\d\d\d$', null, false ); [/code] to do a regex filter which matches your description. Allan

setting bProcessing and bServerSide to false - fixed this. bProcessing, bServerSide = true is needed for other ajax related functionality (although doesn't circumvent ajax) , but apparently it turns off the very useful client-side functionality of filter, sorting, and pagination.

Nevermind... I figured it out. I just took the filter class and appended my own html next to it. :)