6.0.0-beta1
9/1/25

[#8797] Incoming alarm-less events from syncML get standard reminder
Summary Incoming alarm-less events from syncML get standard reminder
Queue Kronolith
Queue Version FRAMEWORK_3
Type Bug
State No Feedback
Priority 2. Medium
Owners
Requester mephisto (at) gmx (dot) net
Created 12/23/2009 (5731 days ago)
Due
Updated 03/17/2010 (5647 days ago)
Assigned 01/26/2010 (5697 days ago)
Resolved 03/17/2010 (5647 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
03/17/2010 03:40:47 PM Jan Schneider State ⇒ No Feedback
 
01/27/2010 07:55:51 PM mephisto (at) gmx (dot) net Comment #3 Reply to this comment
Are you really using a FRAMEWORK_3 checkout? Sounds like a duplicate 
of bug #8588.
Indeed, sounds like a duplicate. I will re-check with a recent cvs 
checkout soon and report the results here.
01/26/2010 10:46:54 PM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
Are you really using a FRAMEWORK_3 checkout? Sounds like a duplicate 
of bug #8588.
12/23/2009 01:15:01 PM mephisto (at) gmx (dot) net Comment #1
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Incoming alarm-less events from syncML get standard reminder
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
When using the syncML interface with a standard reminder set in 
kronolith, events that were created on the syncML client without alarm 
get the standard reminder set when they are synchronized to kronolith.
I assume that this is due to the constructor
function Kronolith_EVent(&$driver, $eventObject = null) in 
kronolith/lib/Driver.php setting the default alarm regardless of what 
the constructed event is going to be used for.

The bug can be worked around by simply disabling the standard reminder 
in kronolith.

Saved Queries