I see this issue often and I assume (but don't know - I haven't gone so far as to inspect the code) that this is caused by saving values in UTC - but forgetting to convert them to local time on the display end. There are many ways to handle internationalization, but the standard approach I've always seen is: Store everything in UTC (i.e., in the database). Then transform it on the display end according to the user's locale. But this approach (if that is indeed what they're doing) often leads to these kinda little bugs where someone wrote some code that just grabs the raw date value and doesn't bother to localize it.
Of course, maybe something entirely different is going on... ¯_(ツ)_/¯
We're a place where coders share, stay up-to-date and grow their careers.
I see this issue often and I assume (but don't know - I haven't gone so far as to inspect the code) that this is caused by saving values in UTC - but forgetting to convert them to local time on the display end. There are many ways to handle internationalization, but the standard approach I've always seen is: Store everything in UTC (i.e., in the database). Then transform it on the display end according to the user's locale. But this approach (if that is indeed what they're doing) often leads to these kinda little bugs where someone wrote some code that just grabs the raw date value and doesn't bother to localize it.
Of course, maybe something entirely different is going on... ¯_(ツ)_/¯