Update Progress
Permalink Browser Info Environment
Just wanted to provide a quick update on progress.
As I mentioned to a couple people, this issue came up right as I was moving my family to a new home. The move is now done, though there is still a lot to do. Combined with that, I have a day job that unfortunately has to come first.
That said, I have done some investigation into the new methods that Google provides to access its data. There are 4 different methods that I am investigating to determine which one is the least complex to configure by users of the addon. Regardless, the update to the addon will require more configuration than previously but I will provide as detailed instructions as I can.
I am aiming to have a rudimentary version with some manual configuration up first (exact eta tbd), hopefully within a week. After that, I will be rebuilding the addon as the new method for accessing Google requires quite a different addon setup.
Thanks and apologies again for the inconvenience that Google change has caused!
As I mentioned to a couple people, this issue came up right as I was moving my family to a new home. The move is now done, though there is still a lot to do. Combined with that, I have a day job that unfortunately has to come first.
That said, I have done some investigation into the new methods that Google provides to access its data. There are 4 different methods that I am investigating to determine which one is the least complex to configure by users of the addon. Regardless, the update to the addon will require more configuration than previously but I will provide as detailed instructions as I can.
I am aiming to have a rudimentary version with some manual configuration up first (exact eta tbd), hopefully within a week. After that, I will be rebuilding the addon as the new method for accessing Google requires quite a different addon setup.
Thanks and apologies again for the inconvenience that Google change has caused!
| Type: | Discussion |
|---|---|
| Status: | In Progress |
Hey there, Do you have an news on the update release date? I have a customer who is using your add-on in their site and are concerned that the GCalendar Viewer functionality isn't working currently.
I need to make sure the problem is related to the changes Google has made and not something else. Nothing has changed on the site and the calendars have event in them but it is simply blank currently.
Would you be able to advise, or better still take a quick look at their site to ensure this issue is down to the issues google's changes have caused.
I'm more than happy to test any new updates if that helps.
I need to make sure the problem is related to the changes Google has made and not something else. Nothing has changed on the site and the calendars have event in them but it is simply blank currently.
Would you be able to advise, or better still take a quick look at their site to ensure this issue is down to the issues google's changes have caused.
I'm more than happy to test any new updates if that helps.
Yes, please can you let us know the latest. We are very concerned about the fact that we haven't been able to use a calendar on our website for nearly two months.
First, thanks for everyone's patience, I know the wait has been a pain (for me as well)!
The good news: I have successfully updated the addon! You can see it working here:http://www.fbcwaterloo.com/ (the skin is custom).
Unfortunately I haven't had time to write polished instructions on how to configure Google to work with the new addon ... it's not quite as simple as it used to be.
To access data from Google, you now need to configure access using their Developer Console (https://console.developers.google.com). The gist of setting it up is as follows:
1. Create a new project at the above Developer Console url using the Google Account that owns your primary Calendar Feed
2. In the new project, turn on the Calendar API under 'APIs & auth' -> 'APIs'
3. In the new project, create a new 'Web Application' OAuth Client ID under 'APIs & auth' -> 'Credentials'
- IMPORTANT: for the 'AUTHORIZED REDIRECT URIS' option while creating a new Client ID, use 'http://www.yourdomain.com/packages/g_calendar_viewer/config.php', where 'www.yourdomain.com' is the domain name where you have installed a copy of GCalendarViewer.
- It is not necessary to include any values for 'AUTHORIZED JAVASCRIPT ORIGINS', though you can include your root website address.
4. In Google Calendar, share your Google Accounts' primary calendar with the Google generated 'EMAIL ADDRESS' (associated with the new Client ID you just created) using a permission setting of 'See all event details'. For example, my Google account is 'dean@whillier.com' and my primary calendar's ID is 'dean@whillier.com'. All secondary calendars ID's consist of random alpha-numeric values followed by '@group.calendar.google.com' ... or something similar.
- a benefit of sharing your Client ID's 'EMAIL ADDRESS' with your primary Google Calendar is that you should be able to choose from all of the calendars you have access to in GCalendar Viewer. No more copy-pasting calendar URL's.
5. Make sure you have installed the updated GCalendar Viewer.
6. Using the Google-generated 'CLIENT ID' and 'CLIENT SECRET' of the new Client ID you just created, visithttp://www.yourdomain.com/packages/g_calendar_viewer/config.php,... where 'www.yourdomain.com' is the domain name where you have installed your copy of GCalendarViewer. This URL should help you complete the GCalendar Viewer configuration.
- IMPORTANT: This URL must be the same URL you configured above for the 'AUTHORIZED REDIRECT URIS' when creating your new Client ID!
7. Delete the 'config.php' file from '/packages/g_calendar_viewer/' when done for security purposes.
- I eventually plan on integrating the configuration steps into the Dashboard in C5.
I am not posting the new addon for general access just yet as I would like to test it for a bit first. I am however attaching it to this post so that anyone interested can give it a go. If you are interested and do install it, please let me know if you come across any challenges!
Thanks,
Dean.
The good news: I have successfully updated the addon! You can see it working here:http://www.fbcwaterloo.com/ (the skin is custom).
Unfortunately I haven't had time to write polished instructions on how to configure Google to work with the new addon ... it's not quite as simple as it used to be.
To access data from Google, you now need to configure access using their Developer Console (https://console.developers.google.com). The gist of setting it up is as follows:
1. Create a new project at the above Developer Console url using the Google Account that owns your primary Calendar Feed
2. In the new project, turn on the Calendar API under 'APIs & auth' -> 'APIs'
3. In the new project, create a new 'Web Application' OAuth Client ID under 'APIs & auth' -> 'Credentials'
- IMPORTANT: for the 'AUTHORIZED REDIRECT URIS' option while creating a new Client ID, use 'http://www.yourdomain.com/packages/g_calendar_viewer/config.php', where 'www.yourdomain.com' is the domain name where you have installed a copy of GCalendarViewer.
- It is not necessary to include any values for 'AUTHORIZED JAVASCRIPT ORIGINS', though you can include your root website address.
4. In Google Calendar, share your Google Accounts' primary calendar with the Google generated 'EMAIL ADDRESS' (associated with the new Client ID you just created) using a permission setting of 'See all event details'. For example, my Google account is 'dean@whillier.com' and my primary calendar's ID is 'dean@whillier.com'. All secondary calendars ID's consist of random alpha-numeric values followed by '@group.calendar.google.com' ... or something similar.
- a benefit of sharing your Client ID's 'EMAIL ADDRESS' with your primary Google Calendar is that you should be able to choose from all of the calendars you have access to in GCalendar Viewer. No more copy-pasting calendar URL's.
5. Make sure you have installed the updated GCalendar Viewer.
6. Using the Google-generated 'CLIENT ID' and 'CLIENT SECRET' of the new Client ID you just created, visithttp://www.yourdomain.com/packages/g_calendar_viewer/config.php,... where 'www.yourdomain.com' is the domain name where you have installed your copy of GCalendarViewer. This URL should help you complete the GCalendar Viewer configuration.
- IMPORTANT: This URL must be the same URL you configured above for the 'AUTHORIZED REDIRECT URIS' when creating your new Client ID!
7. Delete the 'config.php' file from '/packages/g_calendar_viewer/' when done for security purposes.
- I eventually plan on integrating the configuration steps into the Dashboard in C5.
I am not posting the new addon for general access just yet as I would like to test it for a bit first. I am however attaching it to this post so that anyone interested can give it a go. If you are interested and do install it, please let me know if you come across any challenges!
Thanks,
Dean.
Hello,
Thank you for the detailed instructions. The installation worked!
Right now i have the problem that only events in the current month are showed.
Can this be changed?
Thank you for the detailed instructions. The installation worked!
Right now i have the problem that only events in the current month are showed.
Can this be changed?
I will now work on integrating the new access code into the gcalendarviewer. Hope to have something up in the next couple days.
Once the update is released, anyone wanting to use the addon will need to run through a few steps to set up access tokens with Google to allow the addon to access your data. I will provide instructions on doing so.