VBO: Custom access for Views bulk operation¶
Available since: 1.0.0
Provided tokens
| Token | Description |
|---|---|
[event] |
The event. |
[event:view] |
The view config entity. |
[event:view:id] |
The view ID. |
[event:view:display_id] |
The display ID. |
[event:action] |
The action plugin. |
[event:action:plugin] |
The ID of the action plugin. |
[event:action:config] |
An array with key value pairs of the configuration of the plugin. |
[event] |
The event. |
[event:machine_name] |
The machine name of the ECA event. |
[session_user] |
The user account that dispatched the event, regardless if ECA is processing models under a different account. This is only available if ECA is configured to always run under a specific account. |
Fires during the access check to determine whether the current user can see and use a particular bulk operation. Use the VBO: Set custom access action to grant or deny access.
Requires ECA bulk operations field
The operation name filter only works when the View uses the ECA bulk operations Views field plugin, not the standard VBO field.
Fields¶
Operation name-
Important note: The operation name is only available, when the operation got executed from the ECA bulk operations Views field plugin.
The operation name to check access for. Only available when using the ECA bulk operations Views field plugin.
Optionally restrict by view ID-
Optionally restrict to a specific View by machine name. Leave empty to react to all Views. Comma-separated for multiple values.
Optionally restrict by view display ID-
Optionally restrict to a specific View display (e.g.,
page_1,block_1). Leave empty to react to all displays. Comma-separated for multiple values.