Views ajax exposed filters break vbo when more than a VBO view is embedded on the same page

Thanks for the patch. I'll review it soon.

Sounds like a good idea.
Views Form does the same for us in D7.

EDIT: But VBO for D6 already does something like this:

 212     // Append suffix to avoid clashing between multiple VBOs on same page.
 213     static $form_suffix;
 214     if (isset($form_suffix)) {
 215       $form_suffix++;
 216     }
 217     else {
 218       $form_suffix = 1;
 219     }
 220     $this->form_id = 'views_bulk_operations_form__' . $form_suffix;

So the question is why does it fail? Maybe the $form_suffix gets reused?

Okay, so we actually need to modify the code I mentioned above, kill $form_suffix, and add your / D7 variant (appending view name and display name)

@bojanz, where's the code for this in D7?

In views itself (Views Form API).

/**
 * Implements hook_forms().
 *
 * To provide distinct form IDs for Views forms, the View name and
 * specific display name are appended to the base ID,
 * views_form_views_form. When such a form is built or submitted, this
 * function will return the proper callback function to use for the given form.
 */
function views_forms($form_id, $args) {
  if (strpos($form_id, 'views_form_') === 0) {
    return array(
      $form_id => array(
        'callback' => 'views_form',
      ),
    );
  }
}


/**
 * Returns a form ID for a Views form using the name and display of the View.
 */
function views_form_id($view) {
  $parts = array(
    'views_form',
    $view->name,
    $view->current_display,
  );

  return implode('_', $parts);
}

and:

  // If form fields were found in the View, reformat the View output as a form.
  if (views_view_has_form_elements($view)) {
    $output = !empty($vars['rows']) ? $vars['rows'] : $vars['empty'];
    $form = drupal_get_form(views_form_id($view), $view, $output);

@bojanz, thanks for the info. Committed similar code to D6. @kongoji, please test it and let me know.

Not sure if you have a system for flagging things as needing release notes, but this might be one of those things.

It's probably borderline but it could be considered an API change because form id changes are something that can have an effect on external code, such as CSS & form alterations.

It is probaly worth a proper notice at the top of the next release's release notes.

Whoops, too late now, since there have been releases since this fix went in. Sorry.

Updated issue summary.