5점중 1점 받음

작성: mia1dolfan, 날짜: 4월 24, 2012 ·

FACT:
1. Anyone that says that this addon works flawlessly doesn't have to process invitations into there Google Calendar, which doesn't work, period.

2. Thunderbird Lightning is able to process Google Calendar requests out of the box, without the need of this addon, and is able to process invitations into Google Calendar, via Caldav. I urge users reading this to try Caldav first, which is the supported method.

-----

This add-on, while good intention, creates more confusion than it's worth, as people think that this add-on is required to access Google Calendar, and issues with this plugin and Caldav become intertwined creating more confusion on the forums and bug reporting. I urge the author to do the community a favor and remove this addon from the repository. If your going to donate, do so to the Mozilla foundation that manages Firefox and Thunderbird.

이 검토는 현재 부가 기능의 이전 (0.9) 버전에 대한 것입니다. 

5점중 4점 받음

작성: mia1dolfan, 날짜: 12월 1, 2011 ·

It's killing me... In my previous post I said that I turned to Evolution, however Evolution suks much more. It is such a shame I have to open Evolution to accept a invite into my Gmail calendar. No other features should be added until this is resolved!!! I tried adding the calendar via Caldev but still can only accept invites to local calendar. :(

이 검토는 현재 부가 기능의 이전 (0.9) 버전에 대한 것입니다. 

5점중 3점 받음

작성: mia1dolfan, 날짜: 9월 23, 2011 ·

Processing invitations properly into Google calendar is vital for Thunderbird. Such critical extension should be supported by the Mozilla / Lighting team, in addition to the community. Evolution accepts calendars requests properly, and to the best of my knowledge Thunderbird is the only mail client to exhibit this behavior... for many years now :( Several bugs have been logged on Google on this, and they all have been invalidated. I use Evolution now because of this, even though I prefer Thunderbird otherwise.

이 검토는 현재 부가 기능의 이전 (0.8) 버전에 대한 것입니다. 

작성: Philipp Kewisch (개발자), 날짜: 9월 26, 2011 ·

Agreed, this needs to be fixed. I found a new way to do so, if you want to track it see this bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=684482