Closed
Bug 685319
Opened 13 years ago
Closed 13 years ago
Event invites can not be "accepted"/saved to Google-Provider-based calendar in Lightning
Categories
(Calendar :: Provider: GData, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 684482
People
(Reporter: bugzilla.mozilla.org, Unassigned)
References
Details
User Agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.6.8; U; en) Presto/2.9.168 Version/11.51 Steps to reproduce: What I did: received an event invite from a non-google/Outlook email addr/MUA. Actual results: What happened: couldn't save a meeting invite (via an "Accept" button) to my google calendar. Expected results: What should have happened: should have been able to save to my google-provider-based calendar. Details: MacOS 10.6.8 Thunderbird 6.0.2 Provider for Google Calendar: 0.8 Lightning 1.0b5 Receive meeting invite (from an Outlook sender with a non-google email address). Can not "accept" the meeting invite to my "synced" google calendar. Have read/skimmed [url=http://www.google.com/support/forum/p/Calendar/thread?tid=2dcfda2de638b884&hl=en]this[/url] and [url=https://www.google.com/support/calendar/bin/answer.py?answer=74783&hl=en]this[/url] and still don't understand what's wrong. Now, I -can- accept invites to my "local"/non-google-synced calendars (in Thunderbird Lightning). It's noteworthy that said calendars have an email address associated with them... and the google calendar does NOT. Suspect if the email address to which the invite was sent was "associated" with the google-provider-based calendar, that I -could- accept invites and "populate" them on said calendar. To note: the email address for which I'm receiving the emails is NOT the primary address in said google account, but it IS an "alternative" email addr in said google account. But for whatever reason, this isn't working. Thoughts? Side note: seems similar, but with at least slightly diff symptoms than Bug 668222.
Reporter | ||
Comment 1•13 years ago
|
||
fyi, above links (without the forum-based encoding): http://www.google.com/support/forum/p/Calendar/thread?tid=2dcfda2de638b884&hl=en https://www.google.com/support/calendar/bin/answer.py?answer=74783&hl=en
Reporter | ||
Updated•13 years ago
|
OS: All → Mac OS X
Hardware: All → x86_64
Comment 2•13 years ago
|
||
I thought I had seen this reported already, but I cannot find it back — and bug 668222 is supposedly FIXED in 1.0b5
Whiteboard: DUPEME
Reporter | ||
Comment 3•13 years ago
|
||
Roger that, thx. fwiw, I've looked around on bugzilla.mozilla.org significantly and haven't see an full dupliate. Also fyi: after looking at bug 668222 a little closer, thinking it's quite a bit different than my experience. I don't get any Accept/Deny/Tentative button to show up at all... while bug 668222 says the button display is "inconsistent" (I think).
Reporter | ||
Comment 4•13 years ago
|
||
Got another/similar report of this symptom: http://forums.mozillazine.org/viewtopic.php?p=11226071#p11226071 Note above report is a on Win7/xp, otherwise (seemingly) same apps/config as mine. Am rather surprised if this is a systemic problem. Are there not many 0.8 "business class" users that need to accept meeting invites? Further: seeking workarounds. Current workaround options I see: 1. define "local" Lightning calendar (ie, one that's not "Google Calendar" connected), accept meeting invites to this calendar, then hand-copy said invites to the google-calendar-provider-connected calendar. 2. employ another application besides TB-Lightning to accept/decline the invites, sync that app with google calendar, then sync those changes back to TB-Lightning. Any other thoughts/workarounds/suggestions/questions?
Reporter | ||
Comment 5•13 years ago
|
||
(sorry for poor line-wrapping on my above/previous post, will work to fix in future msg posts...)
Comment 6•13 years ago
|
||
Thanks for the report. This was mainly a server issue, but Google now says that there is a way to do it without breaking things. See this bug:
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•