Search

For some reason just adding a parameter to the controller method fixes and form variables are present

Thanks @colin I will check that.

THANK YOU!!!! (as I cuss myself under my breath) I knew it was something simple!

Nevermind - I have figured it out but ran into a new problem which I'll start a new thread for The issue was this snippet editor.add({ label: "Division:", name: 'division_id', }); notice the name 'division_id' doesn't match the column definitions: "columns": [ {"data": "id"}, {"data": "eo_role", "defaultContent": "N/A"}, {"data": "division", "defaultContent": "N/A"}, {"data": "product_name"}, {"data": "category"}, ],

I am returning 200s by hand as a test and the problem goes away. I'm not sure where or if its documented or if I just remember seeing it on the forum but I think Datatables expects both a 200 status code and a valid JSON otherwise you will get the invalid JSON message. Kevin

You are still loading the extensions before loading DataTables itself. Try using the download builder to get the files you need in the order you need. Allan

Hi @nick_bestplaces , When you use columns.width like that, you're saying the table only has one column. Take a look at that link: either have nulls for the other columns, or use columnDefs to specify a single column. Cheers, Colin

I think we'll do the 1.7.4 release towards the end of this month. Enough time to allow anything that crops up to be fixed :). Allan

My guess is that you have included the pdfmake library in that datatables.js file? If so, that is the issue. pdfmake which is used by the Buttons extension for DataTables to create pdfs, doesn't support legacy IE. I am surprised that pdfmake throws an error on that though, rather than just testing for it and then refusing to execute. I'm only guessing without a link to a test case showing the issue though. Allan

Thank you so much!