What I'm proposing is kinda what you get on StumbleUpon:

Example: user signs up and creates a content profile which is a node and which has Tags field "Interests". There he lists all the tags that she is interested in. Once the profile node is submitted Flag Terms module takes those tags and marks them as flagged.
(Of course in Flag Terms settings page the admins would have a choice to designate a particular field in a particular content type as the Taxonomy field from which the flagged terms are to be extracted)

Why create this feature? Right now the user has to list his interests in his profile. THEN he has to take a second and third and fourth and many more steps to go to each of those taxonomy term pages in order to flag them. That's very inefficient and is an example of bad user experience. So once he has listed his interests in one field, those terms should already be marked as flagged.

Comments

tayzlor’s picture

tayzlor commented

hi drupalina,
what you could do is write a small piece of code in hook_nodeapi() (perhaps in the presave op) which would do something like this -

  • get the select terms on the node object
  • foreach selected term
  • flag the term by calling the flag_flag() (or $flag->flag()) function.

this would be a relatively small piece of code to write and would fit your solution.
Otherwise, what would the UI look like for your feature request ? - my initial feeling is it could be quite cumbersome if there are many content types and many cck fields on the website.
Additionally, the amount of extra work is quite high in order to meet this UI / functionality versus the above solution (which is quite simple to implement).

queryblitz’s picture

queryblitz commented

This seems like more of a Rules integration thing. I'd like the same thing, so I'm going to try to see if I can do it through rules.

Similar conversation here: http://drupal.org/node/242870

tayzlor’s picture

tayzlor commented
Status: Active » Closed (won't fix)