Possibly a bug with server side processing

Possibly a bug with server side processing

MathObsessedMathObsessed Posts: 7Questions: 0Answers: 0
edited July 2012 in DataTables 1.9
Hello again, Allan!

I feel sorry to bother you again but it seems that I've hound a bug in your plugin. The deal is:

1) I create a DataTable instance with server-side processing.
2) I'm trying to use your new cool feature - oTable.$("selector") function inside a "fnInitComplete" function
3) I recieve a JavaScript error like "a is null" and it seems to be a jQuery function error not DataTables plugin function...

So I assume the plugin is trying to call something like $("selector", container) of a standart jQuery but there is no "container" variable because I use async request... Can you help me with this problem please? Or if I missed something can you show me a topic in documentation that describes this kind of behavior?

My initial problem is - I need to check some previously checked checkboxes inside of my table, and this table appears in a modal window with the help of an AJAX request. All was fine with previous DataTable versions, but you kinda changed the behavior of your oTable.fnGetNodes() function since then... In prev versions this function returns ALL nodes (on all pages including insivsible nodes), nowadays it returns only visible nodes! I really think that now this function does what it HAS to be done, but your new $() function doesn't seem to work as one could expect! And moreover - there seems to be no sign of handling an error or at least a documented case for this!

~Ernest Lebedev
This discussion has been closed.