Search

I just want to add to this to help someone in the future. The method I mentioned of not defining the non-editable fields in the editor instance is not the correct way to go about it. There is the readonly field type which should be used instead. And if necessary, you can use fields.submit to prevent the field from being passed for update. Example: editor = new $.fn.dataTable.Editor( { table: "#example", fields: [ { label: "Name:", name: "name" }, { label: "Position:", name: "position" }, { label: "Office:", name: "office" }, { label: "Age:", name: "age" }, { label: "Start date:", name: "start_date", type: "datetime" }, { label: "Salary:", name: "salary", type: 'readonly', submit: false /* Optional */ } ], formOptions: { main: { scope: 'cell' // Allow multi-row editing with cell selection } } } );

Use columns.render to perform the calculation.

There are lots of threads discussing this, like this thread. Kevin

Hello @colin , any news? I Noticed that this happens because the "real" gets recreated when the fixed header disappears (scrolling to the top). The regeneration of the thead lose the style attribute of the . Is there a way, by api or config, to avoid the recreation of the thead?

You have api.columns( 7 ).data().sum(); to get the sum. Use the selector-modifier of { search: 'applied' } like this api.columns( 7, { search: 'applied' } ).data().sum();. Kevin

There is a complete working example in the blog page.

Aaah... (o; Missed those two lines: Wasn't aware they were needed even for enabling inline editing as well...

Ah I see. The best bet would be to do something like this. It's a generic function that finds the table that clicked, then gets the index of the row. Colin

Thank you so much. That's exactly what I was looking for.

This is not a DataTables issue. The problem is your misuse of your own CSS. First, you are using both inline ("style" tags in HTML) and external CSS files, which may be overriding or contradicting each other. Choose inline or external, not both. Second, your files goods.css and goods999.css both have many of the same definitions. They also may have conflicting definitions - I didn't check all of them. Your CSS is a mess. You need to clean it up. Not a DataTables issue.