Bug #20122
closed
Time will change on 29-03
0%
Description
Time will change on 29-03 from GMT+1 to GMT+2 in Germany.
When I enter a date, for example 15:00 29-03-2009 and leave the field a javascript changes the value to 16:00 29-03-2009.
Entering a time before 2 o'clock will leave the value as is.
Entering a time between 2 o'clock and midnight will change the value.
I guess that this script will prevent the user for entering an invalid time, i.e. there will no 2:30 at 29-03-2009.
But there must be a bug, because after 3 o'clock the time must stay.
I encounter this problem in version 4.1.3, 4.2.4, 4.0.6.
Didn't test it further on other versions
(issue imported from #M10594)
Updated by Chris topher about 15 years ago
Hi Jens,
I do not think that this is in some way connected to the shift to summer-time.
There were several problems with time-zone-shifts in older versions.
Please make an update to 4.2.6 and tell us if the problem still is there.
Updated by Jens Körte about 15 years ago
Hi Christoper,
I made a new installation of version 4.2.6 and the effect won't appear - it is handled in some other way.
When I enter the date 02:00 29-03-2009 in the 4.2.4 version it will change to 03:00 29-03-2009
and when I enter the date in the 4.2.6 version it will change to 01:00 29-03-2009.
So there must be made an update since 4.2.4.
The main thing is, that I can not update every installation I have (there must be more than 50 installations). There are several customers that uses older branches, i.e. 4.0.12 or 4.1.10 and of course 4.2.4 (and some are stuck to 3.8.1). There must be a workaround for this problem.
Do you know how it is done. Yes I know, that this isn't a big thing to tell people to enter dates one hour earlier to get the right result, but I want to present a fine solution for this :-)
Thanks for your help
Updated by Christian Kuhn about 15 years ago
Resolved, no change required.
This problem is solved in recent releases, please upgrade. If you can't upgrade for some reasons and still must solve this problem, you are on your own. You could check the Changelog, identify the fix, port it back to older versions and solve any additional sideeffects that might pop up.
Updated by