Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
You aren't missing something, there isn't such an option.
This reminds me of the "have separate permissions for unflagging" feature request. Perhaps we can devise some framework, some hook, that vetoes a flag/unflag operation.
I think this would be an appreciated feature. Think of a drupal powered filckr-like site. People shares pictures and bookmarks interesting one. It wouldn't make any sense to bookmark own pictures, isn't it? So, I guess, it would be really cool to develop a kind of system to do that.
People shares pictures and bookmarks interesting one. It wouldn't make any sense to bookmark own pictures, isn't it?
This example isn't very good. It isn't "wrong" to flag a picture of yours. And if it's a "sold!" flag then it's actually makes sense to flag your nodes only.
==
Frankly, I'm not sure this module is the best for bookmarking pictures/films: you'd want to have different folders (amazing, weird, artsy, celebs, nature), not one basket.
This is true but I think I didn't explain well what I'm looking for.
I'm just talking about an option to prevent users from flagging their own content.
E.g. I'm developing a site for sharing recipes. Each user can bookmarks others recipes and retrieve them later in a "my bookmarks page". In this case it's not useful to bookmark my own recipes since they're listed in my personal page. Flickr has a system like this and I think it could be a useful feature that fits well in this module. Probably all we need is a "prevent users from flagging their own content" checkbox in the flag settings page.
Separate permissions for unflagging is something different; probably more useful with global flags. e.g in a project management site we could have tasks that certain roles can flag as active but only a different role (the task manager?) can flag it as inactive(complete). This would be cool but, I think, is a different feature.
Anyway I will try to post a patch if I'm smart enough to understand how to code it.
And thanks for taking time to answer.
Ok. Many thanks. I close this one. I didn't mean to insist, but since I'm not english, everytime I fear people don't understand what I'm saying. Thanks again for your patience.
Comments
Comment #1
mooffie commentedYou aren't missing something, there isn't such an option.
This reminds me of the "have separate permissions for unflagging" feature request. Perhaps we can devise some framework, some hook, that vetoes a flag/unflag operation.
Comment #2
dodorama commentedI think this would be an appreciated feature. Think of a drupal powered filckr-like site. People shares pictures and bookmarks interesting one. It wouldn't make any sense to bookmark own pictures, isn't it? So, I guess, it would be really cool to develop a kind of system to do that.
Comment #3
mooffie commentedThis example isn't very good. It isn't "wrong" to flag a picture of yours. And if it's a "sold!" flag then it's actually makes sense to flag your nodes only.
==
Frankly, I'm not sure this module is the best for bookmarking pictures/films: you'd want to have different folders (amazing, weird, artsy, celebs, nature), not one basket.
Comment #4
dodorama commentedThis is true but I think I didn't explain well what I'm looking for.
I'm just talking about an option to prevent users from flagging their own content.
E.g. I'm developing a site for sharing recipes. Each user can bookmarks others recipes and retrieve them later in a "my bookmarks page". In this case it's not useful to bookmark my own recipes since they're listed in my personal page. Flickr has a system like this and I think it could be a useful feature that fits well in this module. Probably all we need is a "prevent users from flagging their own content" checkbox in the flag settings page.
Separate permissions for unflagging is something different; probably more useful with global flags. e.g in a project management site we could have tasks that certain roles can flag as active but only a different role (the task manager?) can flag it as inactive(complete). This would be cool but, I think, is a different feature.
Anyway I will try to post a patch if I'm smart enough to understand how to code it.
And thanks for taking time to answer.
Comment #5
mooffie commentedYou explained well.
That's no good. We need a more general mechanism. A user has just asked the opposite: to be able to flag as 'complete!' his own nodes only.
dodazzi, the checkbox you propose will suit only you. It won't answer the needs of other people.
I've just opened a feature request: #285237: Ability to disallow a flag/unflag operation (If you're fine with that feature, please close the current issue; or voice your opposition there.)
Comment #6
dodorama commentedOk. Many thanks. I close this one. I didn't mean to insist, but since I'm not english, everytime I fear people don't understand what I'm saying. Thanks again for your patience.