Closed
Bug 429938
Opened 18 years ago
Closed 18 years ago
no cancelation message is send to attendees if event is deleted
Categories
(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)
Calendar
E-mail based Scheduling (iTIP/iMIP)
Tracking
(Not tracked)
VERIFIED
FIXED
0.9
People
(Reporter: juergen.edner, Assigned: informatique.internet)
Details
Attachments
(2 files, 1 obsolete file)
|
11.84 KB,
patch
|
Fallen
:
review+
|
Details | Diff | Splinter Review |
|
1.33 KB,
patch
|
dbo
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
Build Identifier: Thunderbird v2.0.0.12 (20080213) / Lightning v0.9pre (2008041918)
An event has been created which includes attendees and the parameter "Send attendees invitations via email" has been checked. When this event is being deleted no cancelation message is send to the attendees.
Reproducible: Always
Steps to Reproduce:
1. create and event, add attendees, check "Send attendees invitations via email" box.
2. save event
3. delete the event
Actual Results:
the event is being deleted without sending a cancelation message.
Expected Results:
a dialog should appear when the event is being deleted which asks if a cancelation message should me send or not, like OL2K3 is doing it.
Updated•18 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
| Assignee | ||
Comment 1•18 years ago
|
||
Implement event canceling when deleting the whole event or deleting an attendee
please review!
Attachment #318396 -
Flags: review?(daniel.boelzle)
Comment 2•18 years ago
|
||
Comment on attachment 318396 [details] [diff] [review]
Implement event canceling
It would be great if the attendee-calculation part this part of the code could be revised a bit. A lot of nested loops are used (i.e .some() will internally loop through itemAtt) My idea would be to use a js object to create a map of attendees on the original item,
for each (var att in originalItemAtt) {
attMap[att.id] = att;
}
for each (var att in itemAtt) {
if (att.id in attMap) {
// Attendee was in original item.
delete attMap[att.id]
} else {
// Attendee was not in original item
addedAttendees.push(att);Arrays
}
}
// Now attMap should contain all original attendees, that are not in the new item. These can be canceled.
// addedAttendes contains those that were not in the original item but are in the new item. These can be invited
Does this make sense? Please tell me if this doesn't improve performance.
>+ } else
>+ {
>+ recipients = aRecipientsList;
} else {
>+ switch (aTypeOfInvitation) {
>+ case 'request':
>+ item.setProperty("METHOD", "REQUEST");
>+ break;
>+ case 'cancel':
>+ item.setProperty("METHOD", "CANCEL");
>+ break;
>+ }
I think the value of the aTypeOfInvitation parameter should be uppercase, then you could directly set the method here.
>+imipBarCancelText=This message contains a canceling to an event.
This message contains an event cancellation.
>+itipCancelBody=%1$S has cancelled this event : « %2$S »
in en-US, its canceled, in en-GB its cancelled. Please correct to en-US. I'd remove the space before the : also.
r- for now, but only to get a new patch with comments fixed and the map-thing considered.
Attachment #318396 -
Flags: review?(daniel.boelzle) → review-
Updated•18 years ago
|
Assignee: nobody → informatique.internet
Updated•18 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 3•18 years ago
|
||
Attachment #318396 -
Attachment is obsolete: true
Attachment #319568 -
Flags: review?
| Assignee | ||
Updated•18 years ago
|
Attachment #319568 -
Flags: review? → review?(philipp)
Comment 4•18 years ago
|
||
Comment on attachment 319568 [details] [diff] [review]
Implement event canceling v2
Looks good, I'll add a couple of extra brackets for one-line if() statements according to our style guide before checkin
r=philipp
Attachment #319568 -
Flags: review?(philipp) → review+
Comment 5•18 years ago
|
||
Checked in on HEAD and MOZILLA_1_8_BRANCH
-> FIXED
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Target Milestone: --- → 0.9
| Assignee | ||
Comment 6•18 years ago
|
||
There's still a bug with this implementation. If there's only one attendee, delete this attendee and no cancel message is sent...
Resolution: FIXED → INCOMPLETE
| Assignee | ||
Updated•18 years ago
|
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
| Assignee | ||
Comment 7•18 years ago
|
||
Attachment #321595 -
Flags: review?
| Assignee | ||
Updated•18 years ago
|
Attachment #321595 -
Flags: review? → review?(philipp)
| Assignee | ||
Updated•18 years ago
|
Attachment #321595 -
Flags: review?(philipp) → review?
Updated•18 years ago
|
Attachment #321595 -
Flags: review? → review?(daniel.boelzle)
Comment 8•18 years ago
|
||
Comment on attachment 321595 [details] [diff] [review]
[checked in] Fix last bug...
looks good, r=dbo
Checked in on HEAD and MOZILLA_1_8_BRANCH.
What's IMO is yet a bit odd is if you remove some attendees and add some others, you get asked twice if you want to notify the attendees.
Attachment #321595 -
Attachment description: Fix last bug... → [checked in] Fix last bug...
Attachment #321595 -
Flags: review?(daniel.boelzle) → review+
Comment 9•18 years ago
|
||
Hubert, set this bug to FIXED if everything's fixed.
| Assignee | ||
Comment 10•18 years ago
|
||
It seem's to be ok!
Status: REOPENED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → FIXED
Comment 11•17 years ago
|
||
Checked in lightning build 2008072919 -> VERIFIED
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•