I created a new profile property using a TrueFalse data type.
I add the profile field to my registration form template (it is listed in the list of available profile fields from the link from register form tokens ).
However, the profile field is displayed as a text box.

Any ideas?
I even tried changing the profile field to a CheckBox data type. (just in case)

We have added the ability to handle this in our latest release. This was because DNN 4x did not allow this data type and we have not noticed it creep into DNN 5x as something we did not support. This has been fixed.

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

RESULTS OF TEST 1

Using CheckBox as the data type displays

Check boxes on Standard DNN

Text boxes on Advanced Login

Next, I modified the data type of Newsletter to TrueFalse

I then checked the Standard DNN and Advanced Login page

RESULTS OF TEST 2

Changing Newsletter to TrueFalse as the data type displays

True and false on Standard DNN

Check box on Advanced Login

And lastly, I modified the data type of AcceptTerms to TrueFalse

I then checked the Standard DNN and Advanced Login page

RESULTS OF TEST 3

Changing AcceptTerms to TrueFalse as the data type displays

True and false on Standard DNN
Which shouldn't be used

Unable to view Advanced Login (Page Error)

QUESTIONS:

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...

Doing a quick check using Firefox with Firebug
I found this code when I clicked in the dropdown list for Region:
Please note that it's using HTTP and if the page is using HTTPS, then that could be the problem.

We did notice that you have some strange code appear "window.location.replace" that is referenced in your post, but is not in our code. So we are guessing that you have got some page blaster, or SEO module or something going on that is intercepting code before it hits the page and is causing your issue with the HTTPS feature. My guess is that you turn that off and your problem will be solved.

Regards the logic of the check box item. We have implemented the standard Microsoft ASP.Net controls in this module. Microsoft dictates that a check box item cannot be made mandatory. Their logic no doubt is that that how can your give someone a choice but require them to only make a certain choice.

That being said, I know what you are trying to achieve, and that is that someone has agreed to your terms and conditions.

It would be possible to do this by making the item as non mandatory in DNN (thus getting it to display) then using some custom script in the template of the module to ensure that it is ticked in the signup process. The script you use would be simple jquery or js.