<?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>Progress feedback  for the ICS import</title> 
  <pubDate>Wed, 08 Apr 2026 08:01:38 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/11126</link> 
  <atom:link rel="self" type="application/rss+xml" title="Progress feedback  for the ICS import" href="https://bugs.horde.org/ticket/11126/rss" /> 
  <description>Progress feedback  for the ICS import</description> 
 
   
   
  <item> 
   <title>The ICS import for Kronolith calendars needs progress feedba</title> 
   <description>The ICS import for Kronolith calendars needs progress feedback for the user to know what is happening. I&#039;ve just finished importing a 4819 entries calendar - which took about 15 minutes. Now this is all fine - but the only way I knew this was the case was by watching the table in the SQL back end. A regular user would have been left staring at an empty calendar, having no idea if the import is happening, is failing etc. They would have most likely restarted the process 5 times over thinking that it isn&#039;t working - and messed up the whole thing.

This could be implemented either:

1. As a generic message - something like &quot;The import process could take a long time, after which the events will show up in the calendar. It is OK to continue using Horde applications in the meanwhile&quot;. This should be easier to implement, but not that useful to the user (however, more useful than nothing).

2. As a progress display in the Kronolith interface - showing how much of the ICS file has already been processed. This could lock the entire interface during the import - or just display in a corner while the interface is still usable.

Either of the above would make the ICS import process a lot more usable to regular, end users, than it is now. At the moment - specially with larger calendar sets - it is close to impossible for users without access to the back-end to make use of it.</description> 
   <pubDate>Mon, 02 Apr 2012 18:32:16 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11126#t71007</link> 
  </item> 
   
  <item> 
   <title>Importing such large calendars is a rare fringe case of powe</title> 
   <description>Importing such large calendars is a rare fringe case of power users.</description> 
   <pubDate>Mon, 02 Apr 2012 21:44:17 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11126#t71017</link> 
  </item> 
   
  <item> 
   <title>Thanks for acknowledging this.

&gt; Importing such large cal</title> 
   <description>Thanks for acknowledging this.

&gt; Importing such large calendars is a rare fringe case of power users.

I don&#039;t know. Few years worth of events easily amount to few thousand entries for anybody. The very fact that the import procedure has absolutely no feedback (be it that it succeeds or fails) is a significant UI problem.
</description> 
   <pubDate>Tue, 03 Apr 2012 11:35:35 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11126#t71045</link> 
  </item> 
   
  <item> 
   <title>I would second this feature request. Importing my 1000 event</title> 
   <description>I would second this feature request. Importing my 1000 events gathered over the last years takes a very long time (why is that?) and a progress bar of some kind would be greatly appreciated.</description> 
   <pubDate>Tue, 20 Aug 2013 13:06:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11126#t80112</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
