I am looking for a way to limit users on the amount of flagging per content type?

More info:

I have a view that displays 50 node titles of the same content type and I want to create a component so users may flag (using VBO) a limit of 5 only? After that I may clone the component and change it from 5 to 1 or 10 or 20 this way I may apply these components to more views assigning them inside a VBO field? Does this module support that?

CommentFileSizeAuthor
#1 flag_limit.PNG13.45 KBotcassetmgmt

Comments

otcassetmgmt’s picture

StatusFileSize
new13.45 KB

Users may select 6 or more please if anyone knows what is wrong the configuration is in the pic

aschiwi’s picture

Component: Miscellaneous » Code
Assigned: otcassetmgmt » Unassigned
Category: feature » support

I was hoping to do a similar thing: Allow users to flag 3 nodes and not more. The description looks like it does that, but all I get with this module enabled is this message when flagging (first click for each flag)
An HTTP error 200 occurred.

@otcassetmgmt Assigning yourself to an issue is for when you plan to fix it.

otcassetmgmt’s picture

Using Rules you can configure a component or a rule in the event "a node has been flagged_your_flag" and use the action "Trim a flag" this will only allow users to flag the amount you set. If you need to use this in other places create a component. To learn how do a google search for Node One and watch the Rules Framework. Good luck

aschiwi’s picture

@otcassetmgmt Thanks for your answer. A module with just a few settings would be easier than using rules and since it's here I was hoping to be able to use it instead of creating a rule. Trimming a flag is not very user friendly, plus the oldest flag gets trimmed, which would lose the user's first selection. We would have to find a way to build a rule that does what this module does - see if the user has already flagged 3 things and if so, display a message and not allow another flag. Using js flags with rules messages or page reloads doesn't seem to be easy to do, I guess we will first look into why this module isn't working, I assume it's because something has been changed in flag since the last release of this module.