FixedColumns server-side processing error

FixedColumns server-side processing error

binhlkbinhlk Posts: 1Questions: 0Answers: 0

Link to test case: https://datatables.net/extensions/fixedcolumns/examples/initialisation/server-side-processing.html
Error messages shown:
Uncaught TypeError: Cannot read properties of undefined (reading 'anCells')
at _pluck_order (dataTables.js:1235:23)
at _Api.<anonymous> (dataTables.js:8485:11)
at _Api.iterator (dataTables.js:6757:17)
at _Api.<anonymous> (dataTables.js:8484:15)
at _Api.<anonymous> (dataTables.js:6975:18)
at _Api.nodes (dataTables.js:6847:17)
at FixedColumns._fixColumn (dataTables.fixedColumns.js:301:74)
at _Api.<anonymous> (dataTables.fixedColumns.js:201:26)
at _Api.<anonymous> (dataTables.js:9552:9)
at _Api.iterator (dataTables.js:6757:17)
Description of problem: When click other pages the fixed column not fixed anymore.

Replies

  • xStopherxxStopherx Posts: 1Questions: 0Answers: 0

    I can second this issue. In my case I have initialized the DataTable with 2 fixed columns on the 'start' side. It looks like the order array data is being lost on subsequent page loads from the server.

    if ( prop2 !== undefined ) {
                for ( ; i<ien ; i++ ) {
                    if ( a[ order[i] ][ prop ] ) {
                        out.push( a[ order[i] ][ prop ][ prop2 ] );
                    }
                }
            }
    

    In this code snippet from DataTables, after a page change, the order array entries are all undefined causing the 'anCells' key to error out, but the JSON server side response does include the proper order information. The header row does continue to freeze the left columns.

Sign In or Register to comment.