Hello,

On my DNN 7.02.02 website, I have a custom registration form set up. Upon upgrading to DNN 7.02.02, I noticed that regardless of what new users set as their 'Preferred Time Zone' setting when registering, it would show up as '(UTC - 12:00) International Date Line West' when I looked at it in the 'Users' module.

At first, I thought it it was an issue with the DNN registration form, but today looked at the website's MSSQL database and it turns out that the user's 'Preferred Time Zone' profile setting does appear correctly in the dbo.UserProfile table, so the reigstration module is writing things correctly. However, I noticed that users who registered after the 7.02.02 upgrade have their time zone setting entered under the format of something like '(UTC-09:00) Alaska', while users tho registered before the upgrade have their time zone setting entered under the format of 'Alaskan Standard Time'.

So it appears that with the 7.02.02 upgrade, the registration module changed the format that it is writing to the database, but the 'Users' module was not updated to read both '(UTC-09:00) Alaska' and 'Alaskan Standard Time' format?

Any help would be appreciated.

Thanks,

Phil

Phil,
I just checked with a new DNN install, and PreferredTimeZone in UserProfile does just contain the TZ name without preceding UTC offset, therefore I fear the issue is caused by your registration form not storing the proper value. Compare with TZ being stored when editing a user profile in User Accounts module.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

I took a look at the time zone property on my registration module via the Site Settings > Profile Properties section, and the preferred time zone property was set to a type of 'TimeZoneInfo'. I changed the property type 'TimeZone', and now new user registrations do show the correct time zone.

However, when I changed this type property, all of the old users no longer have their preferred time zone recognized correctly by the Users module.

The TimeZone type property (the one that I updated to) has drop down options with code that looks like this:

<option value="-480">(UTC -08:00) Pacific Time (US & Canada); Tijuanaoption>

So in my database I now have values like '-480' stored in the tables. While the Users module is able to recognize this format when I changed the type, all of the users who registered when I had prior versions of DNN installed have values stored in the database with the format of something like 'Alaskan Standard Time', which is apparently no longer recognized by the Users module when I changed the timezone property.

So now it looks like the Users module is looking for a value that is aligned with the type value I have selected for the preferred time zone, but it's not backwards compatible to recognize both formats?