Hello everyone:
I just released my first Expression Engine plugin/extension. It was needed on a recent project to associate entries with member data to create a basic product relationship, but I can definitely see this being useful in other applications (ie. family relationship, Emily Post etiquette seating charts, etc).
I consider this the logical next step beyond LG Member List as it offers more flexibility through the magic of FF Matrix and group_id restrictions.
NG! Member List
NG! Member List is a FieldFrame field type for Expression Engine. It dynamically populates a select with a member list based off your pre-determined configuration.
Download 1.1.2: http://labs.nakedgremlin.com/ee/ng_member_list/
Changelog
1.1.2 (2009-10-09)
Please let me know if you find this useful.
Thanks.
This is pretty awesome, and I can see this becoming very very useful. Is there any plan in the future to make things even more granular? Say, we only need to show 4 names from 1 member group, not all (especially if it’s a giant member group)?
I’d just rather not create several new member groups just to accommodate granularity.
Is there any plan in the future to make things even _more_ granular? Say, we only need to show 4 names from 1 member group, not all (especially if it’s a giant member group)?
That’s an interesting idea. I do fear performance hitches on the admin area for a hyper-large user base (to select the specific members via a multiselect would be an awful experience). I’ll look into it and see if this is a possibility. Thanks for the feedback.
I have installed your fieldtype but instead of the Member Name (“Some Name”) the output is the member_id (“3”). Any ideas? Edit: Just to clarify, the Screen Name appears in the dropdown in the CP, but the member_id appears on the template. Cheers, Cormac
Hi Cormac:
This is the correct behavior.
Like the other FieldFrame fieldtypes, this only saves the identifier for the member (in this case the ‘member_id’). It is up to your front end to determine how that member_id is handled.
For instance, on some of our projects, we pass that info to Solspace’s User module to get the relevant user data.
NG!
ha ha… I found out myself:
here’s a working example: Tag Pair:
{if your_custom_field}
{your_custom_field}
{if {row_count} == 1}<h3>Title</h3><ul>{/if}
<li><a href="#">{your_col_name}</a></li>
{if {row_count} == {total_rows}}</ul>{/if}
{/your_custom_field}
{/if}your_col_name outputs the member_id
Single Tag:
{your_custom_field}outputs a table with col_label as Heading and Member_id’s as table cells
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.