Tickets :: [#487] Alarms don't get triggered after start date changed

6.0.0-beta1

9/19/25

Summary	Alarms don't get triggered after start date changed
Queue	Kronolith
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	1. Low
Owners	Horde Developers (at)
Requester	thomas (at) creativebusinessystems (dot) com
Created	08/16/2004 (7704 days ago)
Due
Updated	11/24/2004 (7604 days ago)
Assigned	08/23/2004 (7697 days ago)
Resolved	11/24/2004 (7604 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

11/24/2004 12:36:19 AM	Jan Schneider	Comment #5 State ⇒ Resolved	Reply to this comment
Fixed in CVS.

11/24/2004 12:01:30 AM	Jan Schneider	Summary ⇒ Alarms don't get triggered after start date changed

11/20/2004 02:16:16 AM	Chuck Hagenbuch	Comment #4	Reply to this comment
Sort of. You don't want to trigger an alarm twice for an event that's just after midnight, for example. But something along those lines sounds like the right way to go. If you meant the event start date and the alarm interval (instead of the alarm date), then yes, that sounds like it'd work.

11/20/2004 01:12:59 AM	Jan Schneider	Comment #3	Reply to this comment
Would it be enough to tackle the alarm date and interval to $seenid?

08/23/2004 05:14:26 PM	Jan Schneider	Comment #2 Assigned to Horde Developers State ⇒ Assigned	Reply to this comment
This happens only if the alarm for that event already occured because the id we store for seen alarms only consists of the day the alarm was triggered and the event id. The scheduler doesn't know if the event's start time or alarm interval has changed.

08/16/2004 03:04:23 PM	thomas (at) creativebusinessystems (dot) com	Comment #1 State ⇒ Unconfirmed Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Alarms Queue ⇒ Kronolith	Reply to this comment
If I edit an event's start time and simply save the event, I do not get an e-mail reminder. However, if I save the event as new, I will receive an e-mail reminder.