Hi,

Sorry that you had so much trouble trying to get this to work.  The edit URL
for an event in a calendar should be present if you have "write" access
(ability to create/update/delete event) to that calendar.  This means that
you either have owner or editor access to this calendar.  You have owner
access to any calendars that you created and thus have "write" access to
them.  Any calendars you have subscribed to, the owner of that calendar must
explicitly grant owner or editor access with you in order for you to have
"write" access, otherwise when you pull the event feed for the calendar you
won't be able to see the edit URL.

Another thing to look for is to make sure you are using the private/full
feed URL when you submit the GET request.  Feed URL should look like -

http://www.google.com/calendar/feeds/[CAL_ID]/private/full

Replace CAL_ID with the calendar ID, you should always use private/full
otherwise you won't be able to see the edit URL.  The edit URL would look
like this as an XML element -

<atom:link rel="edit" type="application/atom+xml" href="
http://www.google.com/calendar/feeds/default/private/full/a9f0ijqfg2qvrc2a1bc8i67er8/63344689609
"/>

Lastly, make sure that you are not specifying an alternative format such as
RSS or JSON.  Those feeds format are for read-only, hence no edit URL will
be returned.

These information I just gave can be found in the Calendar Reference Guide -


http://code.google.com/apis/calendar/reference.html

Hope that helps,
Austin

On Thu, Apr 24, 2008 at 11:53 PM, rgarito <[EMAIL PROTECTED]> wrote:

>
> First of all, I want to repeat the concerns of many of the other
> posters here that the documentation for the Google Calendar API is
> quite frankly, terrible.  A lot of important information is missing
> and some of it does not work at all as described.
>
> I am using raw XML and HTTP requests for this project, as the code is
> written in non-dot-net Visual Basic.  There are no API libraries
> available for my environment.  There are almost no example code
> snippets out there for this scenario.  Shame on Google for this, as
> there are a lot of us who's code base contains millions of lines of
> code in older languages that cannot be converted every time a new,
> fancy version of Microsoft's compilers come out (ie, .NET).
>
> Case-in-point:
>
> DELETE an event--one is supposed to send a DELETE request to the EDIT
> uri.  Except that there is no edit URI ever presented to us!
>
> The code works something like this:
>
> 1)  Log in to google using the ClientLogin method.  (ie, subsequent
> requests include the "Authorization: GoogleLogin auth=xxxx" entry in
> the HTTP header).  We are NOT using the "magic cookie" method, which
> is documented as not returning EDIT URI's.
>
> 2)  Obtain a list of all calendars of the user.  (this works fine and
> we do receive an EDIT uri for each calendar itself)
>
> 3)  For each calendar, obtain a list of all entries in the calendar
> (using the Post URI from the above calendar entries in #2).
>
> 4)  For each entry that we want to delete, perform a DELETE with the
> ID obtained in step 4 above.  ***BUT*** There is no edit URI returned
> in step 3.  We have tried Self and Alt (the only 2 URI's returned) and
> neither works.  Both return a 501 NOT IMPLEMENTED error.
>
> As a test, I also tried modifying step 2 with the EDIT URI of the
> calendar instead, but got no event entries in step 3 when I did this.
>
> I also tried all of the scenarios using a PUT event with an X-HTTP-
> Method-Override: DELETE in the header with exactly the same results
> (so it's not a proxy server issue).
>
> So, where is this elusive EDIT URI that is required to do a DELETE?  I
> have seen a ton of people ask this same question and nobody seems to
> be getting any answers....
> >
>

--~--~---------~--~----~------------~-------~--~----~
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://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to