6.0.0-git
2019-03-23

[#2813] Remote Calendar Repeating Events
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 2005-10-19 (4903 days ago)
Due
Updated 2006-10-10 (4547 days ago)
Assigned 2006-06-17 (4662 days ago)
Resolved 2006-10-10 (4547 days ago)
Milestone
Patch No

History
2006-10-10 16:24:42 Jan Schneider Comment #8
State ⇒ Resolved
Reply to this comment
Fixed with Kronolith 2.1.3.
2006-06-17 09:16:49 Jan Schneider State ⇒ Assigned
 
2006-06-16 21:45:28 Rob (at) thehillreaction (dot) org Comment #7
New Attachment: KronolithBug.ics Download
Reply to this comment
Uploading ICS file per your request
2006-06-16 21:39:23 Rob (at) thehillreaction (dot) org Comment #6 Reply to this comment
Sorry.



Calendar exists again. Only 1 entry, "Test 2". Event is a two day 
event for 16/17 June 2006
2006-06-16 09:15:28 Jan Schneider Comment #5
State ⇒ Feedback
Reply to this comment
The remote calendar doesn't exist anymore, can you upload the ics file 
of this calendar to this ticket?
2005-10-20 07:38:52 Jan Schneider Comment #4
Assigned to Horde DevelopersHorde Developers
State ⇒ Assigned
Reply to this comment
Convinced.
2005-10-20 03:56:31 tmpone (at) thehillreaction (dot) org Comment #3 Reply to this comment
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.
OK
Test 2 is displayed correctly. The iCalendar data says that the recurrence
should end on the 12th.
I disagree. The actual iCal file can be downloaded from the URL 
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
2005-10-19 13:12:01 Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
Test 2 is displayed correctly. The iCalendar data says that the 
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.
2005-10-19 04:05:51 tmpone (at) thehillreaction (dot) org Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ Remote Calendar Repeating Events
Queue ⇒ Kronolith
Reply to this comment
Using Kronolith 2.0.3, I am experiencing an issue similar to that 
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

Saved Queries