429090 - Accepted invitation isn't auto added to calendar after pressing "Accept" button

Status: VERIFIED DUPLICATE of bug 428851

(Calendar :: Provider: GData, defect)

Description

[Cosmin Achim]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ro; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13
Build Identifier: Lightning 0.8 with mozilla thunderbird 2.0.0.12

I've just upgraded my mozilla thunderbird addons from lightning 0.7 to lightning 0.8 and discovered that accepted invitation aren't auto added to calendar.
This use to work with lightning 0.7
Please notice that I use google calendar.


Reproducible: Always

Steps to Reproduce:
1.Sent an invitation from another account on microsoft Outlook 2003 to the account on google used to be managed with mozilla thunderbird and lightning 0.8
2.Open Mozilla thunderbird and accept the invitation.
3.Observe the reply e-mail is opened to be sent but the invitation isn't added to the calendar - this use to work with the same thunderbird but lightning 0.7


Actual Results:  
The invitation isn't added to calendar

Expected Results:  
The invitation should be added to calendar

Comment 1

[Stefan Sitter [:ssitter]]

Do you see any calendar related messages in the Error Console? If yes please copy and paste them here.

Comment 2

[Cosmin Achim]

(In reply to comment #1)

No, I don't see any calendar related messages in the Error Console.
after search on web I discovered that someone else has the same problem as I have. Please see this link: http://forums.mozillazine.org/viewtopic.php?p=3335937&sid=94a292d85b0af508a41e253ce855b24d

Regards,
Cosmin

Comment 3

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

Invitations are not really great with Google Calendar.

Please enable calendar.debug.log in the advanced config editor and then check for error console messages again.

The forum entry doesn't seem to mention google calendar or gdata. There is a thread on the gdata provider support forum though.

See also bug 384308. 

Comment 4

[Cosmin Achim]

(In reply to comment #3)
I can't find calendar.debug.log in the advanced config editor.
My invitations are sent from microsoft outlook to gmail. I'm not sure if this has anything to do with gdata.

Comment 5

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

You need to create this key, its not there by default. type boolean, value true.

Outlook is special in any case, I don't think this has to do directly with outlook though.

Comment 6

[Cosmin Achim]

(In reply to comment #5)
I think I have some errors now:

Getting item with id 040000008200E00074C5B7101A82E0080000000090E9F35478A0C80100000000000000001000000029AB5415589EFD4AB8BD9709679E1D27

calGoogleRequest: Requesting GET http://www.google.com/calendar/feeds/cosmin.achim%40gmail.com/private/full?max-results=2147483647&singleevents=false

sendItems: Sending Email...

sendXpcomMail: Creating temp file for attachment.

ICS to be emailed: BEGIN:VCALENDAR
PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN
VERSION:2.0
METHOD:REPLY
BEGIN:VEVENT
CREATED:20080417T074903Z
LAST-MODIFIED:20080417T074959Z
DTSTAMP:20080417T074959Z
UID:
 040000008200E00074C5B7101A82E0080000000090E9F35478A0C801000000000000000010
 00000029AB5415589EFD4AB8BD9709679E1D27
SUMMARY:asdadaslfksadf
PRIORITY:5
CLASS:PUBLIC
ORGANIZER:MAILTO:[e-mail]
ATTENDEE;PARTSTAT=ACCEPTED;ROLE=REQ-PARTICIPANT:MAILTO:
 [e-mail]
DTSTART:20080417T110000Z
DTEND:20080417T113000Z
TRANSP:OPAQUE
SEQUENCE:0
DESCRIPTION:When: 17 aprilie 2008 14:00-14:30 (GMT+02:00) Athens\, 
 Bucharest\, Istanbul.\n\n*~*~*~*~*~*~*~*~*~*\n\n\n
X-MICROSOFT-CDO-IMPORTANCE:1
BEGIN:VALARM
TRIGGER;VALUE=DURATION:-PT15M
DESCRIPTION:Mozilla Alarm: asdadaslfksadf
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR

createTempItipFile path: file:///C:/DOCUME~1/COSMIN~1.ACH/LOCALS~1/Temp/itipTemp

sendXpcomMail: Found USER autoResponse type.

Error parsing XML streamTypeError: item.startDate has no properties

Error getting item undefined:
TypeError: item.startDate has no properties

Hopefully this will help.

Regards,
Cosmin

Comment 7

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

It helps, yes. In that case it is the same issue as in bug 428851. Closing this issue.