Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Website time zone setting for Canada - Whitehorse and Canada - Dawson does not observe now-permanent UTC-7 #16657

Closed
ygdaverogers opened this issue Nov 2, 2020 · 4 comments · Fixed by #16660
Assignees
Labels
answered For when a question was asked and we referred to forum or answered it. not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.

Comments

@ygdaverogers
Copy link

As of March 8, 2020, the Yukon Territory of Canada no longer changes its clocks to observe different standard or daylight saving times. That means Yukon is now permanently UTC-7 (the same as MST at the moment). See https://yukon.ca/time for details.

The "Canada - Whitehorse" and "Canada - Dawson" time zone regions are both in Yukon and should observe that change.

Please note that "Canada - Dawson Creek" is not in Yukon and not part of this time zone change.

Our Matomo installation insists that Canada - Whitehorse is on Pacific Standard Time (UTC-8) even though the underlying OS has the update for the new Yukon Standard Time and is configured as "America/Whitehorse". This means that web hits are tagged one hour behind the time in Yukon.

The workaround for now is to use the Phoenix, Arizona time zone setting as most of Arizona observes year-round UTC-7.

The same adoption of year-round daylight saving time is expected for British Columbia, Washington, Oregon, and hopefully California before long.

Please update the time zone policy for "Canada - Whitehorse" and "Canada - Dawson" to be permanently set to UTC-7.

Thanks from Canada's North!

@tsteur
Copy link
Member

tsteur commented Nov 2, 2020

Thanks for creating this issue @ygdaverogers

This might be an issue with PHP @sgiehl @Findus23 ?

@sgiehl
Copy link
Member

sgiehl commented Nov 3, 2020

The timezones in PHP can be updated with the pecl package timezonedb. If that one isn't installed or updated PHP will use the timezones shipped with the PHP version. Depending on how old the PHP version is, the timezones might not be up to date.
Guess that is the reason why PHP marked a lot timezones as "do not use". See https://www.php.net/manual/en/timezones.others.php

We actually could add a diagnostic check to check the version of timezonedb installed. That can be achieved with timezone_version_get(). On some systems that might return 0.system if the one shipped with PHP is used. Latest version would be 2020.04. See https://pecl.php.net/package/timezonedb

@ygdaverogers
Copy link
Author

Thanks very much for that. I'll have our infrastructure folks work on the PHP setup. "Sorry"--said the Canadian--for taking your time on a PHP issue.

@tsteur tsteur added answered For when a question was asked and we referred to forum or answered it. not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. labels Nov 3, 2020
@tsteur tsteur self-assigned this Nov 3, 2020
tsteur added a commit that referenced this issue Nov 3, 2020
fix #16657

Information may be useful when troubleshooting some issues. Only needed though when Matomo is installed
@tsteur
Copy link
Member

tsteur commented Nov 3, 2020

@sgiehl added #16660 so we have it in the system check. We can then close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered For when a question was asked and we referred to forum or answered it. not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants