I created a Date field in a custom content type and set the Time zone handling to "User's time zone" figuring this would convert the entered date/time to the time zone of the viewer based on the time zone of the creator (i.e. if someone in PST creates the node and someone who's in EST views it, they would see the time entered +3 hours). This however is not the case. It seems the time is literal no matter what time zone the viewer is in.

Another odd quirk is when you go to create a new node with this field in it, and you have the default value set to "now" or "relative", the values show up as UTC! I have my time zone properly set to America/Los_Angeles and times all across the site are otherwise ok. It is only when dealing with this Date field that there is a problem.

Is this a bug or am I just wildly misunderstanding how this is supposed to work? I'd be happy to provide any other data you might need to solve this.

Comments

macgirvin’s picture

macgirvin CreditAttribution: macgirvin commented

subscribe

KarenS’s picture

KarenS CreditAttribution: KarenS commented

This needs to be reviewed. I've just committed a number of changes to timezone handling that may affect it, but won't have time to dig into it more until I get the Views filters handling updated, which is a more pressing project.

KarenS’s picture

KarenS CreditAttribution: KarenS commented
Status: Active » Fixed

I think I found the places where this was getting garbled and committed a fix. I've also recently made a ton of other miscellaneous fixes to timezone handling.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.