Feature #64372

Epic #77562: Misbehaviors with datetime values and timezones

Add timezone-handling for value-display depending on FE-user

Added by Stefan Neufeind over 6 years ago. Updated over 1 year ago.

Status:
Needs Feedback
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2015-01-20
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

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.

Related issues

Related to TYPO3 Core - Feature #61110: Support for timezones in all date fields in TYPO3 BENew2014-08-21

Actions
Related to TYPO3 Core - Feature #80559: datetime and time handling should always have timezone informationClosed2017-03-29

Actions
#1

Updated by Stefan Neufeind over 6 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.

#2

Updated by Benni Mack over 6 years ago

  • Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
#3

Updated by Susanne Moog about 6 years ago

  • Target version changed from 7.4 (Backend) to 7.5
#4

Updated by Benni Mack almost 6 years ago

  • Target version changed from 7.5 to 8 LTS
#5

Updated by Riccardo De Contardi over 4 years ago

  • Target version changed from 8 LTS to 9.0
#6

Updated by Mona Muzaffar over 4 years ago

  • Related to Epic #80852: Datetime handling in backend added
#7

Updated by Riccardo De Contardi over 4 years ago

  • Parent task set to #77562
#8

Updated by Riccardo De Contardi over 4 years ago

  • Related to deleted (Epic #80852: Datetime handling in backend)
#9

Updated by Susanne Moog over 3 years ago

  • Target version deleted (9.0)
#10

Updated by Susanne Moog over 1 year ago

  • Category set to Frontend
#11

Updated by Benni Mack over 1 year 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....

Also available in: Atom PDF