| Summary | Event alarms ignore user's "Local and Time" option |
| Queue | Kronolith |
| Queue Version | 2.0.1 |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | Horde Developers (at) |
| Requester | clawrence (at) optimiser (dot) com |
| Created | 01/06/2005 (7490 days ago) |
| Due | |
| Updated | 03/06/2005 (7431 days ago) |
| Assigned | 02/23/2005 (7442 days ago) |
| Resolved | 03/06/2005 (7431 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
State ⇒ Feedback
debugging on your own.
To answer your questions, yes the server has the timezone trying to
switch to, yes php has the ability to change TZ and yes we are still
experiencing the problem.
The server is set to run in TZ="GMT" by default, with most users
setting their timezone to Australia/Perth
State ⇒ Not A Bug
State ⇒ Feedback
time shift. Maybe the timezone you specified doesn't exist on your
server, or the webserver/php is not allowed to change the TZ
environment variable?
State ⇒
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Event alarms ignore user's "Local and Time" option
Queue ⇒ Kronolith
State ⇒ Unconfirmed
- The server on which Horde is running has its timezone in GMT.
- The user's current time zone as set in Horde's "Local and Time"
options is set to anything but GMT.
- Create a new event on the calendar and set an alarm. (eg: An event
which begins at 18:00 with an alarm 1 hour before the start of the
event, relative to the user's current time zone, say Australia/Perth.)
- Using the above example, expect the alarm to occur at 17:00
(Australia/Perth time). Observe, email reminder is generated at 17:00
GMT (01:00 Australia/Perth time).