Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.After activating the views_bulk_operations module, Create a new page view and select "Bulk Operations View" as the view type, save it. Then browsing to this view, I got a lot of warnings:
No operations are enabled. You must enable one or more operations in order to use Views Bulk Operations.
No operations are enabled. You must enable one or more operations in order to use Views Bulk Operations.
...
But I can't found any instruction: Where can one enable the operations?
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | No_operations_enabled.jpg | 34.22 KB | astra |
Comments
Comment #1
infojunkieOn the view page, you should see a new tab called "Operations". Does this not appear for you?
Comment #2
astra commentedI group my a few view pages by setting with the menu as tabs. On the view page I can see my menu tabs but NOT other tab "Operations" from the module Views Bulk Operations.
However, if configure these view pages WITHOUT using the menu as tabs, I can see those tabs, such as "View", "Edit", as well as "Operations". So I can set something on the Operations' page.
Whold this feature be possible to support view pages with menu as tabs?
Comment #3
infojunkieTo reproduce this, I need to "view pages with menu as tabs". Can you tell me what that means and where to activate this feature?
Comment #4
astra commentedSee the attachment that shows "4 view pages with menu as tabs", which can be set on the edit page of the Views module. Through this attachment, now you can see a selected view page with a menu tabed as "in Print".
The problem is: if set "Bulk Operations View" as the view type for this kind of view pages, I can't see the "Operations" tab enabled. Is there perhaps tab conflict between the two modules?
Comment #5
infojunkieThanks for your clarification. Here's what I did:
* Override the default Bulk view "admin/content/node2" and add a tab menu entry to it called "A"
* As a result, the view displayed "A" on the first level of the tab menu and the view operations ("Edit", "Clone", etc., "Operations") on the second level of the tab menu.
* Clone the overridden view, change URL to "admin/content/node3" and add a tab menu entry called "B"
* As a result, both "A" and "B" showed whenever I opened the view as first level tab menu, with the other operations on the second level.
Can you confirm that this happens on your end (I'm using the latest release 5.x-1.x-dev release) ? How does your case differ from the scenario described above?
Comment #6
astra commentedI have a test:
For the view pages with menu as FIRST level tab, the "operations" tab can show up and looks work well, Even though it doesn't work for them set with SECOND level tab menu.
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.