Closed
Bug 632317
Opened 12 years ago
Closed 12 years ago
Error accepting meeting invitation when more than one calendar is assigned to this email account
Categories
(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)
Tracking
(Not tracked)
RESOLVED
FIXED
1.0b4
People
(Reporter: tleepa, Assigned: Fallen)
Details
Attachments
(1 file)
834 bytes,
patch
|
bv1578
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b12pre) Gecko/20110205 Firefox/4.0b12pre Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b12pre) Gecko/20110205 Thunderbird/3.3a3pre Lightning/1.1a1pre.20110203 When I get an email invitation (from Outlook/Exchange) to account A and try to accept it, the following error is logged in the error console: Error: calGetString is not defined Source file: resource://calendar/modules/calItipUtils.jsm Line: 472 This happens, when I have more than one calendar that have the account A configured in its properties. Reproducible: Always Steps to Reproduce: 1. Have more than one calendar configured with the email account you get the meeting invitations to. 2. Accept the meeting in this account Actual Results: Nothing and the error logged in the console Expected Results: The dialog should be presented that would allow to choose the calendar to save the invitation to.
Reporter | ||
Updated•12 years ago
|
Version: unspecified → Trunk
Assignee | ||
Comment 1•12 years ago
|
||
This patch takes care, thanks for catching this!
Assignee: nobody → philipp
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Attachment #510531 -
Flags: review?
Assignee | ||
Updated•12 years ago
|
Attachment #510531 -
Flags: review? → review?(bv1578)
Comment on attachment 510531 [details] [diff] [review] Fix - v1 r+
Attachment #510531 -
Flags: review?(bv1578) → review+
Assignee | ||
Comment 3•12 years ago
|
||
Pushed to comm-central <http://hg.mozilla.org/comm-central/rev/74eff51b6489> -> FIXED
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Trunk
You need to log in
before you can comment on or make changes to this bug.
Description
•