Feature #64372
closed
Epic #77562: Misbehaviors with datetime values and timezones
Add timezone-handling for value-display depending on FE-user
0%
Description
For a website with users from the other side of the world it would be great to be able to use full timezone-handling depending on the FE-user. We might imho either decide to add a new field to the FE-user that, if set, overrides the timezone of the server or provide such functionality through TypoScript so developers can switch timezones themselves.
- Things like visibility-settings of course must not be influenced by this, only display of date/time-values.
- Also take date/time-display in Fluid into account.
- Maybe even consider something similar for BE-users.
Updated by Stefan Neufeind over 9 years ago
Internally (and in the DB) we should handle times cleanly in UTC anyway, see for example also #61110.
So imho this one here has the same/a similar target.
Updated by Benni Mack almost 9 years ago
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Riccardo De Contardi about 7 years ago
- Target version changed from 8 LTS to 9.0
Updated by Mona Muzaffar about 7 years ago
- Related to Epic #80852: Datetime handling in backend added
Updated by Riccardo De Contardi almost 7 years ago
- Related to deleted (Epic #80852: Datetime handling in backend)
Updated by Benni Mack about 4 years ago
- Status changed from New to Needs Feedback
FYI - this would mean that we cannot have group-based caching at all anymore, and all code considered is USER_INT. Does not sounds too valuable to me in this case... Other sites have added logic that does the "2 minutes ago" via JavaScript. So Timezone handling in Frontend could follow a similar pattern....
Updated by Christian Kuhn over 2 years ago
- Status changed from Needs Feedback to Closed
Closing due to lack of feedback. Please re-open if the issue persists with action points we should take to get this done.