I am using Flag 7.x-3.0 and VBO on my site and love its functionality. My site allows all authenticated user to "Favorite" a node using Flags, and the users don't come across the term "Flag" anywhere on the site.

On the site's user account page, I have a view that shows the authenticated users their Favorite nodes. I want to allow the users to unfavorite the nodes using VBO Flag action. I selected the "Skip confirmation step" on the VBO Action, but then the users are presented with the Flags confirmation screen - with options "Flag to affect" and "Flag operation". So basically users are still presented with another confirmation screen. My users are not dumb and can figure out whats going on, but this is not very UX friendly in general.

This merging of actions is not consistent with other VBO actions, Publish Content, Unpublish Content, Make Content Sticky, Make Content Unsticky and so on..

Since the confirmation screen seems necessary for users to select which Flags are to be used when performing the VBO action, I was wondering if this process can be moved to the individual Flag settings page itself where admins can select which Flag types can be associated with specific views. By default all views can be set to be selected so new module users are not confused but the customization for VBO usage can still be performed for use cases that require such granularity. The second part of the request would be as stated, can the actions be split between Flag and Unflag to be consistant with other VBO actions?

Also if this can behavior can be achieved through custom code or other settings please let me know. I couldn't find it. Thanks.

Comments

acidpotato’s picture

Title: Split Flag VBO Action to Flag VBO Action and Unflag VBO Action » Split Flag VBO Action to two separate actions - Flag VBO Action and Unflag VBO Action
joachim’s picture

> This merging of actions is not consistent with other VBO actions, Publish Content, Unpublish Content, Make Content Sticky, Make Content Unsticky and so on..

That's a good point.

> this process can be moved to the individual Flag settings page itself where admins can select which Flag types can be associated with specific views.

If you mean bake something about views into the actual flag's admin settings (ie at admin/structure/flag/foo), then I don't think that would be a good thing to do at all.

I think it's more that you want some configuration options on your VBO in the view, so you can set the action to only work with one flag -- and therefore cause the action options form to be skipped.

acidpotato’s picture

Thanks for the quick response. Yes, some configuration options on the VBO in the view itself would be great and would actually work very well for my use case. Its just that I didnt see any specific customizations in other actions in the VBO so was not sure if this was possible.

joachim’s picture

> not sure if this was possible.

Me neither! Can you do some reading up on VBO's hooks?

acidpotato’s picture

Sure let me check whats going on with the VBO hooks and report back.

Scryver’s picture

You can create a custom action to take care of it. admin/config/system/actions

joachim’s picture

Version: 7.x-3.x-dev » 8.x-4.x-dev

Not sure we can change this now 7.x-3.x is a stable branch -- it would break people's existing VBO views.

Upping the version to 8.

rajesh.vishwakarma’s picture

@Scryver I have add new action and listed in VBO but how can I add my custom operation with this action.

joachim’s picture

Issue tags: +Release blocker

I'm tagging this as release blocker in the sense that we either need to tackle it before release, or postpone it for the next major version.