Version 3.2 of views_bulk_operations was just released:

https://drupal.org/node/2161705

It contains loads of bug fixes!

I think the only thing in Panopoly that directly uses it is the 'admin_views' module which is installed by Panopoly Admin.

I'll attach a patch in a moment.

CommentFileSizeAuthor
#1 panopoly_core-update-vbo-2163447-1.patch467 bytesdsnopek
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
CreditAttribution: dsnopek commented
Status: Active » Needs review
FileSize
panopoly_core-update-vbo-2163447-1.patch467 bytes

Patch is attached! I haven't done any testing yet.

cboyden’s picture

cboyden CreditAttribution: cboyden commented

This update will be very helpful - we want to use the new "cancel user account" action in our admin views.

lsolesen’s picture

lsolesen CreditAttribution: lsolesen commented

@cboyden You are very welcome to test out, whether the update breaks anything :) If not after extensive testing, set it to RTBC.

caschbre’s picture

caschbre CreditAttribution: caschbre commented

I've upgraded to 3.2 and so far have not had any issues.

cboyden’s picture

cboyden CreditAttribution: cboyden commented

Likewise. Upgraded to VBO 3.2 on the latest Panopoly 1.1 with no errors.

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
CreditAttribution: dsnopek commented

VBO is used exclusively by 'admin_views', which implements the following paths with VBO:

  • admin/content/book
  • admin/content/comment
  • admin/content/comment/approval
  • admin/people

I poked around on those pages doing bulk operations - everything worked fine! I searched the admin_views issue queue to see if there were any problems reported for VBO 3.2 - nothing!

I'm going to commit this.

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
CreditAttribution: dsnopek commented
Status: Needs review » Fixed

Committed:

http://drupalcode.org/project/panopoly_core.git/commit/c0edc7416e6b9d8a0...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.