6.0.0-beta1
12/21/25

[#3839] Import of CSV fails
Summary Import of CSV fails
Queue Horde Framework Packages
Queue Version HEAD
Type Bug
State Resolved
Priority 1. Low
Owners jan (at) horde (dot) org
Requester medwards1 (at) onehealth (dot) ca
Created 04/26/2006 (7179 days ago)
Due
Updated 12/04/2007 (6592 days ago)
Assigned 04/28/2006 (7177 days ago)
Resolved 12/04/2007 (6592 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
12/04/2007 10:32:18 PM Jan Schneider Comment #6
Assigned to Jan Schneider
Taken from Horde DevelopersHorde Developers
State ⇒ Resolved
Reply to this comment
This CSV file parses fine now. The fix will appear in Horde 3.2.
06/16/2006 09:35:30 AM Jan Schneider Comment #5
Version ⇒ HEAD
Queue ⇒ Horde Framework Packages
Reply to this comment
Moved to Horde_Data for now.
05/24/2006 09:43:46 PM Chuck Hagenbuch Comment #4
Taken from Chuck Hagenbuch
Reply to this comment
I've added the start of a test case for this to CVS in the Data 
package; looks like File_CSV simply chokes on the .csv provided. Once 
we get that working in the Data package hopefully Kronolith will just 
be fine.
05/22/2006 07:37:40 AM Jan Schneider Comment #3 Reply to this comment
I don't have this fixed yet, but related: since we provide our own
File_CSV class now, is there any reason to keep the code in
Horde_Data that checks for whether File_CSV is available?
No.
05/22/2006 04:21:54 AM Chuck Hagenbuch Comment #2 Reply to this comment
I don't have this fixed yet, but related: since we provide our own 
File_CSV class now, is there any reason to keep the code in Horde_Data 
that checks for whether File_CSV is available?
05/18/2006 08:53:55 PM Chuck Hagenbuch Assigned to Chuck Hagenbuch
 
04/28/2006 05:48:08 PM Jan Schneider Assigned to Horde DevelopersHorde Developers
State ⇒ Assigned
 
04/26/2006 03:30:50 PM medwards1 (at) onehealth (dot) ca Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Import of CSV fails
Queue ⇒ Kronolith
New Attachment: cleaned2.csv Download
State ⇒ Unconfirmed
Reply to this comment
Importing this CSV file results in a truncated description. If there 
are events that follow after the problem event, then those events are 
not imported at all. Appears to be related to double-quoted entries 
appearing before a newline.



Please see attached CSV file, delimiter: ~ quote: " fields: 12

Saved Queries