Search

Fixed! Thanks! Chris

Great - thanks for the update! Allan

Thanks again for your help.

Interesting one! I've not come across this specific issue before, but it sounds like the entry button is triggering another event for some reason. Are you able to link to the page you are working on so I can take a look and debug it? Thanks, Allan

hrome seem to handle rendering of datatables more or less the same when the width styles attached to the th elements are disabled Its a Chrome 30 bug - see the discussion here: http://datatables.net/forums/discussion/17714 . The good news is that they've fixed it - we are just waiting from them to push up the update. Allan

wow I'm lazy, I should have updated this post sooner. Allan and philse thank you for the input. Given in our case we don't need at this point to absolutely control the numbering, i.e. if you click up that means you want this item to take the position field value of the one above it (regardless if that is a larger or smaller number) so we don't disable filtering. Or to put it another way the numbers in this instance mean nothing other than ordering data for display, 'this before that', 'that after this', so a number sequence might end up being along the lines of: 1,2,10,15 etc. It just means things are where we need them with minimal processing. To that end I found this snippet of code in the docs for editor. [code]// Automatically submit an edit without showing the user the form editor.edit( TRnode, null, null, false ); editor.set( 'name', 'Updated name' ); editor.set( 'access', 'Read only' ); editor.submit();[/code] Using this and what I had previously managed, which was knowing the position I wanted a record to be I could submit that change silently via the form and have our DB procedure work out the rest. Really happy with the result. Thanks.

I can't speak for the Editable plug-in, but: I've seen Editor but it seems to favor PHP for the server-side end Editor does indeed ship with a complete PHP server-side implementation, but the client-server communication protocol is fully documented here: http://editor.datatables.net/server/ - allowing it to work with any server-side environment. We have plans for C# and Node.js server-side implementations in future. Regards, Allan

Please do not cross post: http://datatables.net/forums/discussion/12157 . It specifically says that in the 'New Discussion' instructions. Allan

If you set the width to 100% that will retain fluid layout: http://datatables.net/release-datatables/examples/basic_init/flexible_width.html . However, without that, no currently the width must be set by DataTables, otherwise the columns can jump on paging and it causes a raft of issues in IE. Allan

Hi, This is a bug in 1.2.0 - thanks for pointing it out. A fix will be included in 1.2.1, which will be released next week. The problem is that TableTools isn't loaded on that page, and although Editor should work just fine without TableTools, the bug is that there is a reference to TableTools, when out checking for its existence first. For the moment, if you look int he _constructor function, you'll find var ttButtons = window.TableTools.BUTTONS; . That, and the block below it should be enclosed by if ( window.TabelTools ) . Regards, Allan