952151 - Invitation not send after connected with Caldav (Horde)

Status: UNCONFIRMED

(Calendar :: Provider: CalDAV, defect)

Description

[Sovannaroth]

User Agent: Mozilla/5.0 (Windows NT 6.2; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20131112160018

Steps to reproduce:

HI,

I have connect TB/Lightning through CalDav to a Calendar server (Horde Kronolith). I tried it with the other calendar client (evolution) and it is working as expected. When creating an event, the option notify on attendee is already selected before I save the event. I use Lightning 2.6.4 and Thunderbird 24.2.0 both on Linux and windows are not work for invitation.


Actual results:

- Invitation not send to attendee and have the following error in Error Console

Timestamp: 12/19/2013 11:41:03 PM
Error: [Exception... "'[JavaScript Error: "a is undefined" {file: "chrome://calendar/content/calendar-month-view.xml" line: 935}]' when calling method: [calIObserver::onModifyItem]"  nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame :: resource://calendar/modules/calUtils.jsm -> file:///C:/Users/sovannaroth/AppData/Roaming/Thunderbird/Profiles/db33xddf.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calUtils.js :: notifyFunc :: line 1265"  data: yes]
STACK: undefined
Source File: resource://calendar/modules/calUtils.jsm -> file:///C:/Users/sovannaroth/AppData/Roaming/Thunderbird/Profiles/db33xddf.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calUtils.js
Line: 1267


Timestamp: 12/19/2013 11:44:05 PM
Error: foundAttendee is null
Source File: resource://calendar/modules/calItipUtils.jsm
Line: 1214


Expected results:

An email should be get by attendee or an pop up notification to ask for sending email to attendee.

Comment 1

[Robert Schetterer]

Hi i confirm this behave , please fix it.

Comment 2

[Ludovic Marcotte]

This happens if the email address associated to your CalDAV identity doesn't match one from the event attendees list. This generally means that your server configuration is broken.

Comment 3

[Robert Schetterer]

Yes and No, to make this work the server must have caldav scheduling enabled, but some servers dont have this feature full implemented yet i.e Horde, in the TB error console can be seen, that TB is informed about the server does not do scheduling ( as well there is a "hard" setting in Lightning for that calendar.caldav.sched.enabled;false), so the expected behave is fallback to local send.

Comment 4

[Christian Reischl]

I had the same problem on several Thunderbird clients and SOGo as CALDAV backend.

Switching the calendars associated email address to none and then back to the correct address fixed the problem.

Comment 5

[Christian Reischl]

in addition to my former comment:
calendar.caldav.sched.enabled was and still is set to false in all cases

Comment 6

[u511987]

We also have the problem that Lightning isn't sending out email invitations.
We're using SOGo here, too.

I tried switching the associated email address to none and back, but that didn't help.

Also, changing "calendar.caldav.sched.enabled" didn't have any effect.

I even don't get any error messages reported in Tools -> Error Console. Or do I need to do anything first in order to get those messages?

It may be worth noting that the calendars for which sending out invitations doesn't work are functional non-person calenders. I.e. they don't belong to the person creating the event and wishing to send invitations, but the person has full permissions on it (Change for all privacy levels, create and delete).

I'm not sure if this is a problem in Lightning or SOGo and any clues as to how to debug it further might be helpful.

Comment 7

[Philipp Kewisch [:Fallen][📱📆]]

Could you enable calendar.debug.log and calendar.debug.log.verbose in the advanced config editor (Options > Advanced > General > Config Editor) and show us some logs about what is happening when you do this?

The calendar.caldav.sched.enabled pref is mostly broken, so I'd suggest disabling it. Also, make sure you have the correct identity set in the calendar properties dialog.