The "Merge single action's form with node selection view" setting is cool, and a step in the right direction. However, over at #357565-8: Port signup_status to Views2 I've run into a case where I've got a default VBO view with 4 actions. Only one of them is configurable, the others are not. What I'd love is a hybrid of the "Merge ..." setting with the "Each action as a separate button" setting. See attached (crude) mockup. ;)

There are 3 screenshots:

  1. VBO-1-configurable-action.png is a picture of the existing "Merge single action's form with node selection view" setting at work on the default view if I only give it that 1 action.
  2. VBO-N-actions.png is a picture of the same view with all 4 actions enabled, using the "Each action as a separate button" display setting.
  3. VBO-hybrid-1-config-N-nonconfig-actions.png is a crude mockup of what I'd really love -- a hybrid of both. Since there's only 1 configurable action, that action's form appears along with the view, and you get the button to execute it at the bottom, but you also get the other buttons for the non-configurable actions if you want to use one of those...

Any thoughts on this? ;)

Thanks!
-Derek

Comments

infojunkie’s picture

This is quite a special case! IMO, the scenario "one configurable action and N nonconfig actions" is unlikely to come up for many users, and thus I am not inclined to hard-code it into VBO. Here's what I suggest:

Use hook_form_alter() in your module to alter views_bulk_operations_form to implement your UI logic. You'll just need to make sure to set $form_state['storage']['step'] and other values correctly so that validation and submission can proceed. The advantage is that you can change your UI logic if the above turns out to be insufficient, without needing to revert to hacking VBO every time. I can help with testing and debugging.

Hope this helps :-)

infojunkie’s picture

Status: Active » Closed (won't fix)