Just noticed that some of our VBO views do not show the Operations tab and nor do they allow access to the "operations" settings to choose which actions are configurable. The common thread is that each of these views contains more than 1 arg, i.e., is comprised of subpaths.

So, the VBO view for /published shows the Operations tab and allows setting which actions can be executed by accessing /published/operations.

However, the VBO view for /published/archived does not show an Operations tab and when I try to manually access /published/archived/operations it just redirects me back to the view.

Any ideas on how to get around this so I can make changes to the /published/archived VBO operations?

Comments

btully’s picture

btully commented
Title: VBO Operations settings not accessible for views with subpaths? Tab does not appear if view has more than 1 arg() » VBO Operations settings missing for views with subpaths? Tab does not appear if view has more than 1 arg
infojunkie’s picture

infojunkie
Location Vancouver
commented
Assigned: Unassigned » infojunkie

I am not getting this problem. The default VBO shipped with this module has URL admin/content/node2 and the "Operations" tab shows fine. I tried creating new views with multi-arg URLs and the tab showed still. There must be something else that causes this. Try to insert a var_dump($path); after line 76 and make sure the code does get there. Keep me posted.

jonathan_hunt’s picture

jonathan_hunt commented

I ran into this issue when I was using a View with an argument. No sign of the operations tab. If I handcrafted the URL admin/build/views/[viewname]/operations, then checked the checkboxes and submitted the form, I found the View would then work with the argument passed.

infojunkie’s picture

infojunkie
Location Vancouver
commented
Status: Active » Fixed

I was able to reproduce something close to this and I checked in a fix. Please try the latest -dev version. Thanks!

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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