Summary | Alarm warns once then if time is changed then there is no 2nd alarm |
Queue | Kronolith |
Queue Version | 2.3.2 |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | jan (at) horde (dot) org |
Requester | support (at) math (dot) gatech (dot) edu |
Created | 11/18/2009 (5707 days ago) |
Due | 12/02/2009 (5693 days ago) |
Updated | 05/10/2010 (5534 days ago) |
Assigned | 12/15/2009 (5680 days ago) |
Resolved | 05/10/2010 (5534 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Resolved
Re-send mails if alarm has been changed (
Bug #8717).http://git.horde.org/diff.php/framework/Alarm/lib/Horde/Alarm.php?rt=horde-git&r1=75e7b21e9459391e5785427ca2aa24b63ae2e35c&r2=7849bb120a42470f694ad1f7ccd9662ff0357199
http://git.horde.org/diff.php/framework/Alarm/lib/Horde/Alarm/Handler.php?rt=horde-git&r1=75e7b21e9459391e5785427ca2aa24b63ae2e35c&r2=7849bb120a42470f694ad1f7ccd9662ff0357199
http://git.horde.org/diff.php/framework/Alarm/lib/Horde/Alarm/Handler/Mail.php?rt=horde-git&r1=75e7b21e9459391e5785427ca2aa24b63ae2e35c&r2=7849bb120a42470f694ad1f7ccd9662ff0357199
http://git.horde.org/diff.php/framework/Alarm/test/Horde/Alarm/HandlerTest.php?rt=horde-git&r1=3e4a9d6208d5cdec779b80517db1a52d9829a933&r2=7849bb120a42470f694ad1f7ccd9662ff0357199
State ⇒ Assigned
Assigned to Jan Schneider
exact Kronolith version.
The install of Kronolith is via the Horde Groupware Webmail Edition
1.2.4 tarball.
Is there a better way to identify the running version?`
Priority ⇒ 1. Low
State ⇒ Feedback
exact Kronolith version.
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Alarm warns once then if time is changed then there is no 2nd alarm
Due ⇒ 12/02/2009
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
We are working with horde webmail and we have noticed a bug with the
alarm system. If a date and time is set for an event and a reminder is
already sent out and the event date or time is edited then the alarm
for the event will not send another warning. Is there any way to
correct this bug or is this a known issue that is working as intended?