Search

It's hard because is a serverside pagination. Btw I solved: $('#presentation tfoot th').each( function (i) { var title = $('#presentation thead th').eq( $(this).index() ).text(); $(this).html( '<divREMOVEME><input class="filter_' + title.replace(/\s/g, "") + '" type="text" placeholder="' + title + '" data-index="'+i+'" /></divREMOVEME>' ); $(this)[0].children[0].setAttribute('title','<val \n >val \n & == val \n ! <> val \n % like %val% \n @ not like %val%'); } );

thanks, brother you are correct and now I fix the problem with your answer thanks hundred times

We're happy to take a look, but as per the forum rules, please link to a test case - a test case that replicates the issue will ensure you'll get a quick and accurate response. Information on how to create a test case (if you aren't able to link to the page you are working on) is available here. Cheers, Colin

Thank you very much Kevin.

I'm not clear on what you are having a problem with. I updated an old YADCF example I have to show both horizontal and vertical scrolling: http://live.datatables.net/tomimadu/58/edit I checked with their portal, everywhere scroll is used on .DataTable() but not on .dataTable() When applying Datatable's options it doesn't matter which you use. For more information on the differences please see the Install doc. In the example I used yadcf.init() instead of chaining the yadcf init off the Datatables initialization. If you still need help please build a test case showing what you are trying to do so we can help. https://datatables.net/manual/tech-notes/10#How-to-provide-a-test-case Kevin

We're happy to take a look, but as per the forum rules, please link to a test case - a test case that replicates the issue will ensure you'll get a quick and accurate response. Information on how to create a test case (if you aren't able to link to the page you are working on) is available here. Cheers, Colin

I think it purely depends upon the VIEW and what it is doing (hundreds of sub-queries for example would be bad). It certainly won't be less efficient than hitting the db with 300 individually compiled and executed queries though. Allan

I think because you're explicitly asking for a record, it's ignoring the fact that it's not on that page. Probably the easiest way would be to do something like this: if ( table.rows({page: 'current'}).ids().toArray().includes('id_1')){ $('#tiger').css('visibility','visible'); } See here, Colin

Hi @akwebapps , We include links to the documentation for SearchPanes for each of the platforms that are supported (as below). From there you are within the documentation for the relevant Editor Library. Full documentation for the platforms we support is available here: - .NET - NodeJS - PHP From there you can find the install instructions through a link on the navigation pane on the left side. I guess we thought this would have been fairly clear, I'll talk to the other guys and see what they think though. Thanks, Sandy

@kthorngren Thank you. That worked :)