Following this as i actually have a use case for needing dropdowns.

I was thinking of just making the front end with my own HMTL and copying the values into the Umbraco Fields (That would be hidden)

Thanks @Elitenet

Hopefully it is something that gets some attention by HQ.

Going to go with the mixed aproach passing stuff around with jQuery and taking care of validation etc then giving the end result over to Umbraco to save.

I've also noticed the the sort order of the member properties are not the order in which they are rendered.

https://our.umbraco.org/forum/umbraco-7/using-umbraco-7/59996-Member-Profile-Page

In the end of this post, theres a guy who have hi-jacked the snippet and hardcoded the "registerModelMemberProperties5__Value" with some select boxes. You could maybe see if it's something for you. :-|

I have noticed that you can still change the rendered fields as per below.

@Html.EditorFor(m => registerModel.MemberProperties[i].Value, new { htmlAttributes = new { @class = "form-check-input", @type = "checkbox" } })

@Html.EditorFor(m => registerModel.MemberProperties[i].Value, new { htmlAttributes = new { @class = "form-control", @type = "date" } })

And I have tested that having a Member field set to "date" dataType will save correctly if the Html.EditorFor field is set to "date".

And to render things out in the order I wanted;

@for (var i = 0; i < propertiesCount; i++)
{
   if (@registerModel.MemberProperties[i].Alias == "testDate")
   {
       // Do some stuff
   }
 }

That way you can at least split out fields into different sections or do pretty much what you want.

Okay, thats great news, its very helpful. Great work.

Have you tried to make a checkbox with ie "Opt-in to Newsletter". I get an error with "Cant Cast Boolean to String", because it seems that the checkbox returns boolean, and the member property is written as a string. Maybe you can get it to work? Only if you have time to test.

Cheers Peter

Hi Amanda, you dont have to test, I have tested it. The checkbox doesnt save the value.

Also something funny, I found this in the controller:

 //TODO: Perhaps one day we'll ship with our own EditorTempates but for now developers 
// can just render their own.

So its something which was actually planned at some point.

I have create an issue, now please vote it up.

http://issues.umbraco.org/issue/U4-11357

Up voted!

In the mean time to get around the checkbox issue for my consent checkbox I have done the following.

        // Consent
        $("#consentCheckBox").on('change', function () {
            var consentReceived = "true";
                consentDeclined = "false";

            if ($(this).is(':checked')) {
                $(".form-section-hide").show();
                $('.field-consent-checkbox').val(consentReceived);
                alert($('.field-consent-checkbox').val())
            }
            else {
                $(".form-section-hide").hide();
                $('.field-consent-checkbox').val(consentDeclined);
                alert($('.field-consent-checkbox').val())
            }
        });

And for the MVC Form fields I have left them as textboxes in the front end and in Umbraco. (Please note that I am using bootstrap material design checkboxes hence some of the markup).

                    if (@registerModel.MemberProperties[i].Alias == "consent")
                    {
                        <div class="col-md-6 push-top">
                            <div class="form-check @registerModel.MemberProperties[i].Alias">
                                <div>
                                    <strong>@Html.LabelFor(m => registerModel.MemberProperties[i].Value, registerModel.MemberProperties[i].Name, new { @class = "bmd-label-static" }):</strong><br />
                                    <i>
                                        I consent to my data being collected so as to display my results in a graphacal format.<br />
                                        I understand that all of my data will be treated and secured as "sensitive"data.<br />
                                        No data will be shared with 3rd parties.<br />
                                        If data is later considered to be of benefit for future use to help the Trans* community, further consent will be sought.
                                    </i>
                                </div>
                                <label class="form-check-label">
                                    <input id="consentCheckBox" class="form-check-input" type="checkbox" value="" required data-validation-required-message="Consent is required to continue.">                                        
                                    <span class="form-check-sign">
                                        <span class="check"></span>
                                    </span>
                                </label>
                                <div class="hidden-field">
                                    @Html.EditorFor(m => registerModel.MemberProperties[i].Value, new { htmlAttributes = new { @class = "form-control field-consent-checkbox" } })
                                    @Html.HiddenFor(m => registerModel.MemberProperties[i].Alias)
                                </div>

                            </div>
                        </div>
                    }

It isn't a perfect solution but at least it's a property that can be easily checked / tested against.

For my consent box i actually have it hide all other data fileds I have for registration and also the submit button unless it is checked. But the "false" value is still there to be added in as a fallback incase something goes weird with the JavaScript or someone does something dodgy.

Great work. Now I will dive into making a custom controller and models for my project.

On another sidenote, but still related to Members. It would be great if we could:

• Export Member DocTypes
• Render Member Properties in the order they are sorted in their DocType (easily!),
• Use "Nested Content" for a Member (Haven't tried this to see if it might work... but I have doubts that it does)
• Export All Members from the Backoffice (Not just one at a time)

Actually the MemberService does expose a lot of this.

                @{
                    var svc = ApplicationContext.Services.MemberService;
                    var member = svc.GetById(currentMember.Id);
                    foreach (var prop in member.Properties)
                    {
                        <p>Alias: @prop.Alias</p>
                        <p>Property Type: @prop.PropertyType.Name</p>
                        <p>Value: @prop.Value</p>
                        <p>Description: @prop.PropertyType.Description</p>
                        <hr />
                    }
                }

is working on a reply...