I’m looking to edit the default member list so that I can show two custom fields member_first_name and member_last_name. Is there a way to do this, or do I need to make my own in the standard templates?
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
September 15, 2008 1:41pm
Subscribe [8]#1 / Sep 15, 2008 1:41pm
I’m looking to edit the default member list so that I can show two custom fields member_first_name and member_last_name. Is there a way to do this, or do I need to make my own in the standard templates?
#2 / Sep 15, 2008 4:16pm
I tried adding the following, but that gives me my last name for all of the members.
http://expressionengine.com/wiki/Member_Profile_Templates:_Getting_User_Information/
Alternatively, since I’m not going to find many of the default fields useful, is there a downside to using something like {aol_im} and {msn_im} for my first and last name fields?
One more question regarding the member profile. Are there any best ways to add a anniversary field(s) similar to the birthday field, Or do I have to do I have to populate the drop downs manually?
#3 / Sep 15, 2008 6:00pm
What about this solution:
#4 / Sep 15, 2008 7:34pm
What about this solution:
I think that’s kind of what i meant by make my own in the standard templates. I was hoping to just edit the default so that I didn’t have to do the work of adding the search stuff, not to mention making sure all of the links to memberlist get rerouted to my custom one. I added a reply to the tread that was linked in the wiki. http://ellislab.com/forums/viewthread/23806/P18/ Not sure if you guys want to merge the threads or not.
#5 / Sep 15, 2008 8:05pm
I think that’s kind of what i meant by make my own in the standard templates.
Do you know about the SolSpace User Module? Here’s a link directly to the function in the docs for the User Module that seems to do what you’re wanting to do: http://www.solspace.com/docs/entry/user_users/
The built-in EE Member controls are great. But when we need to do something custom with Members and Profiles, dropping $90 on SolSpace’s User Module is a huge time and money saver
[NOTE: I do NOT work for SolSpace. Just use and love his modules!]
#6 / Sep 15, 2008 9:26pm
I think that’s kind of what i meant by make my own in the standard templates.
Do you know about the SolSpace User Module? Here’s a link directly to the function in the docs for the User Module that seems to do what you’re wanting to do: http://www.solspace.com/docs/entry/user_users/
The built-in EE Member controls are great. But when we need to do something custom with Members and Profiles, dropping $90 on SolSpace’s User Module is a huge time and money saver
[NOTE: I do NOT work for SolSpace. Just use and love his modules!]
Thanks for the suggestion, but I don’t think i’ll be ponying up for the module. I’m a volunteer webmaster for a church, so budgets are tight, and we aren’t looking to get nickled and dimed, or fiftied and hundreded anytime we want to add something to the site.
The modules to a paid product are a blessing and a curse, as the product may decide not to add that native functionality and hurt the developer.
#7 / Sep 15, 2008 9:36pm
Know what you mean about tight budgets. We do a lot of work for non-profits and volunteer development. Some of the SolSpace modules have provided such a savings in terms of our development time that we’ll pony up the license fee ourselves just to be able to do the work faster.
In terms of ongoing support, that is always a concern. One thing to keep in mind is that Mitchell at SolSpace, and the entire SolSpace crew, seems to work closely with EE. SolSpace even threw a party with EE at the last SxSW in Austin this year. And so far, SolSpace’s Tag module is the only Third Party Certified module listed on the EE site: http://expressionengine.com/downloads/details/tag_module/
So, as a company, we’re confident that EE and SolSpace will continue to work together and support the EE dev community as they have for the past many years already.
Just my 2 cents….
#8 / Sep 15, 2008 9:49pm
Know what you mean about tight budgets. We do a lot of work for non-profits and volunteer development. Some of the SolSpace modules have provided such a savings in terms of our development time that we’ll pony up the license fee ourselves just to be able to do the work faster.
In terms of ongoing support, that is always a concern. One thing to keep in mind is that Mitchell at SolSpace, and the entire SolSpace crew, seems to work closely with EE. SolSpace even threw a party with EE at the last SxSW in Austin this year. And so far, SolSpace’s Tag module is the only Third Party Certified module listed on the EE site: http://expressionengine.com/downloads/details/tag_module/
So, as a company, we’re confident that EE and SolSpace will continue to work together and support the EE dev community as they have for the past many years already.
Just my 2 cents….
Still a different situation. I have a day job that isn’t web design related. And am getting paid nothing.
I’m not so much afraid of solspace not backing their module, but I’m afraid of ee not updating their built in code because they don’t want to hurt solspace, by making their module obsolete.
#9 / Sep 16, 2008 10:21am
I’m not so much afraid of solspace not backing their module, but I’m afraid of ee not updating their built in code because they don’t want to hurt solspace, by making their module obsolete.
We have no idea if EE 2.0 is going to make the User module obsolete. Even if it does, the 1.6.x branch will be continuing for a while.
Ultimately, you use what you have access for now.
Back to your original question:
Alternatively, since I’m not going to find many of the default fields useful, is there a downside to using something like {aol_im} and {msn_im} for my first and last name fields?
There is no downside—other than remembering what you’re replacing. 😊
#10 / Sep 18, 2008 5:33pm
I came upon this thread as I’m trying to do the same thing as the OP. I’ve settled on editing the default member templates rather than writing my own custom set with queries.
My question is how do I access custom member data from the member list rows template? It seems like these member templates don’t take anything except raw HTML, certainly not the {exp:member:custom_profile_data} tags. Any help is appreciated!
#11 / Sep 24, 2008 12:24pm
I came upon this thread as I’m trying to do the same thing as the OP. I’ve settled on editing the default member templates rather than writing my own custom set with queries.
My question is how do I access custom member data from the member list rows template? It seems like these member templates don’t take anything except raw HTML, certainly not the {exp:member:custom_profile_data} tags. Any help is appreciated!
Any progress on that? I’m running in to the same problem.
#12 / Sep 24, 2008 12:55pm
Nope, I gave up and went with the custom member list documented above. Once you figure out the EE SQL syntax, it becomes astronomically easier than changing all of the default member templates, which, as it turns out, can’t parse any standard EE or PHP code, so if you want them to do anything additional, you’re pretty much out of luck.
I think I spent close to a week pulling apart my site design and reassembling it around the member templates. Once I gave up on it, it took me about one day to get the custom list up and running.
#13 / Sep 24, 2008 1:01pm
Yeah, that makes sense. I’ll likely do the same thing. One question though: how did you implement a member search function with your member list? Did you?
#14 / Sep 24, 2008 1:27pm
This is a handy thread with some excellent brainstorming in it. I’m going to go ahead and shift it to ‘How to’ and let it run. We’re pretty far afield from stock usage at this point. But the workarounds are very handy.
#15 / Sep 24, 2008 2:21pm
Yeah, that makes sense. I’ll likely do the same thing. One question though: how did you implement a member search function with your member list? Did you?
I haven’t yet, but I seem to remember a built in EE member search tag? I could be wrong though. I’ll post here once I’ve reached that point.