It appears the only difference between our fields is that you use a TrueFalse data type, while I use a CheckBox.
So I decided to do a structured test and compare the Standard DNN Registration page with the Advanced Login page.
In our first set of tests, I decided to leave both fields as CheckBox.
I then checked the Standard DNN and Advanced Login page
Using CheckBox as the data type displays
Next, I modified the data type of Newsletter to TrueFalse
Changing Newsletter to TrueFalse as the data type displays
And lastly, I modified the data type of AcceptTerms to TrueFalse
Changing AcceptTerms to TrueFalse as the data type displays
1. Why does Advanced Login not display the correct element on the form?
I'm not a developer, but if you select a CheckBox as data type, shouldn't it also display a check box on the page?
So something seems wrong there
Using CheckBox displays a text box on your page
Using TrueFalse displays a check box on your page
2. Why does securing the AdvancedLogin Registration page (with HTTPS) disables the Region dropdown list?
That one seems very strange to me...
I just installed the module and it kinda works...
If you do not make the custom profile field mandatory (by either using DNN-Manage Profile Properties or by using your |required=true in the form) then it will display the checkbox properly.
When I do this
It breaks the Advanced Login registration page.
I have also checked this with the Newsletter custom field.
...and it appears that if you make any custom field mandatory, it breaks the Advance Login registration page.
1. Did you get a chance to read my previous post to a potential solution regarding the problem with Region dropdown list and securing using HTTPS?
It appears that you are using an Absolute URL, perhaps using a Relative URL might fix the problem.