301586 - Delete event from remote calendar does not update server

Status: RESOLVED WORKSFORME

(Calendar :: General, defect)

Description

[Serge Knystautas]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

I have subscribed to a remote calendar on a server and set it to automatically
publish changes to the remote calendar.  I can add or update events just fine,
but if I try to delete it, the next time I reload the remote calendar, that
event will reappear.  My remote calendar is on a communigate pro server,
accessed using WebDAV.  I can delete the event using their web-calendar
interface, so I know the server can delete it, and everything else works fine. 
Just doesn't seem like the delete is propagated to the remote calendar.

Reproducible: Always

Steps to Reproduce:
1. Subscribe to remote calendar, click to automatically publish your changes to
the remote calendar.
2. Create an event on the remote calendar.
3. Reload the remote calendar to confirm it is on the server.
4. Delete the event on the remote calendar (it will appear deleted locally)
5. Reload the remote calendar

Actual Results:  
Grimaced because the event has reappeared.

Expected Results:  
The event should not appear... it should be removed from the remote calendar.

Comment 1

[Serge Knystautas]

Sorry, though the user-agent would have picked up this info.  This is in Mozilla
Calendar 2005011112-cal, both when using it in the Thunderbird extension and the
Firefox extension.

Comment 2

[Joey Minta]

(In reply to comment #1)
> Sorry, though the user-agent would have picked up this info.  This is in
> Mozilla
> Calendar 2005011112-cal, both when using it in the Thunderbird extension and
> the
> Firefox extension.
> 

That's a really old version.  Please try testing with Sunbird 0.3a1 and report back.  I think this has been fixed in that build.

Comment 3

[Joey Minta]

No response from reporter.  Issue should be fixed in current builds/WFM.