Calendar:Google Provider: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Initial Version)
 
(Remove outdated information, redirect to new page)
 
Line 1: Line 1:
Please remind that this provider '''IS STILL PRELIMINARY, NO WARRANTY!'''
#REDIRECT [[Calendar:GDATA_Provider]]
 
==Initial Steps==
To enable Google Calendar support, the following steps are required:
 
* Select the 'Advanced' tab in Sunbird/Lightning preferences.
* Select the 'General' sub-tab.
* Click on 'Config Editor...'
* Right click in the lower right area and select 'New' -> 'Boolean'
* Enter <code>calendar.google.enabled</code> as the preference name.
* Select <code>true</code>.
 
==Subscribing To Your Calendar==
The Sunbird/Lightning ''Create New Calendar'' wizard comes up with a third Format type for remote calendars (''Google Calendar''). As location, provide the XML calendar address from Google:
 
* Open the Google Calendar GUI
* Click on the down arrow next to the calendar you want to use in Sunbird/Lightning.
* Select 'Calendar Settings'.
* Click on the orange XML button.
* Copy this link into your clipboard.
* Insert this link into the location textbox.
 
==Login==
There are two types of login queries you may encounter. The first variation asks for a username and a password. This is also the type of dialog you will get when you first create your calendar. Here you decide which account name is used to access the calendar. Its use is revealed when you use a non-default Google calendar, where the calendar name is ''long-hash-value@group.calendar.google.com'' but the account name required is still your google email address.
 
The second type of dialog only asks for a password. This is explicitly the password for the account name. If the account name is wrong you may cancel the dialog and can then reenter your account credentials.
 
Note that currently, if you cancel the dialog with the username and password, you won't be asked again and must restart the application to reenter the password.
 
The account authorization is securely made via https, but the calendar data is requested via http.
 
==Restrictions==
There are some restrictions and known issues in the current version.
 
===Restricted by Google===
 
* Event Categories
* Event Priority
* Event Status Cancelled (Warning: Setting this status eventually deletes the event)
 
===Restricted by the Google Provider===
 
* Recurring Events are not implemented. You will see the single occurrences of the event, but you will probably have errors when you try to edit them.
* Alarms have not been patched yet. Don't expect to be reminded.
* Attendees and notifications of Attendees have not been patched yet.
 
==Logging==
The provider can log for diagnose purposes. If you suspect an error, check the javascript console and be sure to enable <code>calendar.debug.log</code> if you want all debugging info.
 
 
==Misc==
*Total Progress tracked via [https://bugzilla.mozilla.org/show_bug.cgi?id=335826 bug 335826]
*Minimal Support tracked via [https://bugzilla.mozilla.org/show_bug.cgi?id=355117 bug 355117]

Latest revision as of 17:38, 7 March 2007