Closed Bug 277443 Opened 20 years ago Closed 19 years ago

Mozilla Calendar Doesn't Warn When WebDAV Error Occurs

Categories

(Calendar :: Sunbird Only, defect)

Product:
Calendar
Component:
Sunbird Only
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 306508

People

(Reporter: cdjones, Assigned: mostafah)

Details

We're using WebDAV to store calendar files for our department. We have a user A who needs to be able to write to a shared calendar with user B, but also to view a personal calendar published by user B. Both A and B have PUT access for the shared calendar, but only B has PUT access for the personal calendar. All operations work as expected, if somewhat slowly, with the shared calendar, but when user A accidentally creates an event in B's personal calendar on A's Mozilla instance, there is no warning that A does not have permission to do that (or, alternately, that the WebDAV PUT operation failed). Instead, the new event is happily accepted by Mozilla Calendar and shows up on A's screen until B's personal calendar is refreshed by A, at which point it disappears (which, while expected behaviour from a technical point of view, is unexpected from a general user perspective). The application should either (1) note when it is unable to PUT a calendar and warn the user when the user tries adding an event to that calendar, or (2) warn the user when the attempt to PUT the calendar after adding the event fails.
What version of calendar are you using?
2004-12-17 with Mozilla 1.7.
bug 271029 should have made the error pop up after webdav put fails. Are you using publish automaticly? Does an error show up if you manually publish after editing a calendar you can't publish to?
(In reply to comment #3) > bug 271029 should have made the error pop up after webdav put fails. Are you > using publish automaticly? Does an error show up if you manually publish after > editing a calendar you can't publish to? We're using publish automatically. I don't know whether it happens after a manual publish attempt, but I'll try that out and report back.
QA Contact: gurganbl → sunbird
Should have been fixed by the error reporting bug *** This bug has been marked as a duplicate of 306508 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.