Posted by mrtoner on October 24, 2007 at 7:05am
Jump to:
| Project: | Site User List |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
What am I doing wrong here? Instead of using the View User Column, I want to make a member's name (a Profile field) clickable -- taking me to the user's profile. This works well when I'm using the User ID, but not when using the User Name. That is, a template of
<a href="user/@uid">@profile_real_name</a>
produces a valid link, but
<a href="user/@name">@profile_real_name</a>
produces a link like domain.com/user/@name
Don
Comments
#1
one suggestion use l() function instead of <a> tag it will be useful while you use pathauto and other seo modules
#2
Well, I don't know what I'm doing, so when I used
return l("@profile_real_name", "user/@name")as an eval'd template, it didn't work. However, I learned something about Site User List that I didn't know. When I made User Name (with a template of "@name") a hidden field instead of a "not displayed" field, @name was substituted in the template for Real Name:
<a href="user/@name">@profile_real_name</a>So, the appropriate field being substituted must be used or hidden in the list. Hope that makes sense.
Don
#3
Once a name is made clickable is there a way to carry that name into the next form? I have the name being clickable and opening a webform when it is clicked. Is there a way to include this name in a prepopulated field at the top of this webform? The situation that I have is one where someone logs into the site and can see a list of certain users thanks to the site user list module. They click on a name in the list in order to evaluate them. So the attached webform needs to have the name of the person being evaluated (the name clicked on in the list) at the top in a text field so that we know who it is for.
#4
#5
#6
Going to close this (again): if you have a support request, please file a new issue instead of hijacking a 3+ year-old closed issue that's only tangentially related to yours.