beardcoder - I Have a Problem with the datetime...
# ❓questionsb
beardcoder
05/19/2023, 6:33 PMI Have a Problem with the datetime picker 😦
beardcoder
05/19/2023, 6:34 PMI can not set the correct date time zone in the frontend. the backend handles the timezone correct
beardcoder
05/19/2023, 6:41 PMCurrently the only way is this code
$item->number_assignment_date->shiftTimezone('UTC')->setTimezone('Europe/Berlin')beardcoder
05/19/2023, 6:42 PMwithout shiftTimezone('UTC') nothing will happend
i
ifox
05/19/2023, 8:20 PMhi @beardcoder did you change the default Laravel timezone (UTC)?
ifox
05/19/2023, 8:20 PMasking because as a good practice you probably shouldn't so that you store timezone agnostic dates in database, which is what Twill is doing
ifox
05/19/2023, 8:21 PMso even if you changed your default timezone, Twill still stores dates using UTC (and renders in the user timezone in the CMS)
ifox
05/19/2023, 8:22 PMso it makes sense that you have to indicate to carbon that the date you're trying to render is not on UTC
b
beardcoder
05/20/2023, 5:35 PMYes I have changed the timezone to Europe/Berlin. And the behavior from Twill looks correct to store the dates in UTC. But I don’t find any solution to say carbon the timezone from the database.
beardcoder
05/20/2023, 5:36 PMHave you any solution to set the timezone from the database or transform this with a cast?
i
ifox
05/20/2023, 5:59 PMthe problem is that a cast will affect twill too. the recommendation is to keep utc as your Laravel timezone so that it doesn't think dates in your database are stored using a different timezone (which is why you have to shift it right now). The fact that you want to show a date in a specific timezone is a concern of your application and should be dealt with at render time, not in the database.