[MGNLUI-2694] Dates and times should be displayed in a configured timezone to not confuse user Created: 19/Feb/14 Updated: 22/Feb/17 Resolved: 28/May/16 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 5.4.4 |
| Fix Version/s: | 5.4.7 |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Lipp | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||
| Sprint: | Kromeriz 46 | ||||||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||||||
| Description |
|
Steps to reproduce:
(storage in JCR is fine) A workaround is to add the time diff in hrs between the server and the client timezone to the date/time you're entering. |
| Comments |
| Comment by Mikaël Geljić [ 19/Feb/14 ] |
|
Vaadin DateFieldFactory does assign the current client timezone to the field before setting the value, hence why 8:00 AM is correctly converted into 14:00. |
| Comment by Daniel Lipp [ 19/Feb/14 ] |
|
Greg and me came to the conclusion, that for events it would correct to save the date/time in the timezone of the client creating it. In the context of events we don't want to calculate proper date/time from the client and server timezone when rendering the event but simply show the date/time as entered by the other. E.g. if there's an event today at 2pm at Boston we don't want to display a completely other time just because a visitor might surf the website from somewhere in China. |
| Comment by Roman Kovařík [ 02/May/16 ] |
|
We can already set a timezone on the date field, see:
|
| Comment by Mikaël Geljić [ 03/May/16 ] |
|
First two tickets are old and released, I understand 7450 is still open, but it's only an enhancement for an application-wide (or component-tree-wide) setting. |
| Comment by Roman Kovařík [ 03/May/16 ] |
|
^^ Updated the commend above |
| Comment by Mikaël Geljić [ 03/May/16 ] |
|
Right, the client-side Vaadin widget and connector haven't got any notion of time zone (on its own it's not necessarily a bad thing). Anyway, we cannot display offsets for user input: offsets are sensitive to the chosen date (e.g. depending on DST you might want to format as UTC+1 or UTC+2).
|
| Comment by Mikaël Geljić [ 04/May/16 ] |
|
linking to ticket where timezone awareness in date-field was implemented; |
| Comment by Marvin Kerkhoff [ 19/Oct/16 ] |
|
We / You have a huge bug in Magnolias datefields. If you save a date in the winter period with the time set before 30th of October 2016 it will save all dates -1 hour in the database. More Informations and an example here: |
| Comment by Pierre Sandrin [ 02/Feb/17 ] |
|
Hello Marvin |
| Comment by Marvin Kerkhoff [ 02/Feb/17 ] |
|
Hi Pierre, yes there are several bugs reported in JIRA. https://jira.magnolia-cms.com/browse/MGNLUI-4014 This is the main ticket. We have just updated to 5.5.1 version which should fix the bug. But we are not at the point where i can definetly say that it is fixed. But you can give it a try. Thx |
| Comment by Pierre Sandrin [ 02/Feb/17 ] |
|
Thanks, I will update to 5.5.1 then EDIT: The bug is fixed |