Hello
When using Server-side processing and bStateSave to True, it might happen that DataTables ask data with an obsolete iDisplayStart (from previous saved state) and then receives no data starting at this index because it has been deleted by some other users.
This results in inconsistent display like "Showing 21 to 20 of 20 entries", same problem for the pagination display.
This inconsistency could be easily detected by DataTables and a new XHR request could be performed.
Is there already a way to do this auto-refresh in that case ?
If not, how can I do it myself ? I saw that the pagination plugin offers the possibility to call fnCallbackDraw for fnUpdate function but fnUpdate does not seem to be the appropriate place to put auto-refresh code.
Any advice please ?
When using Server-side processing and bStateSave to True, it might happen that DataTables ask data with an obsolete iDisplayStart (from previous saved state) and then receives no data starting at this index because it has been deleted by some other users.
This results in inconsistent display like "Showing 21 to 20 of 20 entries", same problem for the pagination display.
This inconsistency could be easily detected by DataTables and a new XHR request could be performed.
Is there already a way to do this auto-refresh in that case ?
If not, how can I do it myself ? I saw that the pagination plugin offers the possibility to call fnCallbackDraw for fnUpdate function but fnUpdate does not seem to be the appropriate place to put auto-refresh code.
Any advice please ?