- Affected version
- 2.3.13
BC, Alberta, the NWT and Manitoba stopped observing DST on 2026-11-01 (tzdata 2026b–2026e).
Steps to reproduce
Actual: UTC-8. The same applies to Alberta on Mountain (
Notes
Suggested fix
Add
Workaround for now: Arizona, Saskatchewan and Bogota give the correct offsets.
Related: XenForo timezone data is out of date, Certain timezone returning error
XF\Data\TimeZone has no entry that follows any of them, so users there are an hour out on the zone they'd normally pick.America/Vancouver: UTC-7 year-round (2026b)America/Edmonton,America/Inuvik: UTC-6 (2026c, 2026d)America/Winnipeg: UTC-5, followed by northwestern Ontario (2026e)America/Whitehorse: UTC-7 since 2020, also missing
Steps to reproduce
- Account > Preferences > Time zone.
- Select (UTC-08:00) Pacific Time (US & Canada), i.e.
America/Los_Angeles.
Actual: UTC-8. The same applies to Alberta on Mountain (
America/Denver) and Manitoba on Central (America/Chicago).Notes
- The same list backs the admin user editor,
guestTimeZoneand user criteria. XF.AutoTimeZonekeys on the current year's Jan/Jun offsets, so 2026 registrations from these regions get Los_Angeles/Denver/Chicago. From 2027 they resolve to Phoenix/Belize/Bogota, which have the right offsets but the wrong labels.- The new zones only resolve correctly with tzdata 2026e or later. PHP 8.3.30's bundled 2025.2 still returns -08:00 for
America/Vancouver. - Unchanged in 2.3.13:
TimeZone.phpandlogin_signup.jsare identical to 2.3.10.
Suggested fix
Add
America/Vancouver, America/Edmonton and America/Winnipeg with their own phrases. The "(US & Canada)" labels on Pacific, Mountain and Central no longer hold for these regions.Workaround for now: Arizona, Saskatchewan and Bogota give the correct offsets.
Related: XenForo timezone data is out of date, Certain timezone returning error