server side, new api, stateSave, colReorder and column's order in the xhr request

johndegey

Hello,

I'm using DT 1.10.4, the new api and server side processing.
I've switch to yadcf instead of ColReorder.

I'm facing a problem with yadcf and after debugging, i've noticed that the xhr request send was different when you reload the html page than the one send when you use the DT pagination system.

Here is my test case:
http://yadcf.johndegey.org/

If you switch field2 and field3, then reload the page, the xhr request will be

columns[0][data] field1 columns[0][name] field1 columns[0][orderable] true columns[0][search][regex] false columns[0][search][value] columns[0][searchable] true columns[1][data] field2 columns[1][name] field2 columns[1][orderable] true columns[1][search][regex] false columns[1][search][value] columns[1][searchable] true columns[2][data] field3 columns[2][name] field3 columns[2][orderable] true columns[2][search][regex] false columns[2][search][value] columns[2][searchable] true

If you just go to page 2 with the pagination, it looks like

columns[0][data] field1 columns[0][name] field1 columns[0][orderable] true columns[0][search][regex] false columns[0][search][value] columns[0][searchable] true columns[1][data] field3 columns[1][name] field3 columns[1][orderable] true columns[1][search][regex] false columns[1][search][value] columns[1][searchable] true columns[2][data] field2 columns[2][name] field2 columns[2][orderable] true columns[2][search][regex] false columns[2][search][value] columns[2][searchable] true

Notice the column 1 is now field3 and column 2 is field2.

Is this an expected behavior ?
Shouldn't the 2 request be the same ?

Here is the discussion we have on github
https://github.com/vedmack/yadcf/issues/151

thanks for help

John