<?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>php errors on kronolith &quot;startup&quot;</title> 
  <pubDate>Fri, 10 Apr 2026 19:28:27 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/11396</link> 
  <atom:link rel="self" type="application/rss+xml" title="php errors on kronolith &quot;startup&quot;" href="https://bugs.horde.org/ticket/11396/rss" /> 
  <description>php errors on kronolith &quot;startup&quot;</description> 
 
   
   
  <item> 
   <title>Hi,

when entering the new kronolith, I get these errors i</title> 
   <description>Hi,

when entering the new kronolith, I get these errors in the horde log:

2012-09-01T17:33:51+02:00 NOTICE: HORDE [kronolith] PHP ERROR: Undefined index: display_calendars [pid 18081 on line 211 of &quot;/datastore/DEVEL/horde/kronolith/lib/Application.php&quot;]
2012-09-01T17:33:51+02:00 WARN: HORDE [kronolith] PHP ERROR: Invalid argument supplied for foreach() [pid 18081 on line 104 of &quot;/datastore/DEVEL/horde/kronolith/lib/Kronolith.php&quot;]

Backend is configured to &quot;SQL&quot; to make sure it&#039;s not something caused by the Kolab driver.

Thomas
</description> 
   <pubDate>Sat, 01 Sep 2012 15:34:59 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11396#t72710</link> 
  </item> 
   
  <item> 
   <title>But I must admit the new kronolith looks nice :)
</title> 
   <description>But I must admit the new kronolith looks nice :)
</description> 
   <pubDate>Sat, 01 Sep 2012 15:36:17 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11396#t72711</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git (master):

commit 830c6af0d976</title> 
   <description>Changes have been made in Git (master):

commit 830c6af0d976d5d41f7f1f6fcc3ee4612472c538
Author: Jan Schneider &lt;jan@horde.org&gt;
Date:   Mon Sep 3 14:54:26 2012 +0200

    Drop alarms in menu.
    
    We have consistent alarm notifications across all applications now, and this
    requires the complete application to be initialized before the topbar is even
    rendered, which want to avoid with deferred application initialization.
    Fixes bug #11396.

 horde/config/registry.php     |   18 ------------
 kronolith/lib/Application.php |   56 --------------------------------------
 nag/lib/Application.php       |   60 -----------------------------------------
 3 files changed, 0 insertions(+), 134 deletions(-)

http://git.horde.org/horde-git/-/commit/830c6af0d976d5d41f7f1f6fcc3ee4612472c538</description> 
   <pubDate>Mon, 03 Sep 2012 12:57:25 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11396#t72755</link> 
  </item> 
   
  <item> 
   <title>Fix is working fine, thanks.
</title> 
   <description>Fix is working fine, thanks.
</description> 
   <pubDate>Wed, 05 Sep 2012 08:11:53 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11396#t72770</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git (develop):

commit 830c6af0d97</title> 
   <description>Changes have been made in Git (develop):

commit 830c6af0d976d5d41f7f1f6fcc3ee4612472c538
Author: Jan Schneider &lt;jan@horde.org&gt;
Date:   Mon Sep 3 14:54:26 2012 +0200

    Drop alarms in menu.
    
    We have consistent alarm notifications across all applications now, and this
    requires the complete application to be initialized before the topbar is even
    rendered, which want to avoid with deferred application initialization.
    Fixes bug #11396.

 horde/config/registry.php     |   18 ------------
 kronolith/lib/Application.php |   56 --------------------------------------
 nag/lib/Application.php       |   60 -----------------------------------------
 3 files changed, 0 insertions(+), 134 deletions(-)

http://git.horde.org/horde-git/-/commit/830c6af0d976d5d41f7f1f6fcc3ee4612472c538</description> 
   <pubDate>Mon, 15 Oct 2012 20:37:07 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11396#t73487</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
