bStateSave and sAjaxSource together can cause errors
bStateSave and sAjaxSource together can cause errors
chriskl
Posts: 2Questions: 0Answers: 0
Scenario is this:
1. Table is set up with an AJAX data source with 5 columns
2. Someone uses the table, gets a cookies set with settings for all 5 columns
3. Subsequently a column is dropped from the table and the AJAX data set
4. Person with 5 column cookie revisits the site, gets the 'Warning - added data does not match known number of columns' popup error
The solution is to verify the data in the cookies against the actual number of TH's in the THEAD or in the oColumns parameter. Around line 4096 of the javascript is about right. Sorry for not submitting an actual patch myself!
Chris
1. Table is set up with an AJAX data source with 5 columns
2. Someone uses the table, gets a cookies set with settings for all 5 columns
3. Subsequently a column is dropped from the table and the AJAX data set
4. Person with 5 column cookie revisits the site, gets the 'Warning - added data does not match known number of columns' popup error
The solution is to verify the data in the cookies against the actual number of TH's in the THEAD or in the oColumns parameter. Around line 4096 of the javascript is about right. Sorry for not submitting an actual patch myself!
Chris
This discussion has been closed.
Replies
* FF 3.5
* IE 8
* IE 6
There will be a fix for this in 1.5.3 which should be released soon. Just looking for someone else to confirm that my fix works for them (care to volunteer? http://www.datatables.net/contact ), and a couple of other minor fixes to be included.
Regards,
Allan