Replies

• mihomes Posts: 165Questions: 23Answers: 0

  January 2014

  Anyone? Allan if you see this could you pass some advice or possibly when you expect 1.10 to be 'released' including docs and examples?
• allan Posts: 63,383Questions: 1Answers: 10,449 Site admin

  January 2014

  Sorry for the delay in replying. I've been traveling this week.
  
  Personally, I'd use 1.10 - as its new API is the way forward for DataTables as a whole. However, as you note, there is currently no documentation for 1.10's new API... I'm actively working on that as fast as possible and hope to have a preview up early next week. If you can wait that long, I'd go with that.
  
  1.10.0 release is going to be about a month after the beta is released, so perhaps mid-February.
  
  Allan
• mihomes Posts: 165Questions: 23Answers: 0

  January 2014

  I noticed the traveling message after posting - sorry about that and hope the holidays treated you well!
  
  Thanks for the information Allan... I think I will take a look at 1.10 again today and see if its something I might be able to work with. I guess the other question I should have asked is if the plugins will be updated as well... in particular TableTools when 1.10 is out?
• allan Posts: 63,383Questions: 1Answers: 10,449 Site admin

  January 2014

  Yes - I'm planning to release the plug-ins before the 1.10 beta is out. The "nightly" versions are all compatible with DataTables 1.10 already.
  
  Allan
• mihomes Posts: 165Questions: 23Answers: 0

  January 2014

  Thanks. I have some time available tonight so I think I will play around with it and see what happens..
• mihomes Posts: 165Questions: 23Answers: 0

  January 2014

  Just tried server-side with 1.10. I am not getting any errors, but the table is showing ALL rows from the db. The funny thing is the info (showing x to x of x entries) is correct and changes correctly when I do a search or use pagination, but the table still shows all rows. Even if I do the sort records and choose 50 for example the information area will be showing 1-50, but all 300+ rows (in my case) are shown.
  
  Any ideas? I did not modify the server-side processing script or the ssp.class.php other than entering my own db connection settings.
• mihomes Posts: 165Questions: 23Answers: 0

  January 2014

  Scratch that... I was using old naming in the table initialization like sAjaxSource and bProcessing... changed those to the new names and it works as expected.
• allan Posts: 63,383Questions: 1Answers: 10,449 Site admin

  January 2014 edited January 2014

  To explain what is happening here, DataTables 1.10 uses a more modern approach for sending the parameters needed for server-side processing when the `ajax` option is specified. The new ssp.class.php script uses this new method.
  
  The old method is still available and will automatically be used when sAjaxSource is used as the parameter to specify the Ajax URL. It can also be enabled using `$.fn.dataTable.ext.legacy.ajax = true;` .
  
  As such, it is fully backwards compatible, but if you update to use `ajax` then you must also update the server-side scripts (unless you specify the legacy flag).
  
  This is noted in the documentation I have been writing for 1.10, which will be published soon.
  
  Allan