We have moved to GitHub Issues
You are viewing the read-only archive of Umbraco's issue tracker. To create new issues, please head over to GitHub Issues.
Make sure to read the blog posts announcing the move for more information.
Created by Shannon Deminick 29 Oct 2013, 04:06:19 Updated by Shannon Deminick 05 Nov 2013, 02:27:44
Relates to: U4-3264
I've updated the picker to get the search to work now and use the same data structures as the other pickers (i.e. an Entity). However, the picker by default is configured to be a multi-picker but there's no UI indication on what has been picked and there is not button to submit the picked members. I haven't tested it when it's a single only picker.
Set memberpicker to default to a single item picker, as this is really what it should support by default. But what kind of data should it store? id or the member key?
Should store the member key so that it might be possible for it to work with a non-umbraco membership provider
So how do I get these and entities from their guid? - would I have to switch to the member api to do that?
I've checked and in v6 we store the value as integer id (and the property editor needs to be configured to store as INT in the db to be backwards compat)
this means it would never support a diff membership provider but that's how it is currently. Lets leave it like that and eventually can create another member picker that stores the GUID.
And in order to be backwards compat, we can only store one value as an INT so we cannot enable a multi-select. Again if we want that we can make a newer member picker later on. I've updated the property editor to store an "INT" in the db, didn't have time to look at the JS changes needed.
This is all fixed now and backwards compatible. If we want to support a member picker with other membership providers we'll have to create another version.
Assignee: Shannon Deminick
Backwards Compatible: True
Due in version: 7.0.0