Timezone error after upgrade to 2.0

[emrahtokalak]

Describe the bug

After upgrading my 1.8.3 project to 2.0, I am getting an error that I think is caused by the "OrchardCore.Users.TimeZone" module. Each user's setting is "local time zone" and the application's global time zone setting is "GMT+3".

These settings, which worked fine in 1.8.3, are causing me to get errors on the content items page and at many points where the "GetLocalTimeZoneAsync" method is called.

Orchard Core version

2.0

To Reproduce

Steps to reproduce the behavior:

• Upgrade your project from 1.8.3 to 2.0.

• Set your users in your project to the default timezone option.

• Activate the "OrchardCore.Users.TimeZone" module.

• You will see that many mechanisms, especially content items, do not work correctly.

Expected behavior

A clear and concise description of what you expected to happen.

Logs and screenshots

While timezone is active, I cannot call a SQL query with the "api/queries" endpoint, it throws an error caused by timezone.

[Piedone]

I can see the issue. It's because we get an NRE here:

This is only when the user's time zone is set as "Use site's time zone":

[Piedone]

This is a regression, so we need to fix it for 2.1.0 at least, perhaps also release it as a 2.1.1.

[github-actions]

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

[Piedone]

This isn't just for an ugpraded site, BTW, even a vanilla 2.0 site has this issue.

BTW a workaround you can use for now is to either set the time zone of the affected users to something else than the site's, or to disable OrchardCore.Users.TimeZone altogether for now.

[emrahtokalak]

This isn't just for an ugpraded site, BTW, even a vanilla 2.0 site has this issue.

BTW a workaround you can use for now is to either set the time zone of the affected users to something else than the site's, or to disable OrchardCore.Users.TimeZone altogether for now.

Yes, I later realized that there was a problem with the vanilla installation too.

[MikeAlhayek]

I think @Piedone meant to fix this and release 2.0.1 not 2.1.1.

[Piedone]

Yep!