6.0.0-alpha14
7/1/25

[#8355] non-standardconform iCal-File
Summary non-standardconform iCal-File
Queue Kronolith
Queue Version 2.3.1
Type Bug
State Duplicate
Priority 2. Medium
Owners
Requester michael.groene (at) zew (dot) uni-hannover (dot) de
Created 06/17/2009 (5858 days ago)
Due
Updated 06/17/2009 (5858 days ago)
Assigned
Resolved 06/17/2009 (5858 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
06/17/2009 08:19:07 PM Jan Schneider Comment #3
State ⇒ Duplicate
Reply to this comment
Duplicate of bug #7846.
06/17/2009 03:54:45 PM michael (dot) groene (at) zew (dot) uni-hannover (dot) de Comment #2 Reply to this comment
Has somebody a solution for this bogus behavior?
Which files/functions are affected?
I have found the file, creating the iCal recurrence rule in

HORDE_BASE/kronolith/lib/Recurrence.php (Horde Groupware Edition 1.2.3)



ca. in line 1061 the function toRRule20(...) is defined.

I changed the code to the following, which works fine for me:

function toRRule20($calendar)

{

...

   if ($this->hasRecurEnd()) {

      #$rrule .= ';UNTIL=' . $calendar->_exportDate($this->recurEnd);   
   #doesn't sync correctly with lightning 0.9

      $rrule .= ';UNTIL=' . $calendar->_exportDateTime($this->recurEnd); #works

   }

...

}



But the origin of the time is a mysterium to me. Maybe someone really 
knows how to solve this problem completely in a neat way.


06/17/2009 02:17:09 PM michael (dot) groene (at) zew (dot) uni-hannover (dot) de Comment #1
Priority ⇒ 2. Medium
New Attachment: example.ics Download
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ non-standardconform iCal-File
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
An example .ics-file is attached. When syncing this file, generated by 
Horde Groupware Edition 1.2.3, to lightning, the event is repeated 4 
times, not the expected 5 times.



This is due to an non-standardconform iCal-File, as we discussed a bit 
earlier in the bugtracker of lightning:

https://bugzilla.mozilla.org/show_bug.cgi?id=498621



Has somebody a solution for this bogus behavior?

Which files/functions are affected?

Saved Queries