Search

I also wanted to do this feature.If you get any ideas ,Can you please share with me?

Never mind.. I've figured it out.. I should have had the sLengthMenu outside the oPaginate...i.e. { "bLengthChange": true, "bFilter": false, "bSort": true, "bInfo": false, "bAutoWidth": true, "bJQueryUI": true, "sPaginationType": "full_numbers", "bProcessing": false, "oLanguage": { "sLengthMenu": ' "Records per Page") MENU ', "oPaginate": { "sFirst": 'First Page', "sLast": 'Last Page', "sNext": 'Next Page', "sPrevious": 'Previous Page' } } } Thanks for the great tool!!! :)

thanks alot! :)

You should take a look at: http://datatables.net/examples/basic_init/language.html You can also use an AJAX source: [code] $('#table').dataTable({ "oLanguage": { "sUrl": "../res/js/dataTables.fr.txt" } }); [/code] where the text contains the oLanguage object: [code] { "sProcessing": "Traitement en cours...", "sLengthMenu": "Nombre maximum d'

It looks okay to me when sorting it (Safari 5). However, it would be worth using this example: http://datatables.net/examples/basic_init/multi_col_sort.html , since the ones on my personal site are using DataTables 1.3... Allan

Hi, I tried this method and it seems to work. Only problem I saw was in pagination. I mean u might have 100 records but since on initial display of table u are just making 10 visible. Pagination think u only have 10 records to display. So pagination link seem to remain disabled

Yes there is: http://datatables.net/usage/options#aaSorting Allan

Thank you for your helpful answer, works fine and was indeed an easy task :)

Just sharing this solution because it took me quite a while to figure it out. I'm using an ajax call, serverside setup and I have scroller turned on. I also have auto-sorting happening on each initial page load. Together, these were causing issues with getting a column with consistent numbers from 1 to the end of whatever the current view/results were because of the virtual pages Scroller users and because relying on the initial order of the results was not reliable due to the sorting on initial draw. Finally, I landed on this, added inside the drawCallback, which seems to work great: var info = api.page.info(); var start = info.start; api.column(0, { page: 'current' }).nodes().each(function (cell, i) { cell.innerHTML = i + 1 + start; }); If you're using another column except the 1st one, just change 0 to whatever the column index is.

Dear, I am doing the server-side search as explained in the official documentation, but I have the problem that the search is now not as accurate as before implementing this. I explain, before the order did not matter, it did not matter to write the words complete or be so explicit, now I only find the coincidences completely accurate. This has caused problems for weeks and I still can not solve it. I hope you can help me or guide me on how to make my search more accurate. Thank you.