535400 - attempted move of a task to a CalDAV server that lacks support for VTODO leads to loss of data

Status: RESOLVED INVALID

(Calendar :: Provider: CalDAV, defect)

Description

[Graham Perrin]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_2; en-gb) AppleWebKit/531.21.8 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b2pre Thunderbird/3.0

Lightning loses any task that it tries (fails) to move from a supporting CaldDAV server to Google Calendar CalDAV service.

Reproducible: Always

Steps to Reproduce:
1. configure Lightning to work with a CalDAV server that supports tasks

2. create a task on that server

3. configure Lightning to work with Google Calendar CalDAV

4. move the task to the collection (calendar) on the Google server

5. click 'Save and Close'
Actual Results:  
An error occurred when writing to the calendar …!

Details… 

Error code: MODIFICATION FAILED
Description: 

---

Task is removed from the server, 
_LOST_ from Lightning, 

Expected Results:  
IF a VTODO can not be verifiably moved to a destination,
THEN that VTODO must not be removed from its original location.

http://code.google.com/apis/calendar/caldav/
— highlights: http://ur1.ca/i043

Comment 1

[Graham Perrin]

http://identi.ca/conversation/16874347

Comment 2

[Bruno Browning]

Once the patch for bug #455232 is applied it will not be possible to select a Google calendar as a move-to location for a VTODO (or, more generally, a calendar component to a CalDAV calendar that doesn't list components of that type in its supported-calendar-component-set).

Comment 3

[Graham Perrin]

Thanks to Bruno for the reference.

Comment 4

[Philipp Kewisch [:Fallen][📱📆]]

Closing this bug since bug 455232 is fixed. Thanks for reporting though!