Closed Bug 1228776 Opened 9 years ago Closed 9 years ago

Provider for Google Calendar does not show any calendar in selection box

Categories

(Calendar :: Provider: GData, defect)

Lightning 4.6
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1201169

People

(Reporter: denis.savostyanov, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36

Steps to reproduce:

Thunderbird 44.0a2, Lightning 4.6a2, Provider for Google Calendar 1.0.4

- Goto Calendar tab.
- In Pane "Calendars" right click.
- Select "New Calendar".
- Within the Popup select "On Network" -> Next
- Select "Google Calendar" -> Next
- only one line shown up with entry field -> enter your google calendar mail -> Next
- Within the empty pane all calendars belonging to the entered google calendar mail shall show up.


Actual results:

Empty selection list. Maybe because login fails, because password required.

JavaScript error: resource://gdata-provider/modules/gdataSession.jsm, line 136: ReferenceError: OAUTH_BASE_URI is not defined


Expected results:

Selection list filled with at least one calendar belonging to the entered mail address. If login required -> ask for password.

Close Bug 1201169 and Bug 1201812
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
This problem was fixed with Bug 1201169. But you are still using old Provider for Google Calendar 1.0.4 release build that is meant to be used with Lightning release builds. 

When using Lightning test builds you should be using the matching Provider for Google Calendar test build. For Lightning 4.6a2 us Provider for Google Calendar 2.5a2 that can be found in the same folder: https://ftp.mozilla.org/pub/calendar/lightning/nightly/latest-comm-aurora/
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Hello Stefan!
Thank you very much.
Now - work!

I thought provider can be automatically update. Now I will update manualy!
Thanks!
You need to log in before you can comment on or make changes to this bug.