Views AJAX not working for table sorting

What do you mean by not working? Not displaying the view? Not sorting? Not executing the operation? Please send a more detailed report including steps to reproduce, observed behaviour and expected behaviour. Thanks!

Thanks, I was able to reproduce that behaviour. I'll be working on it during the next few days. What happens when you submit the form?

I committed a fix that should be available in a few hours. Please download the latest 6.x-1.x-dev when the date on it changes to Nov 14th. Let me know how it works for you.

Yes I found it as well and that's what I was waiting for you to confirm. It's not a VBO dump so I'll try to track this down. Thanks for your patience :-)

Good point. I have started debugging this issue and it seems that Views changes the action on *all* forms of the view (not just the pager and exposed filters) to point to view/ajax. I'll be looking for a way to defuse that behaviour cleanly. If you can provide some help there you're more than welcome :-)

An additional problem introduced by Ajax sorting is that the extra table row used by VBO to allow selection of all nodes across all pages is deleted upon sorting. That's another thing that needs to be handled.

Fixed in the latest 6.x-1.x-dev. Please wait 12 hours before Drupal refreshes the release.

FWIW, here's a description of the problem and its solution:

Views Ajax refreshes the whole view by rebuilding it on the server and replacing the DOM of the page with the newly built fragment. For some reason, it overrode the action of the VBO form to point to views/ajax instead, although it only needs to do this on its own forms. Also, because VBO attaches JavaScript events via jQuery, these bindings are lost when the old fragment is replaced.

After going through the code of views/includes/ajax.inc & co., I found that hook_ajax_data_alter() gets called before sending the newly-built view to the Ajax caller. The object being sent back includes an array of callbacks that the JavaScript will call to perform the response handling. So I wrote my own JS callback Drupal.vbo.ajaxViewResponse() and added it to the array in views_bulk_operations_ajax_data_alter(). On the client, the callback replaces the incorrect form action with the correct URL (saved during the initial rendering of the form), and re-installs the event bindings where they should be.

Infos: http://drupal.org/node/158859#comment-580684

This is issue is not fixed. I've got 6.x-2.3 installed and the table sorting AJAX still does not work. It refreshes the page completely.

Reopened to investigate. Thanks.

Works for me. The selection is lost, yes, but the page isn't refreshed, as far as I can tell. What version of VBO are you using?

Don't work for me when i have a date exposed filter.

Without date filter, no problem

EDIT :
In fact, the problem appears when view display no result at the first load. So don't display the bulk form.

EDIT2 :

Adding

drupal_add_js('misc/tableselect.js');
  drupal_add_js(drupal_get_path('module', 'views_bulk_operations').'/views_bulk_operations.js');
  drupal_add_css(drupal_get_path('module', 'views_bulk_operations') . '/views_bulk_operations.css', 'module');
  drupal_add_js(array('vbo' => array('url' => url($_GET['q']))), 'setting');

in init function fix the bug, but there is always a problem width date field ....

I can confirm that there's a problem with the date filter. With me, seems that the initial values of the exposed date filter (which is marked as optional) cause the view *not* to find any matching nodes, which throws off VBO (and Views). Can anybody confirm this or describe another scenario?

I'll be investigating the filter more closely, time permitting.

I've closed this issue and opened another one (#445118: Date filter loses selection values) concerning the date filter specifically. If anyone is encountering a problem *without* a date filter, please re-open this issue.