Now all that we need is a preference to set whether to use a comma or a pipe character as the delimiterThat one is a candidate for a hack on the part of the user 😊
Yep, I think I can take care of that one. I’m not that bad at PHP.
I can’t wait for the sneak preview of 2.0 at SXSW. OK, off to install and try this out.
I’m sure that unless everyone who enters the preview event has to sign an NDA, there will be plenty of twittering going on as things are announced or revealed.
By the way, after installing Member List 1.2, I did have to uninstall/install but it seems to be working exactly as I need - which was to have a simple list of member ID’s associated with a post. Seemed easy enough, anyway!
Other than the fact that there must be an extension conflict in my installation, because my other field types go dead when this is installed, so I can’t create any new custom fields with Member List installed - it’s working fine!
I’m wondering, if it’s not too much of a pain for me to uninstall, make my new field(s), then re-install - does it keep the previous info I’ve entered or eliminate it? I’d hate to have a bunch of selections made, uninstall and lose them.
For the record, these are the extensions installed currently. I’m willing to bet one of them doesn’t have a last call in there or something along those lines (Wow, I didn’t realize I had such a list on this one):
ext.add_sitename.php (Me) ext.checkbox.php (Mark Huot) ext.cloner.php (1st party) ext.disable_news_feed.php ext.edit_remember.php (Mark Huot) ext.edit_tab_ajax.php (1st party) ext.empty_options.php (Mark Huot) ext.ez_category_checkboxes.php (Cocoaholic) ext.favorites_ext.php (Solspace) ext.fresh_variables.php (1st party) ext.geo.php (Mark Huot) ext.hidden_weblogs.php (Mark Huot) ext.lg_member_list.php ext.livesearch.php (Mark Huot) ext.mh_file_ext.php (Mark Huot) ext.multi_text.php (Mark Huot) ext.selected_items.php (Andrew Weaver) ext.simplify_edit_table.php ext.textile_editor.php (Lavalamp)
Is the easiest thing to do when troubleshooting these to look for those extensions that use the same hooks - in this case the same hooks that Member List is using?
Hey Ryan,
LG Member List uses the following hooks:
‘publish_admin_edit_field_extra_row ‘publish_form_field_unique’ ‘show_full_control_panel_end’ ‘submit_new_entry_start’
The only hook which doesn’t check $EXT for previous data is http://expressionengine.com/developers/extension_hooks/submit_new_entry_start/ which is cool because it returns no data in the first place.
I would start by disabling extensions that aren’t written by Mark or are first party… and go from there.
I would start by disabling extensions that aren’t written by Mark or are first party… and go from there.
Hmm, not trying to be rude or anything… but I would start by disabling extensions that are written by Mark. Especially older versions of “livesearch” and the “file” extension. Make sure your extensions are up to date!
Anyway, just my 2 cents :red:
If I’m not mistaken, I think this extension disables the other field types when creating a new custom field. I installed it this morning, and went to create some custom fields. When I tried selecting any of the fields (notably ‘File’ - which is Mark Huot’s extension) - none of the options popped up for it. Same with any of the other field types.
I have the same problem. It looks like a javascript issue. When I disable LG Member list everything works fine.
The work-around is to select the new custom field type from the drop-down, hit save, then re-edit the custom field and the appropriate details for that field type now show up.
I have these extensions in-common with Ryan:
ext.checkbox.php (Mark Huot) ext.geo.php (Mark Huot) ext.lg_member_list.php ext.multi_text.php (Mark Huot)
ExpressionEngine 1.6.0 Build: 20070815
Hey Sue,
There is no template tag to do that automatically at the moment. It could be achieved using a custom query to loop over the members and add them as select options.
The option value is the member_id and the text displayed is their name.
Should be pretty easy to knock up.
Update: Try
SELECT member_id as q_member_id, screen_name as q_screen_name FROM exp_members WHERE group_id = 1
Cheers
Hi all,
I am using this fantastic extension, but found one thing slightly frustrating…having to use a database call to access the user details.
I originally tried using “custom_profile_data” tag within my “weblog:entries” tag, but this doesn’t seem to work (clearly “artwork_member_id” is the custom weblog field generated by the LG Member List):
{exp:weblog:entries weblog="artwork" dynamic="off"}
{exp:member:custom_profile_data member_id="{artwork_member_id}"}{screen_name}{/exp:member:custom_profile_data}
{/exp:weblog:entries}
So I didn’t have to keep writing queries in my templates, I have created a little plugin that grabs a specified field from the exp_members table. Note that this doesn’t work with custom member fields as yet.
I have attached the zip for the plugin to this post. All you have to do is stick the plugin into the “system/plugins” directory and use it as follows:
{exp:weblog:entries weblog="artwork" dynamic="off"}
{exp:member_details return="screen_name" member_id="{artwork_member_id}"}{/exp:member_details}
{/exp:weblog:entries}
As this is the very very very first plugin that I have created for EE, you will have to forgive me for any issues with the plugin. Really this is a “use at your own risk” plugin.
I would love for all the expert users out there to let me know if this a) could be done another way that is already built in to EE; or b) there are ways to enhance the plugin; or c) if this plugin is useful in anyway!
Enjoy.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.