Closed
Bug 445483
Opened 16 years ago
Closed 16 years ago
Modifying an occurrence sends an incorrect email to those invited
Categories
(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mail, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061712 Fedora/3.0-1.fc9 Firefox/3.0 Build Identifier: Lightning 0.8 When modifying an occurrence of a recurring calendar entry, sending an invite to the attendees will send an icl file with the details of the first instance, not the modified occurrence. Reproducible: Always Steps to Reproduce: 1. Create a recurring event ensuring that it sends an invite to attendees. 2. Accept the invitation as the attendee 3. Update one of the occurrences, changing the date 4. Accept the invitation on as the attendee 5. Check the email which shows the date of the first occurrence 6. Check the calendar to see that it hasn't updated. Actual Results: The wrong icl file is sent to the attendees and the calendar is not updated. Expected Results: The correct icl file should be sent and the calendar should be updated.
Updated•16 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 1•16 years ago
|
||
Matthew, this bug seems to be fixed already and works for me (either with the itip overhaul or some follow-up, I can't remember). Could you please recheck with a recent nightly build? Thanks. I am marking this WFM for now, please reopen if you disagree.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 2•16 years ago
|
||
Hi, Thank you for getting back to me. I can confirm that this does work for interactions between the latest nightlies in Thunderbird 3. However, if you send an updated invite to someone who is only using Thunderbird 2/lightning 0.9, it does have an issue. The correct invite was sent from the lightning nightly, but my colleague was unable to accept the updated invitation in lightning 0.9. I understand that this may not be something that you can fix, so I'm happy for it to be resolved.
You need to log in
before you can comment on or make changes to this bug.
Description
•