Closed
Bug 942644
Opened 11 years ago
Closed 11 years ago
Lightning 2.6.3 does not send invites from CalDAV cals; only cancellations
Categories
(Calendar :: Provider: CalDAV, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: siim, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release) Build ID: 20131115110311 Steps to reproduce: 1. Create/modify CalDAV calendar entry with attendees 2. Save and close Actual results: No notifications sent to invited attendees; except if cancelling/deleting the event. Expected results: A box with an option to send an update notification to attendees should appear.
Issue appeared after the latest upgrade of Lightning to 2.6.3
Comment 3•11 years ago
|
||
Hi, Same issue here (after Thunderbird update to 24.1.1 on x64 ubuntu 13.10 + Lightning upgrade to 2.6.3)
I can confirm that this is happening on Thunderbird 24.1.1/Lightning 2.6.3 on Windows 7 and XP platforms as well. Something has broken thats not popping up the box to send the alert.
Comment 5•11 years ago
|
||
Looks like a duplicate of Bug 942576. Do you get any error messages in Tools > Error Console during the steps you have listed above? If yes: please copy and paste them here.
Flags: needinfo?(siim)
I can confirm that rolling back to 24.1.0 and lightning 2.6.2 resolves the issue. Anyone else wishing to roll back can download the proper versions from these two URLS. https://addons.mozilla.org/en-US/thunderbird/addon/lightning/versions/ http://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/
I can further report that just rolling back lightning to 2.6.2 resolves the issue.
Comment 10•11 years ago
|
||
calendar-js/calDavRequestHandlers.js components/calDavCalendar.js have both changed between the versions. The rest of the tree, as best as I can tell, is the same.
Comment 11•11 years ago
|
||
I think the problem may be at line 161 in calendar-js/calDavRequestHandlers.js. The function multigetSyncHandler now has 7 parameters, except in this call, it has the original 6, so fields arent where they are supposed to be. I think that probably putting another null in the parameters list might fix things. I will test and report back.
Comment 12•11 years ago
|
||
See Bug 930132 Comment 54 and following about the incomplete multigetSyncHandler patch.
Comment 13•11 years ago
|
||
Thanks Stefan, that's the fix. How soon can we get a new 2.6.4 release with those patches?
Comment 14•11 years ago
|
||
@Stefan: should we rather close Bug 942576 as a dup of this one here, since here seems to exist more information and a workaround description...
Comment 15•11 years ago
|
||
I confirm Bug 930132 Comment 56 patch (Attachment #8339151 [details] [diff]) fix the problem and make appear again the box with an option to send an update notification to attendees. Thanks!
Comment 16•11 years ago
|
||
Thanks. But now I have find a new bug: If I get an invitation, I can't accept or reject it, because there is no Checkbox to accept or reject the invitation.
Comment 18•11 years ago
|
||
Issue resolved with latest patch in Bug 930132. Comment 16 is a duplicate of Bug 927346, so closing this one now...
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 19•11 years ago
|
||
Works well with Sven's patch. Thanks for the help!
Comment 20•10 years ago
|
||
Same problem described here with Thunderbird (latest version) with lightning 2.6.4 (tested on 2.6.5 too). I tested also thundebird 24.1.0 and lightning 2.6.2 but the problem persist. With debugging log I can see that thundebird see that caldav doesn't support caldav scheduling ("CalDAV: Server does not support CalDAV scheduling") but no dialog appear. The backend is and Horde 5. I can provide to developer user account and caldav access to our systems. With thundebird 17 and lightning 1.9.1 all work fine.
Comment 21•10 years ago
|
||
I can confirm that on Thunderbird 24.2.0 and lightning 2.6.4 on Ubuntu 13.04
Comment 22•10 years ago
|
||
Mauri & Ivan, your problem seems to be discussed in bug 952151.
You need to log in
before you can comment on or make changes to this bug.
Description
•