6.0.0-beta1
7/29/25

[#5236] Recurring events missing RRULE field
Summary Recurring events missing RRULE field
Queue Kronolith
Queue Version HEAD
Type Bug
State Resolved
Priority 2. Medium
Owners chuck (at) horde (dot) org
Requester horde (at) eltofts (dot) homelinux (dot) com
Created 04/10/2007 (6685 days ago)
Due
Updated 04/12/2007 (6683 days ago)
Assigned 04/11/2007 (6684 days ago)
Resolved 04/12/2007 (6683 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
04/12/2007 02:57:34 PM Chuck Hagenbuch Comment #4
Assigned to Chuck Hagenbuch
Taken from Karsten Fourmont
State ⇒ Resolved
Reply to this comment
The fix is committed now - thanks!
04/12/2007 11:24:20 AM horde (at) eltofts (dot) homelinux (dot) com Comment #3 Reply to this comment

[Show Quoted Text - 26 lines]
I have added the missing "," and this has sorted it... thanks :)


04/12/2007 11:12:09 AM jochem (at) mondrian (dot) nl Comment #2
New Attachment: sql.php.patch Download
Reply to this comment
I did some more research, it seems that the kronolith_event_sql object 
used in _kronolith_export in kronolith/lib/api.php is broken. I've 
modified that file to write the print_r($event, true) value to a file.



When I create an event with or without an enddate, and synchronize it 
to my pda, and examine the contents of $event, it contains no 
recurrence information.



When I create an event with an recurcount, it creates an event with 
'recurtype' set to the number of recurrences (12 in this case):

[recurCount] =>

[recurType] => 12

[recurInterval] => 1



When doing something similar in kronolith/lib/Driver/sql.php's 
getByUID function, I noticed that the data being pulled from the db 
had the same discrepancies. Upon closer inspection, there was a , 
missing from the query after event_recurcount, on line 395. Because 
event_recurtype is the next in the list, mysql assumed the query meant 
'event_recurcount AS event_recurtype', messing up the data.



Fixing this fixed the problem.



I've attached a patch, and I'll be submitting another ticket and patch 
for a seperate problem with recurrence in the SyncML module.
04/11/2007 09:17:27 AM Jan Schneider Assigned to Karsten Fourmont
State ⇒ Assigned
 
04/10/2007 10:49:42 PM horde (at) eltofts (dot) homelinux (dot) com Comment #1
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Recurring events missing RRULE field
Queue ⇒ Kronolith
State ⇒ Unconfirmed
Reply to this comment
Syncing a calendar with recurring entries fails. Each entry only has 
its initial date - no recurrences.



This is an example of an entry that recurs every day.



contents of /tmp/horde.log for SyncML sync;



output received from horde backend (text/x-vcalendar):

BEGIN:VCALENDAR

VERSION:1.0

X-WR-CALNAME:Andy Wright's Calendar

PRODID:-//The Horde Project//Horde_iCalendar Library//EN

METHOD:PUBLISH

BEGIN:VEVENT

DTSTART:20070403T050000Z

DTEND:20070403T060000Z

DTSTAMP:20070402T154830Z

UID:20070402163907.5qf60gruy44c@192.168.1.1

DCREATED:20070402T153907Z

LAST-MODIFIED:20070402T153907Z

SUMMARY:Test title

TRANSP:OPAQUE

ORGANIZER;CN=Andy Wright:mailto:andywright

LOCATION:Test location

CLASS:PUBLIC

STATUS:CONFIRMED

END:VEVENT

END:VCALENDAR



and the same calendar entry exported as iCal;



BEGIN:VCALENDAR

VERSION:2.0

X-WR-CALNAME:Andy Wright's Calendar

PRODID:-//The Horde Project//Horde_iCalendar Library//EN

METHOD:PUBLISH

BEGIN:VEVENT

DTSTART:20070403T050000Z

DTEND:20070403T060000Z

DTSTAMP:20070402T160248Z

UID:20070402163907.5qf60gruy44c@192.168.1.1

CREATED:20070402T153907Z

LAST-MODIFIED:20070402T153907Z

SUMMARY:Test title

TRANSP:OPAQUE

ORGANIZER;CN=Andy Wright:mailto:andywright

LOCATION:Test location

CLASS:PUBLIC

STATUS:CONFIRMED

RRULE:FREQ=DAILY;INTERVAL=1

END:VEVENT

END:VCALENDAR





RRULE:FREQ=DAILY;INTERVAL=1 only appears on the iCalendar export.

Saved Queries