Views Bulk Operations adds advanced bulk operation capabilities to Drupal views, allowing users to perform actions on multiple items at once with features like configurable batching to prevent timeouts, a clear API for custom actions, and an optional confirmation step. It also includes "Actions Permissions" to control which actions users can see and perform based on their roles.
Introduction
This module provides the following features that are not available in Drupal core bulk form:
- Batching of operations with configurable batch size ensuring no timeouts.
- Simple and well documented API for creating custom actions.
- Preliminary action configuration on the view admin page or directly in view config yaml.
- Simple and well documented API for creating custom actions.
- End-user configuration form implemented with an action class method instead of workaraounds.
- Confirmation step.
- Selection persistent across all view pages.
Usage
After enabling the module, a new global field named "Views bulk operations" will become available in every view. To enable Views Bulk Operations for the view, just add and configure this field, if the core bulk operations field is enabled (for example Node operations bulk form for the "Content" view), that field needs to be replaced with the Views bulk operations field.
Complementary modules
- Views Bulk Edit provides an action to edit selected entity fields' values.
- VBO export allows exporting of the selected view rows to Excel xlsx or csv.
- Push Notifications allows sending customized Push Notifications via Firebase Cloud Messaging (FCM).
- Group Actions that provide useful actions for the Group module.
- Courier UI for sending templated messages with token support to selected users.
- VBO Action Kit that contains additional smaller actions both for site builders and to help developers to find reference code. Contributions and ideas welcome
Actions Permissions
A module called Actions Permissions is included in the package. This module generates a permission for each action, and VBO honors those permissions before showing or executing the corresponding actions. This is useful if you want to provide your VBO to several groups of users with different privileges: the same view will accommodate those different groups, showing to each the actions that they are permitted to see.
Note: While multiple 4.x minor branches are published and marked supported, only the latest minor release is actively maintained. Older minor versions remain available as to mitigate update status "unsupported" warnings but will not receive updates or fixes.