I’m attempting to modify the member templates. In Member Profile Outer Enclosure, I have a navigation element that shows the logged in user’s name however it’s not being parsed in the member template. I’ve tried using {name} and {username} both of which fail to parse and just display as-is.
Any idea why this would happen? If I use {name} in the Breadcrumb template, it works… what’s preventing it from being parsed at a higher level?
The member templates parse only a subset of variables specific to each template, as they are not run through the main template engine. If you need to be able to use more variables, have a look at eewiki: Member Templates.
You’re trying to display it in the outer enclosure, not in their profile. If you want it in the public member profile, then you should edit that specific template. =)
I believe that the method for member templates was changed, in part at least, because most people do not need the power of the entire template parser for those particular templates. However, in the case that you do need that power, then you’ll need to use the alternate method. It is not a hack, either. It is simply a different way of doing things - you aren’t modifying any core files, which is what a hack would entail.
What type of performance hit (if any) are we looking at if I move the templating for the member areas (both display, and edit) to the non-Admin template area? We’re talking about a larger site, 3000 - 5000 active members.
OK, so I’m doing it the way suggested in the Wiki and man… this is a pain. Is there a way to make a template for each section? In other words, can I add a “Edit Photo” template and use that instead of having to go through the template bits in Admin > Member Templates? I’m absolutely confused by the 60 different templates and even with the Wiki article explaining them, this is just murder to have to go through. Creating them from scratch knowing which {tags} I could use would be about 5000 easier.
You’re not transferring all of the templates. The templates’ll still pull from the member templates (see the {content} in your member/index?). Does that make sense?
It makes sense, it’s just really frustrating to have to do it that way. Where the normal template area is really easy, trying to incorporate the member templates (edit / display) is driving me insane. Some tags work, some tags don’t.
Anyway, I noticed here that {breadcrumb} is used in the template and that pulls in the breadcrumb template from the Admin Member Template area. Can I do the same with the “Member Profile Form” ? I have a template built for the member area and I’m trying to include in the forms and such…
When you visit index.php/member/profile - it loads the member/index template but then pulls in the appropriate templates from the membership admin templates. This is actually a bunch of different, interconnected templates, including but probably not limitd to (as in I’ll probably miss listing): member profile form, member profile menu, member profile home page, etc. There isn’t really any way that I’m aware of to build your own forms to accomplish these goals. You need to use the ones delivered from the admin area.
The member/index pulls in those templates based off what is in the URL. So if you go to member/profile/ it builds the page as a combination of member/index and the appropriate templates in the admin area. The same goes for all member related links, such as the memberlist, public profiles, etc.
I gotta say though, this area of EE is pretty confusing. It’d be really nice if the template group stayed in the template area and you had some way of telling it to only process certain templates through the preferences area or something. Splitting up the templates makes things totally confusing.
If you have a look at the announcements forum, there is a multi page thread about the control panel demo. Somewhere in there is an explanation of why the forum and member templates are handled in this manner. It’s good reading, if you are interested =)
This makes things easy now. I’ve stripped down the Full Profile Page to just {include:content} and now I can handle the actual skeleton template with the normal template area and just manage the forms and such through the Admin Member Template area.
Thanks for pointing this thread out Lisa.
I’ve done what was described in the Wiki article, I changed the trigger word to memberme, but the “Register” link on the homepage (along with all other member-related links I suppose) still points to index.php/member/register/ wich just gives the index.php page, however, when I change the URL by hand to index.php/memberme/register/, there’s my page. Is there a way to remedy this other then changing all member EE tags by hand?
Discussion in this thread was based on information that was available here but is no longer available. Is there an alternative method for the new version of EE? We need to be able to customize our member panel area and embed templates that we use as header and footer through out the site.