Bug 770793 - Lightning - Google Calendar
Summary: Lightning - Google Calendar
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird-lightning
Version: 16
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-29 06:15 UTC by pavlik.horak
Modified: 2011-12-29 20:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-29 20:47:14 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 574568 0 None None None Never

Description pavlik.horak 2011-12-29 06:15:55 UTC 
Description of problem:
It is not possible to add, modify or delete new item in Google calendar.

Version-Release number of selected component (if applicable):
Thunderbird 9.0 + Lightning 1.1-0.1.rc1.fc16

How reproducible: Every


Steps to Reproduce:
1.Add New Network Calendar,iCalendar(location)....
2.Add new Google calendar item.
3.Modification failed
  
Actual results:
Modification failed

Expected results:
Is it possible to add,modify or delete Google calendar item through Thunderbird.


Additional info:
Error code: MODIFICATION_FAILED
Comment 1 Orion Poplawski 2011-12-29 17:43:59 UTC 
Instead of using iCal (ICS) try using "Google Calendar" and the XML url for your google calendar.
Comment 2 pavlik.horak 2011-12-29 19:13:19 UTC 
Yes, It is working now. Main "problem" option Google calendar is available only with plugin "Provider for Google calendar".
Excuse me my mistake. :-)
Comment 3 Orion Poplawski 2011-12-29 20:47:14 UTC 
Well, the plugin "Provider for Google calendar" comes with Lightning, so it's not that big of a deal.  It should still work with ICS, but at least there is a workaround.  I'm going to close here though, hopefully upstream will fix at some point.
Note You need to log in before you can comment on or make changes to this bug.