Skip to content

[6.x] Avoid localizing time fields in modifiers#13795

Closed
duncanmcclean wants to merge 2 commits into6.xfrom
time-field-localization
Closed

[6.x] Avoid localizing time fields in modifiers#13795
duncanmcclean wants to merge 2 commits into6.xfrom
time-field-localization

Conversation

@duncanmcclean
Copy link
Member

We started localizing dates passed to modifiers in #11409 as part of wider timezone improvements.

It's great for Date fields, where the date is stored in UTC, but should be displayed in a different timezone, like America/New_York.

However, it doesn't work for Time fields, which are stored as simple strings and don't need to be converted. This PR ensures they don't get converted.

Fixes #13766

@duncanmcclean duncanmcclean marked this pull request as draft February 2, 2026 18:11
@jasonvarga
Copy link
Member

I don't really want to start augmenting it to a new thing. I feel like that'll cause even more headaches elsewhere.

I'll put some more thoughts in the issue itself.

@jasonvarga jasonvarga closed this Feb 2, 2026
@jasonvarga jasonvarga deleted the time-field-localization branch February 14, 2026 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Time fieldtype gets wrong timezone in template

2 participants