problem with all day events imported from outlook

RESOLVED FIXED

Status

RESOLVED FIXED
13 years ago
13 years ago

People

(Reporter: qx1nq3a02, Assigned: jminta)

Tracking

Details

Attachments

(2 attachments)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3
Build Identifier: Lightning version 0.1 (build 2006031011)

all day events imported from outlook become regular events that start at 0:00.
when you make then all day events they become all day events that span two days.

Reproducible: Always

Steps to Reproduce:
1. in outlook, create an all day event
2. export that day to a csv file
3. in lightning, import that csv file
4. open the event, check "all day", close

Actual Results:  
after step 3, the event appears to be a regular (non-allday) event with start time of 12am (appears in calendar as 0:00), and end time 12am the next day

after step 4, the event is an allday event and appears to span two days

Expected Results:  
after step 3, the event should be an all day event for the correct day only.
(Assignee)

Comment 1

13 years ago
Can you attach a sample testcase of an outlook exported all-day event?  Thanks.
(Reporter)

Comment 2

13 years ago
Created attachment 221371 [details]
exported outlook calendar

here is the csv file I used. there are two events on may 18, 2006.  "one" should be an all day event.
(Assignee)

Comment 3

13 years ago
Created attachment 221373 [details] [diff] [review]
use .valueTrue

localeEn.True is undefined, it should be localeEn.valueTrue.  The testcase passes for me with this patch.
Assignee: nobody → jminta
Status: UNCONFIRMED → ASSIGNED
Attachment #221373 - Flags: first-review?(mvl)
Comment on attachment 221373 [details] [diff] [review]
use .valueTrue

the localeEn should be locale, otherwise importing outlook files from other languages won't work.
r=mvl with that fixed.
Attachment #221373 - Flags: first-review?(mvl) → first-review+
(Assignee)

Comment 5

13 years ago
patch checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.