<?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>All Day Event Handling from Outlook</title> 
  <pubDate>Thu, 09 Apr 2026 17:52:27 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/4487</link> 
  <atom:link rel="self" type="application/rss+xml" title="All Day Event Handling from Outlook" href="https://bugs.horde.org/ticket/4487/rss" /> 
  <description>All Day Event Handling from Outlook</description> 
 
   
   
  <item> 
   <title>Quoting Muskingum Web Manager:



&gt; Since using Horde, I&#039;ve </title> 
   <description>Quoting Muskingum Web Manager:



&gt; Since using Horde, I&#039;ve grown accustomed to the fact that it 

&gt; recognizes All Day appointments as &quot;Start: Day1 12:00am&quot; to &quot;End: Day2 

&gt; 12:00am&quot; (24 Hour Event). However, Outlook (at least, possibly others) 

&gt; recognizes All Day appointments as &quot;Start: Day1 12:00am&quot; to &quot;End: Day1 

&gt; 12:00am&quot;. Horde, of course, only recognizes this as a 0 hour/0 minute

&gt; appointment.

&gt;

&gt; My question/concern is-- what would be involved with allowing Horde to 

&gt; recognize both formats as &quot;All Day&quot; events? Is this something that 

&gt; should be done to accommodate those of us who frequently rely on both?

&gt;

&gt; Aaron Hall



It makes sense to me to do this just for 12am to 12am events (not 6am to 6am, for example). If that sounds right to you, I say go ahead and create an enhancement ticket for it.



-chuck

----------

Yes, that&#039;s exactly what I had in mind, Chuck.</description> 
   <pubDate>Wed, 04 Oct 2006 19:29:41 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4487#t24596</link> 
  </item> 
   
  <item> 
   <title>Analyzing code, i see that Horde transform explicitly those </title> 
   <description>Analyzing code, i see that Horde transform explicitly those event to 24h event when converting from sif format to vevent :



In /framework/SyncML/SyncML/Device/Sync4j.php: 382, inside sif2vevent function:



  $d = new Horde_Date(array(&#039;year&#039; =&gt; date(&#039;Y&#039;, $t),

  &#039;month&#039; =&gt; date(&#039;m&#039;, $t),

  &#039;mday&#039; =&gt; date(&#039;d&#039;, $t) + 1));



I think that horde should undo that transform when converting vevent to sif. I attach a patch to do it:



It solves the problem, but i don&#039;t know if it has collateral effects.</description> 
   <pubDate>Mon, 02 Mar 2009 12:31:57 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4487#t52816</link> 
  </item> 
   
  <item> 
   <title>Seems like bug #6847 is a duplicate of this. Can you please </title> 
   <description>Seems like bug #6847 is a duplicate of this. Can you please try if the solution I committed there works for you?</description> 
   <pubDate>Tue, 07 Apr 2009 11:19:28 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4487#t53574</link> 
  </item> 
   
  <item> 
   <title>Reposting, because email notifications didn&#039;t work:

&gt; Seems</title> 
   <description>Reposting, because email notifications didn&#039;t work:

&gt; Seems like bug #6847 is a duplicate of this. Can you please try if 

&gt; the solution I committed there works for you?

</description> 
   <pubDate>Thu, 16 Apr 2009 22:34:24 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4487#t53723</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
