Closed
Bug 511063
Opened 15 years ago
Closed 15 years ago
GDATA provider & lightning confuse multiple Google calendars
Categories
(Calendar :: Provider: GData, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 479867
People
(Reporter: mstuff, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2) Gecko/20090803 Fedora/3.5.2-2.fc11 Firefox/3.5.2 Build Identifier: Lightning/1.0pre Thunderbird/3.0b3 ProviderGDATA 0.6pre * I set up 2 calendars on Google Calendar, say C1 & C2; * I add them both to thunderbird-lightning via GDATAprovider; * Then, for every event on C1 on google calendar, events are created on thunderbird-lightning for C1 and C2; and, for every event of C2 on google calendar, events are created on thunderbird-lightning for C2 and C1!!! * Also, for every event created on thunderbird-lightning C1 or C2 a corresponding event is created on google calendar C1 or C2, BUT then when remote calendars are reloaded - events are recreated for thunderbird-lightning on both C1 AND C2 for the corresponding event on google calendar C1 or C2 * So, confusion Reproducible: Always Steps to Reproduce: 1. Set up google calendars 2. Set up tbird-lightning for google calendars 3. Done Actual Results: multi-calendar multi-confusion Expected Results: multi-calendar non-confusion Installed as per f11 latest installs: thunderbird-lightning 1.0-0.5.20090715hg.fc11.i586 thunderbird.i586 3.0-2.6.b3.fc11 GDATA provider updated (0.6pre)
Comment 1•15 years ago
|
||
Did you enabled the experimental cache feature? If yes see Bug 479867.
Updated•15 years ago
|
Version: unspecified → Trunk
Reporter | ||
Comment 2•15 years ago
|
||
Yup, that's it - sure is a regression. Wasn't a problem using CalDEV in v2 nor from memory was it a problem using GDATA provider; now it seems to be a problem with both. So, can't use T'bird with Google calendar and store data locally - that's major security failing!
Updated•15 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•