6.0.0-beta1
7/4/25

[#11663] Time zone not detected correctly
Summary Time zone not detected correctly
Queue Horde Groupware
Queue Version 5.0.0
Type Bug
State Not A Bug
Priority 2. Medium
Owners
Requester horde (at) luetgens (dot) org
Created 11/07/2012 (4622 days ago)
Due
Updated 11/07/2012 (4622 days ago)
Assigned 11/07/2012 (4622 days ago)
Resolved 11/07/2012 (4622 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
11/07/2012 12:55:11 PM Jan Schneider Comment #8
State ⇒ Not A Bug
Reply to this comment
Well ...

- user prefs: works, but is obviously not automatically detected
There isn't anything to detect. Either it's set or not. If not, is 
uses the default which is determined by the following rules.
- date.timezone php.ini setting: see my previous comment. Is there 
any other relevant timezone info in php?
No. If that doesn't work, you need to track down why. The timezone is 
set in Horde/Registry.php.

[Show Quoted Text - 9 lines]
11/07/2012 12:14:32 PM horde (at) luetgens (dot) org Comment #7 Reply to this comment
Well ...

- user prefs: works, but is obviously not automatically detected

- date.timezone php.ini setting: see my previous comment. Is there any 
other relevant timezone info in php?

- TZ environment variable: according to docs, no TZ variable in 
Ubuntu. cat /etc/timezone reads Europe/Berlin.

- UTC: I would like to avoid that. :-)

I can live with manually setting the time zone in preferences, but it 
still seems like a bug to me that I have to do that.

If there is anything I can do to help, please do not hesitate to ask.
11/07/2012 12:02:18 PM Jan Schneider Comment #6 Reply to this comment
Where does horde get its "Default" time zone from?
In descending precedence:
- user prefs
- date.timezone php.ini setting
- TZ environment variable
- UTC
11/07/2012 11:53:38 AM horde (at) luetgens (dot) org Comment #5 Reply to this comment
I did not change any configuration at all during the upgrade. "UTC" is active.

As far as I understand it, if I had changed this option, the problem 
would be permanent. But if I set the time zone to Europe/Berlin 
manually, everything works just fine. I did not upgrade from 3.x to 
5.x, but from 4.x to 5.x.

Besides, devices synchronizing via SyncML or ActiveSync are not 
affected: The time is still correct everywhere but in horde. If I set 
Europe/Berlin manually, it is correct in horde as well.

Where does horde get its "Default" time zone from?
11/07/2012 11:42:38 AM Jan Schneider Comment #4
State ⇒ Feedback
Reply to this comment
Works just fine here. Did you change the UTC flag in the 
Kronolithconfiguration during the upgrade?
11/07/2012 08:06:17 AM horde (at) luetgens (dot) org Comment #3 Reply to this comment
phpinfo() says:
Default timezone         Europe/Berlin

I haven't changed this in a very long time, if ever. The problem did 
not occur with previous horde versions on the same apache/php basis.
11/07/2012 07:54:00 AM arjen+horde (at) de-korte (dot) org Comment #2 Reply to this comment
Events in Kronolith are one hour off after upgrading from horde 4 to 
horde 5. When the current time zone is changed manually from 
"Default" to "Europe/Berlin", the information is displayed correctly.
Could it be that your timezone in 'php.ini' is set to some other value 
than 'Europe/Berlin'?
11/07/2012 07:51:10 AM horde (at) luetgens (dot) org Comment #1
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Groupware
Summary ⇒ Time zone not detected correctly
Type ⇒ Bug
Reply to this comment
Events in Kronolith are one hour off after upgrading from horde 4 to 
horde 5. When the current time zone is changed manually from "Default" 
to "Europe/Berlin", the information is displayed correctly.

Saved Queries