<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Funambol to Kronolith, recur_enddate timezone issue</title> 
  <pubDate>Fri, 10 Apr 2026 05:02:48 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/5250</link> 
  <atom:link rel="self" type="application/rss+xml" title="Funambol to Kronolith, recur_enddate timezone issue" href="https://bugs.horde.org/ticket/5250/rss" /> 
  <description>Funambol to Kronolith, recur_enddate timezone issue</description> 
 
   
   
  <item> 
   <title>When synchronizing a recurring item with an end (either date</title> 
   <description>When synchronizing a recurring item with an end (either date or count) from a windows mobile PDA with the funambol 3.x plugin to kronolith, the last appointment in kronolith is one before the last appointment on the PDA. 



The funambol plugin converts the enddate on the PDA to Universal Time (for both end date and recur count), and the date gets stored unmodified in the kronolith database. Because of DST, I&#039;m now two hours ahead of DST, which means the enddate is set to two hours before midnight on the endday, so the day before. This causes the recurrence to end prematurely.



The attached patch converts the PatternEndDate to a timestamp using mktime, then adds the difference from UTC using date(&#039;Z&#039;);



I&#039;ve so far only noticed this issue with the Funambol plugin. I&#039;ve asked a colleague of mine to test this using a Nokia device, to see if the problem is with the import of the vcard (can&#039;t imagine so), and not funambol&#039;s implementation.



In the mean time, I&#039;ve attached the patch for review. Please comment if this isn&#039;t the right way to fix this, so I can learn how to do it correctly within the Horde framework.</description> 
   <pubDate>Thu, 12 Apr 2007 14:15:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5250#t31480</link> 
  </item> 
   
  <item> 
   <title>I can&#039;t reproduce anymore, because Funambol sends both the n</title> 
   <description>I can&#039;t reproduce anymore, because Funambol sends both the number of occurrences (calculated from the recurrence end) and the recurrence end date. Since number of occurrences has precedence now in the Horde code, such events are converted now to recurrence rules like: RRULE:FREQ=WEEKLY;COUNT=10;INTERVAL=1;BYDAY=WE



Beside that, the date stamp sent by the client is a perfectly valid ISO date time string. If it&#039;s not correctly translated to the local timezone, this has to be fixed either in the iCalendar library or in Kronolith, but definitely not in the Sync4j device handler.



Can you please try if you still see this with the latest code from CVS or the next RCs?</description> 
   <pubDate>Wed, 09 Apr 2008 15:13:44 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5250#t44524</link> 
  </item> 
   
  <item> 
   <title>A colleague of mine is in the process of re-testing recurren</title> 
   <description>A colleague of mine is in the process of re-testing recurrence with the latest version of Kronolith and the Funambol Outlook client, I&#039;ll update when he has some results.</description> 
   <pubDate>Thu, 10 Apr 2008 10:20:58 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5250#t44559</link> 
  </item> 
   
  <item> 
   <title>Ping again?</title> 
   <description>Ping again?</description> 
   <pubDate>Wed, 23 Apr 2008 21:59:09 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5250#t44832</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
