Chad,
thanks for your help and checking on this.
I was able to try what you suggested. I got the error:
Request via script load timed out. Possible causes: feed URL is
incorrect; feed requires authentication
back from the api call below:
query = new
window.google.gdata.contacts.ContactQuery(theThis.fGoogleContactFeedURL);
query.setSortOrder('descending');
query.setShowDeleted(true);
query.setMaxResults(numInBatch);
query.setStartIndex(startIndex);
query.setUpdatedMin(null);
theThis.fContactsService.getContactFeed(query, callback, handleError);
Normally, I do check to see if I am signed into google like this:
var theToken =
window.google.accounts.user.checkLogin(window.kGoogleContactsScope,
optParams);
var status =
window.google.accounts.user.getStatus(window.kGoogleContactsScope);
however, since we were authenticating a different way, I commented out
that code.
The variable for the contact feed is:
this.fGoogleContactFeedURL = window.theHTTP + '://www.google.com/m8/
feeds/contacts/' + this.fGoogleEMailAddress + '/full' + '?
accesstoken=' +
encodeURIComponent('ya29.AHES6ZT1w3mW50HPrGgaLGCEfpry3hG_zs7BgnfAja4ObWo');
I tried with and without the v=3 option that you specified. I also
tried with and without the encodeURIComponent(), but I figured that
the component should be encoded as I saw a period in there.
As far as getting the access token, this is what I did. I took the
google-api-php-client code from google's web site and modified the
contacts demo. I got it to work and then printed the
print 'TOKEN:'.$_SESSION['token']."</br>";
which returned:
TOKEN:
{"access_token":"ya29.AHES6ZT1w3mW50HPrGgaLGCEfpry3hG_zs7BgnfAja4ObWo","token_type":"Bearer","expires_in":
3600,"refresh_token":"1\/FBIoWkK-
byVl2gV968PnE3XUpV5qrE57ZxRlXyBzQi8","created":1336017265}
I figure there's something deep in the guts of the Javascript api
that's checking something and it is realizing that I am not logged in
using the old authentication method. I did delete the cookies to make
sure that auth2 was the authentication I was using.
Let me know if you have any ideas as to other things I can try.
Would it be possible for you guys not to retire AuthSubRequestJS until
your 3.0 javascript contacts api has been released? I see that you
already have an alpha of the javascript calendar api for 3.0 and it
uses the new auth 2.0. Is there going to be a new 3.0 contacts api
for your new javascript api? If that were available, then there would
be an upgrade path available for javascript folks that are using the
contacts api.
thanks,
Scott.
--
You received this message because you are subscribed to the Google
Groups "Google AJAX APIs" group.
To post to this group, send email to
google-ajax-search-api@googlegroups.com
To unsubscribe from this group, send email to
google-ajax-search-api+unsubscr...@googlegroups.com
To view this message on the web, visit
http://groups.google.com/group/google-ajax-search-api?hl=en_US
For more options, visit this group at
http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en
