Replies

• TomC Posts: 43Questions: 0Answers: 0

  April 2010

  Your features are mutually exclusive.
  
  You can't logically update a table that may not show the update. It is a huge UI mistake too. What page do new messages show up on? Are you always sorting by date?
  
  You might consider a panel near the table that shows when new messages have been received but not loaded then the user would manually reload the table which should reset it to a state that shows the new messages. Reloading something and having a possibility of not showing the new information is just a bad User Experience.
  
  I would take your requirements back to your Product Management or I totally missed your point.
• Morrigan Posts: 10Questions: 0Answers: 0

  April 2010 edited April 2010

  Hi Tom,
  
  I thought so too, honestly. They aren't always sorted by date, though it's the default sort (newer messags on top). But I did think it was pretty silly. I'll have to talk to them when I get the chance (they're in France and I'm in Canada so it's not that simple), but in the meantime, there's really no way to do that, then?
  
  Also, this doesn't address the first issue I have. If I do refresh through the browser, it seems to "half" remember it's on page 2. Page 2 is pre-selected, but the data displayed is from page 1, and it says "Showing 11 to 20 of total 12 entries" which makes no sense...
• Morrigan Posts: 10Questions: 0Answers: 0

  April 2010

  Hello,
  
  I have discussed with our product manager and we decided to change the behaviour, so point 2) is moot now.
  
  But I still have the problem described in 1). Can anyone help?
  
  To re-iterate: If I select page 2, and refresh through the browser, page 2 is indeed pre-selected, but instead of displaying "Showing 11 to 12 of total 12 entries" and displaying the last 2 rows, it says, "Showing 11 to 20 of total 12 entries" (not very logical) and it shows the first 10 results from page 1.
• fastbike Posts: 14Questions: 0Answers: 0

  May 2010

  I'm getting the same problem. If page 2 is selected in the table, when we return to the page hosting teh table, the pagination control shows page 2 but the data returned from the server is page 1.
  
  I'll take another look to see what the error is (could be something like the Ajax call asking for page 1 and then the StateSave cookie changing the paginator to page 2 ?)
• fastbike Posts: 14Questions: 0Answers: 0

  May 2010

  I've looked at updating the value of the iDisplayStart paramter before fetching the data from the Ajax URL.
  If I use the value stored in the cookie it works fine for the first load of the page (i.e reloading the data that corresponds to the previous page view) but on each subsequent table paginate event (e.g. clicking a page number button) it is always using the page number from the previous event.
  
  Here's some code snippets:
  [code]
  $(document).ready( function() {
  tblManualCRReferrals = $("#ManualCRRReferrals").dataTable( {
  ...
  "fnServerData": getServerData
  });
  });
  
  function getServerData( sSource, aoData, fnCallback ) {
  var oData;
  var sData = this.oApi._fnReadCookie("SpryMedia_DataTables_" + this.sInstance);
  if (sData !== null && sData !== '') {
  /* Try/catch the JSON eval - if it is bad then we ignore it */
  try {
  /* Use the JSON library for safety - if it is available */
  if (typeof JSON == 'object' && typeof JSON.parse == 'function') {
  /* DT 1.4.0 used single quotes for a string - JSON.parse doesn't allow this and throws an error. */
  oData = JSON.parse(sData.replace(/'/g, '"'));
  }
  else {
  oData = eval('(' + sData + ')');
  }
  }
  catch (e) {
  return;
  }
  
  for (var i =0; i < aoData.length; i++) {
  if (aoData[i].name == "iDisplayStart") {
  aoData[i].value = oData.iStart;
  break;
  }
  }
  }
  
  // tell DataTables to get on with it
  $.getJSON( sSource, aoData, function (json) {
  if (json.sError != undefined) {
  alert(json.sError);
  }
  fnCallback(json)
  });
  }
  [/code]
  
  So next step is to differentiate between loading the whole page (use values from the cookie) and a data refresh (use values from the pagination control).
• fastbike Posts: 14Questions: 0Answers: 0

  May 2010 edited May 2010

  I've fixed this problem with an extension method. Here's my final code snippets.
  
  [code]
  
  $.fn.dataTableExt.oApi.fnFixPaginationParams = function(oSettings, aoData) {
  if (oSettings.newPage == undefined) { // is this the first time a page load has been requested
  var oData;
  var sData = this.oApi._fnReadCookie("SpryMedia_DataTables_" + oSettings.sInstance);
  if (sData !== null && sData !== '') {
  // Try/catch the JSON eval - if it is bad then we ignore it
  try {
  // Use the JSON library for safety - if it is available
  if (typeof JSON == 'object' && typeof JSON.parse == 'function') {
  // DT 1.4.0 used single quotes for a string - JSON.parse doesn't allow this and throws
  // an error. So for now we can do this. This can be removed in future it is just to
  // allow the transfer to 1.4.1+ to occur
  oData = JSON.parse(sData.replace(/'/g, '"'));
  }
  else {
  oData = eval('(' + sData + ')');
  }
  for (var i = 0; i < aoData.length; i++) {
  if (aoData[i].name == "iDisplayStart") {
  aoData[i].value = oData.iStart;
  break;
  }
  }
  }
  catch (e) {
  // do nothing
  }
  oSettings.newPage = true;
  }
  }
  }
  
  var tblManualCRRReferrals;
  $(document).ready( function() {
  tblManualCRReferrals = $("#ManualCRRReferrals").dataTable( {
  ...
  "fnServerData": getServerData
  });
  });
  
  function getServerData(sSource, aoData, fnCallback ) {
  if (tblManualCRRReferrals == undefined) {
  return;
  }
  tblManualCRRReferrals.fnFixPaginationParams(aoData);
  // tell DataTables to get on with it
  $.getJSON( sSource, aoData, function (json) {
  fnCallback(json)
  });
  }
  
  // load the data into the table
  jQuery(document).ready(function() {
  tblManualCRRReferrals.fnDraw();
  });
  [/code]
  
  See also my thread "Extensions not available when loading"
  http://datatables.net/forums/comments.php?DiscussionID=2015&page=1#Item_1
• fastbike Posts: 14Questions: 0Answers: 0

  May 2010

  With the changes in v1.7 (currently in beta) this code gets even simpler, no longer having to work around the uninitialised global datatable var.
  
  [code]
  $.fn.dataTableExt.oApi.fnFixPaginationParams = function(oSettings, aoData) {
  if (oSettings.newPage == undefined) { // is this the first time a page load has been requested
  var oData;
  var sData = this.oApi._fnReadCookie("SpryMedia_DataTables_" + oSettings.sInstance);
  if (sData !== null && sData !== '') {
  // Try/catch the JSON eval - if it is bad then we ignore it
  try {
  // Use the JSON library for safety - if it is available
  if (typeof JSON == 'object' && typeof JSON.parse == 'function') {
  // DT 1.4.0 used single quotes for a string - JSON.parse doesn't allow this and throws
  // an error. So for now we can do this. This can be removed in future it is just to
  // allow the transfer to 1.4.1+ to occur
  oData = JSON.parse(sData.replace(/'/g, '"'));
  }
  else {
  oData = eval('(' + sData + ')');
  }
  for (var i = 0; i < aoData.length; i++) {
  if (aoData[i].name == "iDisplayStart") {
  aoData[i].value = oData.iStart;
  break;
  }
  }
  }
  catch (e) {
  // do nothing
  }
  oSettings.newPage = true;
  }
  }
  }
  
  var tblManualCRRReferrals;
  $(document).ready( function() {
  tblManualCRReferrals = $("#ManualCRRReferrals").dataTable( {
  ...
  "fnServerData": getServerData
  });
  });
  
  function getServerData(sSource, aoData, fnCallback ) {
  // "this" now refers to the global var
  this.fnFixPaginationParams(aoData);
  // tell DataTables to get on with it
  $.getJSON( sSource, aoData, function (json) {
  fnCallback(json)
  });
  }
  [/code]
  
  Many thanks to Allan for the update.