Closed Bug 281484 Opened 20 years ago Closed 20 years ago

removing all events from a remote (webdav) calendar causes reload error

Categories

(Calendar :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 231321

People

(Reporter: m.watts, Assigned: mostafah)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Removing all events from a webdav calendar causes the file on the server to be
zero bytes. This seems to confuse sunbird 0.2 into thinking its not a valid
calendar.

Reproducible: Always

Steps to Reproduce:
1. Create local calendar, add an event then upload it to a webdav server.
2. Remove local calendar so you are only using remote one.
3. Remove all events from remote calendar.
4. Attempt to either "reload remote calendar" or add a new event.

Actual Results:  
Error dialog: "Error getting calendar"

"This doesn't seem to be a valid file. Here's what I got back from"
"http://<url>
"Result:"

Expected Results:  
Software should treat a zero-sized file as an empty calendar.
Adding events to empty calendars should work as expected.
This also fails on 0.2 Sunbird for Windows, in the same way.

Came here to report this bug, tacked this comment onto this bug report to avoid
submission of duplicate. Please update the platform to "all", and set the bug to
"confirmed".
Sorry to be a bother. One further comment: upon encountering this zero byte file
and delivering the error message noted previously, the small loading animated
graphic in the calendars list continues spinning, and refuses to stop until the
application is restarted. 

*** This bug has been marked as a duplicate of 231321 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!
QA Contact: gurganbl → general
You need to log in before you can comment on or make changes to this bug.