Closed
Bug 730537
Opened 12 years ago
Closed 10 years ago
cached calendar does not update
Categories
(Calendar :: Provider: GData, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: sirrahn, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 Build ID: 20120208060813 Steps to reproduce: I had updated tome calendar entries on a google calendar through my iphone. Actual results: The calendar entries on lightning did not up date automatically and did not update when i refreshed the calendars manually. I checked google calendars and the changes were displayed correctly. I went into the properties of the calender on lightning and unchecked the cache option. The entries updated and were correct. Expected results: Lightning should have updated the calendars.
Comment 1•12 years ago
|
||
How do you access Google Calendar? Using the built-in CalDAV provider or using the Provider for Google Calendar extension?
Good question - how can I tell, the properties dialogue does not indicate. I'm pretty sure that when I set up the calendars I choose 'google calendar' from the list (I assume that is the google calendar extension?)
Updated•12 years ago
|
Component: General → Provider: GData
QA Contact: general → gdata-provider
Comment 3•12 years ago
|
||
Nathan, take a look at the url for the calendar in the Properties panel (you can scroll your mouse across the entry to the far right of the field). iCal (CalDAV) urls will end in .ics. XML (usable under GData Provider) will have no extension.
Hi, I'm pretty sure that it was a calendar with a. .ics extension.
Comment 5•12 years ago
|
||
If this is still an issue *and* if the problem occurs with an iCal calendar, this bug should be moved to the appropriate component. Nathan, are you still seeing this with newer Lightning and GData builds?
Hi, sorry Lewis I'm not using it anymore. This bug might have defeated me, I just couldn't afford to lose appointments etc.
Comment 7•12 years ago
|
||
Thanks for following up, Nathan. I recommend we close this.
Updated•10 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•