Search

The first place to start is to follow the troubleshooting steps at the link provided in the alert message: https://datatables.net/manual/tech-notes/1 What are your results from following the steps? Kevin

bootstrap 4.0 theming, the default width of the dropdown editor does use the width of the column according to datasize in it, which makes it hard to select the correct value. What's the best way to customize the width of search dropdown list?

Not yet - sorry. Its been a bit bonkers recently! Allan

I've found a way to do this, and I want to answer my own question, in the hopes that it might help others who are facing a similar design challenge. I got the processing div to stay visible during the loading of data by doing the following: I created a new Deferred instance at the top of my function: var tableDataDeferred = $.Deferred() I added the following properties to the instantiation of the DataTable: { processing: true, ajax: function (data, callback) { tableDataDeferred.done(callback); } }. This attaches the AJAX loading callback as the final step of my deferred object. The callback function only gets called when the tableDataDeferred promise gets resolved, and passes its data on to the callback() function. In my post-processing function, rather than calling row.add() on each record as it is sorted into one table or the other, I simply push it on to an array, tableDataRows.push( newRow ). Finally, when I've collected all of the data for a certain table, I close the loop by resolving the promise, which passes the data on to the Datatable's AJAX callback function, tableDataDeferred.resolve({data: tableData}). Works like a charm!

Tested with Editor 1.6.5. It's working good. Thank you for fixing this.

Problem solved after referring to https://editor.datatables.net/manual/server We are using Python as backend and I need to properly prepare the response data from an ArangoDB reply...so none of your integrations was used.

Can you use JSFiddle or http://live.datatables.net to recreate the issue please? I'm afraid I would need something showing the problem to be able to offer any help. Allan

Is there now way to bypass the editor error message? Not really - Editor by default expects JSON in reply. Indeed, even in your own Ajax method you are telling it to expect JSON ( dataType: "json" ) and it sounds like the server is not returning with JSON. The only way to bypass it would be to generate the JSON that Editor expects on the client-side and pass that into the success callback function. But i am using the following, and that completly omits the sending of the parameter array (data): Because you aren't submitting the parameters from Editor. You would need to do something like: data: $.extend( data, { action: '...' } ) Allan

The options only automatically populate when using Editor with DataTables since that information is included in the Ajax response for the DataTables "get" of the data. Since you are using a standalone Editor there is no Ajax fetch initiated by DataTables, thus there is no way for Editor to hook into it and automatically extract the options. You'd need to use the field().update() method of the select field type to be able to set the options in response to the Ajax data you are fetching. Allan

Hi Mark, Sorry for the delay in getting back to you on this one. I've not heard of any errors like this before. The "processing" message not going away is normally caused by a Javascript error - but that should really be replicable over similar devices / browsers. I don't have an iPad around either I'm afraid, but I've just tried an iPad Pro in the Xcode simulator running iOS 9.3 and the page appears to load without any issues for me. Allan