<?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>Search error for &#039;All Past&#039; and &#039;All Future&#039;</title> 
  <pubDate>Fri, 10 Apr 2026 19:28:25 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/2257</link> 
  <atom:link rel="self" type="application/rss+xml" title="Search error for &#039;All Past&#039; and &#039;All Future&#039;" href="https://bugs.horde.org/ticket/2257/rss" /> 
  <description>Search error for &#039;All Past&#039; and &#039;All Future&#039;</description> 
 
   
   
  <item> 
   <title>When performing a search in kronolith, and using the time fr</title> 
   <description>When performing a search in kronolith, and using the time frames all past or all future, I get the following error:

Fatal error: Call to a member function on a non-object in /usr/share/horde3/kronolith/lib/Driver.php on line 98 (or 97)



Through var_dump()&#039;ing $query, I found that it&#039;s because $query-&gt;start or $query-&gt;end is set to null.  In HEAD, this happend on lines 74-79 of search.php.  It seems that you either need to set the values for -&gt;start and -&gt;end to real, though almost infinite times, or build logic into lib/Driver.php to deal with the case that one of them is null.



I&#039;d be willing to patch this, but I&#039;m not sure on which way to go.



Thanks,



Chris Sacca</description> 
   <pubDate>Tue, 12 Jul 2005 18:59:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2257#t9697</link> 
  </item> 
   
  <item> 
   <title>A patch would be great. I&#039;d put in logic to handle the NULL </title> 
   <description>A patch would be great. I&#039;d put in logic to handle the NULL values, personally.</description> 
   <pubDate>Tue, 12 Jul 2005 19:09:02 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2257#t9700</link> 
  </item> 
   
  <item> 
   <title>Ok, hacked something up against 2.0.3, but from what I&#039;ve lo</title> 
   <description>Ok, hacked something up against 2.0.3, but from what I&#039;ve looked at of head it should apply there too.  Wasn&#039;t acutally as bad as I though it was going to be first.  I did some testing on my changes (basic event, recuring event, all day event) and they were good, but a second check is always useful.</description> 
   <pubDate>Tue, 12 Jul 2005 19:43:02 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2257#t9702</link> 
  </item> 
   
  <item> 
   <title>Committed, thanks!</title> 
   <description>Committed, thanks!</description> 
   <pubDate>Tue, 12 Jul 2005 20:28:52 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2257#t9706</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
