Tickets :: [#4025] CSV import fails on Outlook 2003 data with empty description

6.0.0-RC7

6/27/26

History
Attachments
Comment
Watch
Download

Summary	CSV import fails on Outlook 2003 data with empty description
Queue	Horde Framework Packages
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	2. Medium
Owners	jan (at) horde (dot) org
Requester	okuhl (at) netcologne (dot) de
Created	6/12/06 (7320 days ago)
Due
Updated	12/4/07 (6780 days ago)
Assigned	9/20/06 (7220 days ago)
Resolved	12/4/07 (6780 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

4211	Jan Schneider	Comment #8 Assigned to Jan Schneider Taken from Horde Developers State ⇒ Resolved	Reply to this comment
Fixed in CVS and Horde 3.2.

386	Chuck Hagenbuch	Deleted Original Message

306	Chuck Hagenbuch	Deleted Original Message

226	Chuck Hagenbuch	Assigned to Horde Developers

66	Chuck Hagenbuch	Comment #7 Version ⇒ HEAD Queue ⇒ Horde Framework Packages State ⇒ Assigned	Reply to this comment
This is a framework bug.

346	Chuck Hagenbuch	Comment #6 State ⇒ Summary ⇒ CSV import fails on Outlook 2003 data with empty description	Reply to this comment
I've added a partial test for this to the Data package, where the issue seems to be. I can now reproduce that one of the files contains one record, while the other shows as having zero rows. I haven't gotten farther than that, though.

482	okuhl (at) netcologne (dot) de	Comment #5	Reply to this comment
Did you try both .csv files I attached? The first one should create an error. By removing the line break, it should work. I don't know why the second one works. But there has to be something with the parser. Can anyone confirm this behavior?

342	Chuck Hagenbuch	Comment #4	Reply to this comment
Now I'm confused - do you mean that this ticket can be closed?

311	okuhl (at) netcologne (dot) de	Comment #3 New Attachment: Outlook2003WindowsErrorTest.CSV	Reply to this comment
Maybe the same problem like in ~~bug 3839~~? I'm a bit confused. Inspired by your comment I created a new test which includes a "working" record and a "should-not-work" record. But everything worked. Even the record which was ment to break everything - it's the same as in the last example I uploaded - works now. So this seems to be a more complex problem and maybe it is linked to ~~#3389~~.

1612	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
Maybe the same problem like in ~~bug 3839~~?

287	okuhl (at) netcologne (dot) de	Comment #1 Priority ⇒ 2. Medium State ⇒ Unconfirmed New Attachment: Outlook2003WindowsError.CSV Queue ⇒ Kronolith Summary ⇒ CSV import defekt with Outlook 2003 and empty description Type ⇒ Bug	Reply to this comment
Outlook 2003 (tested with german edition) exports an empty description field as a single newline in quotes, which kronolith does not like. Import works when the newline was removed manually. Attached is an example .csv with one record that produces the error.