| Summary | Remote Calendar Repeating Events |
| Queue | Kronolith |
| Queue Version | 2.0.3 |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | Horde Developers (at) |
| Requester | tmpone (at) thehillreaction (dot) org |
| Created | 10/19/2005 (7196 days ago) |
| Due | |
| Updated | 10/10/2006 (6840 days ago) |
| Assigned | 06/17/2006 (6955 days ago) |
| Resolved | 10/10/2006 (6840 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
New Attachment: KronolithBug.ics
Calendar exists again. Only 1 entry, "Test 2". Event is a two day
event for 16/17 June 2006
State ⇒ Feedback
of this calendar to this ticket?
Assigned to
State ⇒ Assigned
Kronolith. We only support recurrence end dates, not number of
recurrences.
should end on the 12th.
ical.mac.com/rchill548/KTest (I don't mean to imply you don't already
know this, I assume you have more practicle experience scheduling
software than I do - I'm just trying to provide complete info) and it
shows the following for event "Test 2":
UNTIL=20051012T035959Z
Since my current timezone is EDT (GMT - 0400), the event should be
repeated until 20051011T235959EDT. The event should end befor 20051012.
When I display the event in Kronolith, it states:
Recur Until 10/12/2005 12:00 am
Which I assume means midnight between 10/11 and 10/12.
It seems that Kronolith is adding 1 second to the UNTIL field when it
translates the iCAL entry, causing it to recur on 10/12, which seems
incorrect.
Furthermore (and I'm in over my head here), RFC 2445 says about the
UNTIL field:
The UNTIL rule part defines a date-time value which bounds the
recurrence rule in an inclusive manner. (I can't understand the intent
of the next sentence, so it may contradict what follows).
Even with the additional 1 second Kronolith seems to add in
translation, I would think the upper bound on this event would still
be 20051012T040000Z or 20051012T000000EDT, so the event shown at
20051012T150000Z is still outside the bounds given and so is incorrect.
If you remain unconvinced, you may mark this bug as closed. I have
nothing further to add.
Rob
State ⇒ Feedback
recurrence should end on the 12th.
Test 1 has a recurring option that is currently not supported at all
by Kronolith. We only support recurrence end dates, not number of
recurrences.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Remote Calendar Repeating Events
Queue ⇒ Kronolith
State ⇒ Unconfirmed
reported in
bug 1582.The difference is that rather than importing the iCal file, I'm
accessing the file as a remote calendar. The ICal file is a product of
tje Mac OS iCal application which is published on .Mac
webcal://ical.mac.com/rchill548/KTest.ics contains exactly two
entries, both in October and each recurring twice.
In Kronolith, event "Test 1" starts on the correct day (10/3) but then
seems to repeat forever. This event was entered as "End After2
Times". Mozilla Sunbird 0.2 handles this entry correctly.
In Kronolith, event "Test 2" starts on the correct day (10/10), but
then repeates three times, although the even should end on date
10/11/05 (the third instance is on 10/12). This event was entered as
"End on Date 10/11/05". Mozilla Sunbird 0.2 also shows an entry on
10/12.
Rob Hill