| Summary | No free/busy info for Google Calendar | 
| Queue | Kronolith | 
| Queue Version | 2.1.4 | 
| Type | Bug | 
| State | Not A Bug | 
| Priority | 2. Medium | 
| Owners | |
| Requester | colan (at) openject (dot) com | 
| Created | 01/28/2008 (6490 days ago) | 
| Due | |
| Updated | 05/22/2008 (6375 days ago) | 
| Assigned | 05/11/2008 (6386 days ago) | 
| Resolved | 05/22/2008 (6375 days ago) | 
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No | 
Taken from
State ⇒ Not A Bug
information is broken, aka useless. It does *not* contain *any* free
or busy periods.
State ⇒ Assigned
State ⇒ Feedback
http://lists.horde.org/archives/kronolith/Week-of-Mon-20080428/006810.html
New Attachment: example.ics
maybe it's supposed to be ".vcs". I'm not really sure. Anyway, here
it is.
State ⇒ Feedback
it doesn't get lost again?
that it's huge, so it takes a while to do anything with it. I'm not
sure how effectively we're caching, though, and it doesn't seem to
give usable information for me either.
Assigned to
State ⇒ Assigned
deduce the free/busy times from it?
deduce the free/busy times from it?
http://www.google.com/calendar/ical/eric.standlee@gmail.com/public/basic as
listed over at
http://crusaderx.blogspot.com/2006/04/google-calendar-feature-share-freebusy.html. Adding him as an attendee yields no
information.
Now that you mention it, I'm not sure if that's a free/busy feed or a
full calendar feed. Which is it? I thought they were the same. It
looks like that's all Google Calendar offers. Maybe they don't
support free/busy feeds after all.
State ⇒ Feedback
free/busy feed, not the full calendar feed? They're different things.
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
Queue ⇒ Kronolith
Summary ⇒ No free/busy info for Google Calendar
Type ⇒ Bug
Google Calendar free/busy URL,
http://www.google.com/calendar/ical/<e-mail-address>/public/basic, "No
information" is all that comes up even though the non-iCal URL,
http://www.google.com/calendar/embed?src=<e-mail-address>&ctz=America/Toronto,
shows that the user is busy/not busy. So there is information. It's
just not being read or processed.