Joachim, could you look at the request in #912704: Users post in own "username" dir., please. It's an interesting concept that I think fits better with this module. Basically, rather than assigning a term to the user, the username becomes the term in a vocabulary. I've done similar things in other modules, so I don't think this would be a terribly difficult addition here.

Comments

joachim’s picture

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

It's an interesting feature request.

Though on several fronts, I think it's out of scope of this module.

It's certainly a link between users and terms, but it's conceptually different: user terms lets you categorize users with any terms; the suggested feature is to do with creating a 1-1 link with a term that represents the user, with all the synchronization that implies. I don't think that much if indeed any code of user terms would find common use. You *might* want to use the term_user table to store the association, but really, that's not terribly good data storage as you'd be forced to use a join onto term_data to get hold of the vocab id if you wanted to retrieve the term for a given user, as there would be other term to user associations in there.

So I think if this were to be coded, it's a completely separate project, albeit one in a same corner of the Drupal box of lego ;)

Though -- does this even need code? Why not use Views to create lists of weblinks (or any node) per user? Alternatively, if there's a need to use something other than the node author, a module that automates a userreference field might be another way to do it.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Synchronization with the user table is not a big deal; I already do that in RealName.

I can't rely on the term_user table if I create a new user, because they may not also have this module. Joining term_user and term_data is also no biggie; my modules for my current customer do a lot of that.

Views might be a good choice, but I don't understand Views programming adequately to get anywhere with that, which is why Web Links has only minimal Views support. Using parts of CCK on the front-end is way out my ballpark. However, using author instead of a term is an interesting thought since WL does not require a taxonomy.