6.0.0-beta1
7/7/25

[#11127] No failure/debug message for .ics import
Summary No failure/debug message for .ics import
Queue Kronolith
Queue Version Git master
Type Enhancement
State Resolved
Priority 1. Low
Owners mrubinsk (at) horde (dot) org
Requester shop (at) open-t (dot) co (dot) uk
Created 04/03/2012 (4843 days ago)
Due
Updated 04/03/2014 (4113 days ago)
Assigned
Resolved 04/03/2014 (4113 days ago)
Milestone
Patch No

History
04/03/2014 05:39:52 PM Michael Rubinsky Assigned to Michael Rubinsky
State ⇒ Resolved
 
04/03/2014 05:39:30 PM Git Commit Comment #4 Reply to this comment
Changes have been made in Git (master):

commit 3d25bfab26f857f0cd44fb9aea29f85374dffcab
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Thu Apr 3 13:35:58 2014 -0400

     Bug: 11127 Gracefully handle errors during ajax calendar import.

  kronolith/data.php |    8 ++++----
  1 files changed, 4 insertions(+), 4 deletions(-)

http://github.com/horde/horde/commit/3d25bfab26f857f0cd44fb9aea29f85374dffcab
04/22/2012 09:05:22 PM shop (at) open-t (dot) co (dot) uk Comment #3 Reply to this comment
There should be some feedback already. Do you get some if you use 
the traditional calendar view?
The traditional view does display the SQL error message at the top - 
the same style as the Turba import procedure errors. However, the 
Dynamic view just pops up the message (instantly, without waiting 
around):

'The calendar "[calendar name]" has been saved'

This is regardless of failure or success (in this case, it actually 
imported 30 out of 4800 events - I shrank the size of one of the 
fields in the back-end on purpose, to make it fail).

No error message or progress report in Dynamic mode. Actually, it has 
a success message every time - which is worse then no message.
04/12/2012 10:00:00 AM Jan Schneider Comment #2
Priority ⇒ 1. Low
State ⇒ Feedback
Reply to this comment
There should be some feedback already. Do you get some if you use the 
traditional calendar view?
04/03/2012 11:44:06 AM shop (at) open-t (dot) co (dot) uk Comment #1
Priority ⇒ 3. High
Type ⇒ Enhancement
Summary ⇒ No failure/debug message for .ics import
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ New
Reply to this comment
If the .ics import fails in Kronolith - there is no message in the 
interface. Turba spits back the SQL error message when importing .csv 
address books - which is useful in troubleshooting what went wrong. In 
Kronolith there is absolutely no indication of failure or success - or 
further details as to where things got jammed. It makes it impossible 
for users with no direct access to the back-end to troubleshoot 
calendar imports in .ics format (and by golly, they do go wrong a lot, 
in every calendar application I tried!)

Note that I've logged a different enhancement request regarding lack 
of progress feedback during import. I consider the two issues 
distinct: progress feedback during the import process and 
failure/success message at the end of the process.

Thank you

Saved Queries