Date Field: Timezone differs between admin panel input, and rest response

quornik

last year

1 5

• Selected Answer
  

  DanRibbens

  Payload Team

  last year

  Since we deterimined there isn't anything in Payload to fix I'm moving this to a discussion for others to see.

• 

  DanRibbens

  Payload Team

  last year

  Thanks for reporting this @quornik. We're considering what the configuration settings will be for timezone and what effects it will have for the admin UI and APIs to solve the issue. We'll update again when we have a plan or fix ready.

• 

  quornik

  last year

  Thanks @DanRibbens.
  You should also consider if I haven't rushed to quickly to call it a bug. Maybe it works properly and what it actually needs is just slightly updated documentation to the field. A warning of some kind that one should always localize the response.

  If you think about it, the best practice is to adjust the timezone always on frontend, after the dateObject has been received and befere it is displayed, because the user's context should determine the way date is interpreted & displayed.

  The scenario in which I had a problem with the way it works now, was this particular situation that I did not localize the response date before displaying. In every other situation it works fine.

• 

  jmikrut

  Payload Team

  last year

  If you think about it, the best practice is to adjust the timezone always on frontend, after the dateObject has been received and befere it is displayed, because the user's context should determine the way date is interpreted & displayed.

  Exactly, @quornik. This isn't really a bug per se, rather, it's a potentially useful admin UX enhancement.

  We're thinking through how to make this happen as Dan said and will report back here once we have more!

• 

  lucaslcode

  9 months ago

  Here's a use case that doesn't fit the current setup too well - I'm adding events using payload, however the events I'm adding take place in a different timezone to where I am currently.

  It seems payload converts my local time to UTC and stores that - it means I have to do some calculating to input the time I want as it would be in my current timezone.

  I think a possible solution would be to have the ability to select the timezone of the time you are entering, though I'm not sure if react-datepicker supports this.