Search

a href="//datatables.net/reference/option/lengthMenu">initialisation option">lengthMenu initialisation option. This

with, the standard Javascript initialisation options (with the data-*

a href="//datatables.net/reference/option/headerCallback">initialisation option">headerCallback and

a href="//datatables.net/reference/option/search.return">initialisation option">search.return can be used

useful to set the initialisation defaults to common values

a href="//datatables.net/reference/option/columns.visible">initialisation option">columns.visible option and

a href="//datatables.net/reference/option/columns.render">initialisation option">columns.render which can be

lgfAdminOnly" }, "colvis" ] } ); forexTable .on ('init', function () { if ( ! lgfAdmin ) { forexTable.buttons('.lgfAdminOnly').remove();

Due to the async nature of ajax you probably will need to use initComplete or the init event to install the buttons. Otherwise the table.buttons().container().insertBefore( '#example_filter' ); code is executed too soon. Here is an example: http://live.datatables.net/cecemole/1/edit Kevin

draw event after the initial draw has already happened

Yes, my tables have different number of columns. I trimmed all of my complex customization down to: table.DataTable(); same error. My init function is hooked like this: $(function () { setupIntTables(); }); -S

yet. Move the Datatables init code inside the dine

then post your Datatables init code and the response

columns " in the datatables init won't work because data:columnnames[i]

to a "DataTables on init" option: }).on('init.dt', function(){ That

for example, you would init you Datatables with the

By default paging is enabled as noted in the docs. Adding: "paging: false" had no affect. Using paging: false here works with 1.10.18: http://live.datatables.net/girelewa/1/edit What did you upgrade from? Please start by posting your Datatables init code. Kevin