<?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>External events like birthdays don&#039;t stick</title> 
  <pubDate>Sun, 05 Apr 2026 07:58:29 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7779</link> 
  <atom:link rel="self" type="application/rss+xml" title="External events like birthdays don&#039;t stick" href="https://bugs.horde.org/ticket/7779/rss" /> 
  <description>External events like birthdays don&#039;t stick</description> 
 
   
   
  <item> 
   <title>When choosing to display external events, like birthdays, in</title> 
   <description>When choosing to display external events, like birthdays, in Kronolith, the events don&#039;t stick. That is, there is no way to save that preference, and the next time you view the Calendar, the events are gone and must be re-populated by the user.</description> 
   <pubDate>Mon, 15 Dec 2008 10:54:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7779#t51266</link> 
  </item> 
   
  <item> 
   <title>Did you update config/prefs.php?</title> 
   <description>Did you update config/prefs.php?</description> 
   <pubDate>Mon, 15 Dec 2008 14:15:55 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7779#t51268</link> 
  </item> 
   
  <item> 
   <title>&gt; Did you update config/prefs.php?



I looked in kronolith/</title> 
   <description>&gt; Did you update config/prefs.php?



I looked in kronolith/config/prefs.php, but I do not think there is any object responsible for persisting the choice to show birthdays, etc. on the Calendar. I believe this should be present in the Kronolith options UI.</description> 
   <pubDate>Mon, 15 Dec 2008 14:35:07 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7779#t51269</link> 
  </item> 
   
  <item> 
   <title>&gt; I looked in kronolith/config/prefs.php, but I do not think</title> 
   <description>&gt; I looked in kronolith/config/prefs.php, but I do not think there is 

&gt; any object responsible for persisting the choice to show birthdays, 

&gt; etc. on the Calendar.



The external calendars preference. If it&#039;s not in config/prefs.php, then that&#039;s your problem. You need to follow the upgrade instructions.</description> 
   <pubDate>Mon, 15 Dec 2008 15:07:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7779#t51270</link> 
  </item> 
   
  <item> 
   <title>I appreciate that you are trying to point me in the right di</title> 
   <description>I appreciate that you are trying to point me in the right direction.  However, could you please tell me where to find the &quot;external calendars preference&quot;? And which &quot;upgrade instructions?&quot; What does this have to do which upgrading?



I contribute significant amounts of my time and energy to other open source projects, and the main concern is always USABILITY. Simply saying &#039;if not [...], &quot;then that&#039;s your problem&quot;&#039; doesn&#039;t improve the quality of Horde.



&gt;&gt; I looked in kronolith/config/prefs.php, but I do not think there is

&gt;&gt; any object responsible for persisting the choice to show birthdays,

&gt;&gt; etc. on the Calendar.

&gt;

&gt; The external calendars preference. If it&#039;s not in config/prefs.php, 

&gt; then that&#039;s your problem. You need to follow the upgrade instructions.

</description> 
   <pubDate>Mon, 15 Dec 2008 15:32:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7779#t51271</link> 
  </item> 
   
  <item> 
   <title>This is the preference that holds external calendars:



// </title> 
   <description>This is the preference that holds external calendars:



// store the external calendars to display

$_prefs[&#039;display_external_cals&#039;] = array(

    &#039;value&#039; =&gt; &#039;a:0:{}&#039;,

    &#039;locked&#039; =&gt; false,

    &#039;shared&#039; =&gt; false,

    &#039;type&#039; =&gt; &#039;implicit&#039;

);



It does not and should not show up in the UI (thus the implicit type; types are documented in horde/config/prefs.php.dist) because it saves the state of the panel checkboxes, nothing more.



The relationship to upgrading is that if you upgraded and didn&#039;t update prefs.php from prefs.php.dist, you won&#039;t have this preference and it won&#039;t be saved to the db. From horde/docs/UPGRADING:



&quot;After updating to a newer Horde version, or a newer version of **any** Horde

application, you **always** need to update **all** configuration files.&quot;</description> 
   <pubDate>Mon, 15 Dec 2008 15:47:21 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7779#t51272</link> 
  </item> 
   
  <item> 
   <title>Thank you for this clear reply--I appreciate your time. I wa</title> 
   <description>Thank you for this clear reply--I appreciate your time. I was also having related issues with error messages described in http://bugs.horde.org/ticket/7439.



&gt; This is the preference that holds external calendars:

&gt;

&gt; // store the external calendars to display

&gt; $_prefs[&#039;display_external_cals&#039;] = array(

&gt;     &#039;value&#039; =&gt; &#039;a:0:{}&#039;,

&gt;     &#039;locked&#039; =&gt; false,

&gt;     &#039;shared&#039; =&gt; false,

&gt;     &#039;type&#039; =&gt; &#039;implicit&#039;

&gt; );

&gt;

&gt; It does not and should not show up in the UI (thus the implicit type; 

&gt; types are documented in horde/config/prefs.php.dist) because it saves 

&gt; the state of the panel checkboxes, nothing more.

&gt;

&gt; The relationship to upgrading is that if you upgraded and didn&#039;t 

&gt; update prefs.php from prefs.php.dist, you won&#039;t have this preference 

&gt; and it won&#039;t be saved to the db. From horde/docs/UPGRADING:

&gt;

&gt; &quot;After updating to a newer Horde version, or a newer version of **any** Horde

&gt; application, you **always** need to update **all** configuration files.&quot;

</description> 
   <pubDate>Mon, 15 Dec 2008 16:11:00 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7779#t51273</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
