I've encountered this problem also. The issue is that by default the onDataReturnInitializeTable method of the DataTableDataSource creates a new RecordSet object when loading a new data set, however the DataTableSort plugin is listening on the particular RecordSet instance. Since that's thrown away on a load the sort plugin never notices that there's new data to be sorted. I created a special subclass of DataTableDataSource that fixes this bug. Instead of creating a new RecordSet instance, it empties the old one and adds the new results.

        SorterDataTableDataSource = function() {

            SorterDataTableDataSource.superclass.constructor.apply(this, arguments);

        }

        

        Y.extend(SorterDataTableDataSource, Y.Plugin.DataTableDataSource, {

            onDataReturnInitializeTable : function(e) {

                var dt = this.get("host"), rs = dt.get("recordset");

                dt.set("recordset", rs.empty().add(e.response.results));

            }

        }, {

            NS: "datasource",

            NAME: "dataTableSorterDataSource"

        });

We're all waiting on Luke's new and improved DataTable :)

Ticket #2530184 was marked as a duplicate of this ticket.

Ticket #2529975 was marked as a duplicate of this ticket.

Replace the Recordset records, not the Recordset

Fixes #2529872

onDataReturnInitializeTable was replacing the
Recordset instance managed by the DataTable rather
than just replacing its records. Since a fair
amount of functionality is tied to the Recordset,
this broke stuff.

View Commit: 364b3f41370b5853ec58ed0f094565f69ab7c7fd

Ticket #2531191 was marked as a duplicate of this ticket.