Summary | reminders too later |
Queue | Kronolith |
Queue Version | 2.0.1 |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | Horde Developers (at) |
Requester | daniel.eckl (at) gmx (dot) de |
Created | 02/11/2005 (7446 days ago) |
Due | |
Updated | 08/12/2005 (7264 days ago) |
Assigned | 04/10/2005 (7388 days ago) |
Resolved | 04/10/2005 (7388 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
I have a 12:00pm meeting scheduled evryday for two weeks, every day I
get an email reminding me about the event on the first day of the
event happening.
I think we need to tweak the calculation of the event date somehow. I
will also open up a new bug concerning recurring events and
continuous notification.
Summary ⇒ reminders too later
State ⇒ Resolved
think... I've removed it for now.
State ⇒ Assigned
in the first place?
this bug.
I see you already committed the fix to CVS, but for the sake of
completeness, I'll just add that I had to remove $today from the
$seenid because if $today was kept in the id then the reminder would
be sent every day leading up to the event instead of just once at the
given alarm setting.
State ⇒ Resolved
State ⇒ Feedback
New Attachment: sql_alarm.patch
alarms are sent at the right time instead of waiting until the day of
the event.
Basically they don't come until the day of the event, even if, for
example, you set the alarm for 24 or 48 hours prior to the event.
I'm currently testing a patch that sends the reminders at the right
time. It seems to work, but I've only patched
kronolith/lib/Driver/sql.php since that's the backend I use. If the
patch indeed works as expected then perhaps I'll take a look at the
other drivers to see if I can patch those as well. I'll attach my
patch once I verify it, but if someone's dying for the patch in the
meantime I can send what I have so far.
State ⇒ Assigned
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ reminders too late
Queue ⇒ Kronolith
State ⇒ Unconfirmed
event, it will come at beginning of the event.
So let's say you have an event on 15th Feb 2005 and set the alarm to 1 day
before event, then you will get the email on 15th Feb 2005 00:00 AM which is
indeed the exact start time of the event, not one minute before.