Search

Perfectly fixed <3 Thanks, @allan

I'm having an issue while migrating from 1.13.4 to 2.1.6 where the table expands beyond the width of the bounding div, even when there are columns that could be made narrow enough to fit it within the div. The columns appear to not shrink smaller than the original width, but expand as needed. I have not had this issue with 1.13. Here is an example using 2.1 - you'll have to reduce your screen size to ~680px wide for the effect to be obvious. The first page has relatively narrow items in the first column and long items in the second column. When you go to the second page, the items in the first column are wider, so it expands the column width to accommodate them. The second column now has narrower items, but doesn't reduce in size, causing the table width to grow. https://live.datatables.net/vakiqequ/2 Here is an example using 1.13, where the table stays the same width the entire time, shrinking the second column to accommodate the wider first column. https://live.datatables.net/calonuna/1

Awesome. Thank you for fixing that. It will be so much easier to search the forums now.

Try: li.dt-paging-button.disabled { visibility: hidden; } https://jsfiddle.net/8bxpacn6/ I think the use of display: none is messing with the responsive calculations and confusing the code as it was never designed to handle such a case. Regards, Allan

I forgot to post back - sorry... It is fixed now! There was an integration problem with server-side processing when server-side processing was enabled. Allan

I'm not sure what w-auto is but maybe you can place it on the div container for the table, ie <div id='main'>. Or create a new container div, for the table, that is the width you want. Set style="width:100%" on the table tag as shown in this example. This should keep the Datatable and components like page length within the defined container. Kevin

Yup, I successfuly fixed it. Thank you very much for the instantenous feedback!

https://datatables.net/reference/option/dom

Can I display those validation messages in a Modal window, rather than at the bottom of the Editor form? Sure - return an error for the field that is in error. See the fieldErrors array here. How can I set validation for if/when the user attempts to delete a primary record which still have a foreign key (in a secondary table) referencing it? Two options: Set the row to cascade on delete in the database schema, or Use a validation function to check if the row being deleted is being referred to from anywhere else. We don't actually have a built in validator for that - I'll look into an option for that. Allan

I'm not seeing any errors with that test case, it's behaving I'd say as expected. The error you quoted is from Highcharts, not from DataTables. Please can you give steps on how to reproduce, Colin