search

northworld / google_calendar

A minimal wrapper around the Google Calendar API
http://northworld.github.io/google_calendar
MIT License
315 stars 134 forks source link

Google calendar API deprecation (gdata) #36

Closed jlovick closed 9 years ago

jlovick commented 10 years ago

Am i right that this does not affect us?

http://googleappsupdates.blogspot.ca/2014/06/calendar-gdata-api-google-calendar.html

Cheers Joe

szich commented 10 years ago

It does affect us... a update is in the works.

bfosberry commented 10 years ago

Any eta on this?

I need the features on master, but it doesnt work :P

szich commented 10 years ago

No eta yet. But we're working on it at our company (Northworld) as we use it internally.

prokopsimek commented 10 years ago

I'm waiting 4 update too :) Need to use public calendar...

swmorey commented 10 years ago

Do you anticipate releasing an update before November 17 to preserve functionality once the old API is shutdown?

szich commented 10 years ago

@swmorey - I think so. We're working on it right now. We're doing our best to keep the API the same but we will have to make changes to the way you login as the method we currently use is no longer supported.

jlovick commented 10 years ago

@szich Do you want help? i can happily test, and or help in other ways, if you post your current code. Cheers Joe

jlovick commented 9 years ago

@szich Any chance you can share what you have, i dont want to needlessly duplicate your work, but unfortunately need a solution ASAP, I dont want to harry you, as i really appreciate all the work you have done.

johnnygoodman commented 9 years ago

I was wondering why all my calendars went out at once...and now I know. I too thank you for this rocking gem and offer my help.

bfosberry commented 9 years ago

szich commented 9 years ago

I'll do an initial check-in this afternoon, after I clean up the mocks. I have the basic functionality ported over to v3 of their api... but the tests are not all passing and the docs are out of date.

jlovick commented 9 years ago

Thanks Steve, This is a core part of our system so i can give it as much time as we need to get it going.

bfosberry commented 9 years ago

A branch with failing test is much better than a branch that hits a dead endpoint, thanks!

szich commented 9 years ago

I've created a new branch api-v3 and pushed the code so everyone can begin to play with it.

There is still a lot to do before I consider it complete, but it does all of the core functions.

jlovick commented 9 years ago

Thanks!!! I am playing with it now, would you like me to focus in any particular area?

prokopsimek commented 9 years ago

@jlovick How it's look like? Is it possible to create/update/delete events in Google Calendar without problems?

johnnygoodman commented 9 years ago

I was able to auth and create a test event via the api-v3 branch instructions.

I've been unable to get the auth to work without errors in my rails webapp. I also note that as the docs read, it is targeting an installed app and not a webapp.

I have only a basic knowledge of oauth and I think that's the issue. I'll be pairing on it tonight through hackhands.

If successful, I'll make more robust docs and send through a pull request.

prokopsimek commented 9 years ago

+1 :-) Good work!

Dne 18.11.2014 v 22:49 Johnny Goodman napsal(a):

I was able to auth and create a test event via the api-v3 branch instructions.

I've been unable to get the auth to work without errorin my rails webapp. I also note that as the docs read, it is targeting an installed app and not a webapp.

I have only a basic knowledge of oauth and I think that's the issue. I'll be pairing on it tonight through hackhands.

If successful, I'll make more robust docs and send through a pull request.

— Reply to this email directly or view it on GitHub https://github.com/northworld/google_calendar/issues/36#issuecomment-63551733.

jlovick commented 9 years ago

On thing that immediately bites that the "name"/"id" of calendars change. your primary account calendar is likely to stay the same or similar.

so for a primary account like "My High School Combined Calendar" this change to the email address of the user, so something like "my.highschool.calendar@gmail.com"

but sub calendars that might have been named like "My football Calendar" go to something quite different like, o16eui7s31pb2o85v2tc3i72n4@group.calendar.google.com

you can grab a list of your active calendars using the online google api explorer. https://developers.google.com/google-apps/calendar/v3/reference/calendarList/list

i am still working so more info soon,

szich commented 9 years ago

@johnnygoodman we use this in a backend app, and I've written the instructions along those lines. It would be great to include better instructions for folks who want to integrate this with a rails app. So any info you learn abut the process please pass on.

szich commented 9 years ago

I've merged the api-v3 branch to master and released a new gem.

I'm going to close this issue.

Please open up new issues for any problems you find.

johnnygoodman commented 9 years ago

I was able to get this going in rails.

I'm busy tonight but will try to document it and throw that pull request through on Friday.

Short version for those needing it quick:

  1. Run through the script twice. You'll get a one time access code from google as a parameter in the callback url you specify on the first run. The second run tell the script what your request token is. The second code is the money code that you want to store and pass in as a :request_token parameter.
  2. Don't use the documented non http based thing for the :redirect_url. Use a http or https link.
  3. The gem request already ensures you are pasing an :access_type == offline parameter but if doing this raw or weird, know that you'll need this if you wish to receive a "good forever from the app on behalf of the user" request_token.
  4. When setting credentials in the google dev panel, use the Web App option.
bfosberry commented 9 years ago

You guys are awesome! On Nov 20, 2014 4:35 PM, "Johnny Goodman" notifications@github.com wrote:

I was able to get this going in rails.

I'm busy tonight but will try to document it and throw that pull request through on Friday.

Short version for those needing it quick:

1.

Run through the script twice. You'll get a one time access code from google as a parameter in the callback url you specify on the first run. The second run tell the script what your request token is. The second code is the money code that you want to store and pass in as a :request_token parameter. 2.

Don't use the documented non http based thing for the :redirect_url. Use a http or https link. 3.

The gem request already ensures you are pasing an :access_type == offline parameter but if doing this raw or weird, know that you'll need this if you wish to receive a "good forever from the app on behalf of the user" request_token. 4.

When setting credentials in the google dev panel, use the Web App option.

— Reply to this email directly or view it on GitHub https://github.com/northworld/google_calendar/issues/36#issuecomment-63892879 .

jakelodwick commented 9 years ago

@johnnygoodman I was able to regain access thanks to your instructions. Cheers.