Help with GetMembersByGroupName in members XSLT library
Hey all,
I am using the uComponents package, which is fantastic, and I can't find documentation or forum entries to help me list members on the front-end of my website using GetMembersByGroupName.
Can anyone help me use this method? I've had some success using apply-template, but it just spits out a single string of Names and I'd like to have more control over this.
Ideally would like to list entire profiles as stored in the membership directory. Can you help?
First the "members" template is matched, then inside there we can define any wrapping elements, like <ul> tag. Then we apply the "member" template ... which would output the <li> and member's name.
The reason we only use the member's name (and no other details), is because that's all the underlying membership provider can provide (using "Roles.GetUsersInRole").
Help with GetMembersByGroupName in members XSLT library
Hey all,
I am using the uComponents package, which is fantastic, and I can't find documentation or forum entries to help me list members on the front-end of my website using GetMembersByGroupName.
Can anyone help me use this method? I've had some success using apply-template, but it just spits out a single string of Names and I'd like to have more control over this.
Ideally would like to list entire profiles as stored in the membership directory. Can you help?
Thank you!!
Dave
Have you tryed using the umbraco.library:Split command try split with a ',' or '|'
Hi Dave,
Yeah, the documentation isn't the best - usually my fault, I get carried away developing new extensions - not enought time on documentation! ;-)
OK, example snippets!
Calling the extension directly in an apply-templates, like so...
This would return the following XML nodeset:
The pointer for the nodeset should be set to the root <members> node, so you'd have the following templates in place:
First the "members" template is matched, then inside there we can define any wrapping elements, like <ul> tag. Then we apply the "member" template ... which would output the <li> and member's name.
The reason we only use the member's name (and no other details), is because that's all the underlying membership provider can provide (using "Roles.GetUsersInRole").
Cheers, Lee.
Cheers, Lee.
Thanks Lee!
is working on a reply...