Hi Bim, Thanks again for replying. As you realize, there has been no (apparent) way to achieve what I’ve been trying to do through the apis. What you may not have realized though, is that this situation is actually somewhat worse than it appears, because, when you are sharing the calendar with a group -as opposed to an individual-, there is *no way at all* that the calendar will show up for each individual in this group -in their calendar listing- unless each has clicked on the ‘invite url’ link that was emailed to them. So I’ve actually come up with a solution that worked for me until now, but it now appears to be broken once a Google Apps domain has been transitioned to the new infrastructure L. The solution for me was to have my program construct this ‘invite url ‘manually’ (taking the urls emailed as samples for me to generate it). Note that these urls *are* permanent as far as I can tell; in fact they *do* use the calendar’s id and not a random security code. However, the problem that they started presenting in the newly transitioned domain, is that the url will work for you when you click on it, but only *as long as* you are already logged into Google Apps, (otherwise, it takes you a regular Google Accounts login page; certainly very confusing to Google Apps users). Thinking that this problem might have an SSO-related flavor to it, I have posted about this problem in the SSO related forums, but I’ve been told that I am using calendar urls created in a ‘non-supported’ way, which prompted me to post here try to find out if there *is* in fact a supported way to get these urls L L.
Having said all this, I am looking into the possibility that the calendar subscription api (which did not exist at the time I came up with my original solution) might be something I can use to get around this problem. Of course it will need much more coding than my original (now broken) solution. BTW, your suggestion about sending users the invite url would not work (first of all, they are already getting the invite directly from Google Apps, but it is just not a very friendly process if they need to go read their email before they can click on one of my application’s html links L). Thanks again, -Patricia From: Bim [mailto:[email protected]] Sent: Thursday, April 14, 2011 6:06 AM To: [email protected] Cc: [email protected] Subject: Re: RE: [Calendar API] Re: FW: how to generate these calendar urls programmatically? ( TRYING AGAIN) sorry for late reply, ah yes i did misread it i thought you wanted a loop through all calendars to make public url's to them but i looked further into that and it seems there is no such thing! I am guessing the id inside the link is just a random security code generated and has no reference to the calendar so little to be found there - the only way i could find to get a public link is to sign into google calendar manually and go to calendar settings and click on the calendar address, either xml ical or html depending on which format you want and that link, as long as they are allowed to view the calendar or the calendar is public, will bring up the calendar data in that format. one way i can think of doing it is for your system to keep a public link stored for each calendar when they are created and when a person receives an invite they get the link sent to them. personally i think its a pretty bad oversight if this has been left out i think it's more likely gcal is just badly documented cause i can't find anything on how to do this bim -- You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://code.google.com/apis/calendar/community/forum.html
