Now I see...

Requiring TimeZone, and requiring a valid profile for registration is where it does't work correctly.

Not requiring TimeZone,  or not requiring a valid profile for registration, captures the correct default from the site settings. [but gives you no overcheck or reminder]

Requiring a valid profile for login [rather than for registration] yields the correct default being stored upon registration but with an opportunity to have a new user then check it on first login... [a crude workaround; note you need some other blank field to be required, too since TimeZone is not blank...]

[I have actually used the above to force users to check their profiles yearly, by simply adding a new checkbox to the profile properties list once each year and then always requiring a valid profile for login ]

If you don't like this don't shoot me...  I'm just a user trying to help a fellow user.

Bob

That's what we where doing and had to switch because we need a custom field populated at the point they register. Additionally interrupting the clients first log in was complicating the process and aggravating them. I may try not requiring TimeZone, but this will no doubt lead to confusion down the road for clients in other timezones. I'd rather it just be fixed as it makes is difficult to pitch a paid version of DNN with these types on bugs.

 

Thanks for you assistance