Closed
Bug 397936
Opened 18 years ago
Closed 18 years ago
Import of duplicate items from an .ics file fails to take LAST-MODIFIED into account.
Categories
(Calendar :: Import and Export, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 325449
People
(Reporter: vcssupport1, Unassigned)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7
Build Identifier: Thunderbird version 2.0.0.7pre (20070926) / Lightning version 0.7pre (2007092803)
The ics import code only appears to take the UID of an event into account when importing items. If the LAST-MODIFIED line exists in the importing event and is more recent than the LAST-MODIFIED line in the existing event, then the software should at least offer the option to update the event to the more recent version.
Reproducible: Always
Steps to Reproduce:
1.Set up a new test calendar.
2.Import the following event:
BEGIN:VEVENT
CREATED:20070928T184453Z
LAST-MODIFIED:20070928T184500Z
DTSTAMP:20070928T184522Z
UID:e4aec1d1-5975-4783-a269-e7fae63f4532
SUMMARY:Test Event
DTSTART:20070928T190000Z
DTEND:20070928T200000Z
END:VEVENT
3.Now import the following event:
BEGIN:VEVENT
CREATED:20070928T184453Z
LAST-MODIFIED:20070928T185000Z
DTSTAMP:20070928T184522Z
UID:e4aec1d1-5975-4783-a269-e7fae63f4532
SUMMARY:Test Event with a different title
DTSTART:20070928T190000Z
DTEND:20070928T200000Z
END:VEVENT
Actual Results:
On step 3, no events are imported and a message saying 1 duplicate item(s) were ignored appears
Expected Results:
The event is updated with the new title and a message saying 1 duplicate item(s) have been updated, or better yet, a dialog appears asking if you wish to update the item in question.
I'll try to attach the .ics files to make this easier to test.
Comment 3•18 years ago
|
||
Seems like a duplicate of Bug 325449. Objections?
No objection here.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Updated•18 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•