Poco

Do you have a link I can test?

@sonolento. Your calendar ID is still wrong.

Right now it is this…
https://www.google.com/calendar/feeds/nahoracompt%40gmail.com

it should be this…
[email protected]

@Hendison Scott
You have a similar problem. You must set the calendar ID in the widget settings to just the email id, not the full url.

Looking at your page, you are requesting with an ID of this

https://www.google.com/calendar/feeds/eastportlandchmbr74%40gmail.com/public/basic

It should be this
[email protected]

@gremie, thanks for replying so quickly. You beat me to it by 16 minutes.

I’m going to need more than that. What is the full dump of your console from when you load the page? Can you also look include the details of the failed requests?

Is there a way that you can make the page public temporarily so that I can look at it directly?

Without a link or JavaScript console output there isn’t much I can do to help. Please provide more information.

Unfortunately, it won’t work in some browsers by default if you open a local HTML page. It requires CORS support (so that it can download files from a different domain) and browsers like chrome block cross domain access from a local HTML file by default. Search for “allow cors support from local file on <your browser here>” to find out how to enable it.

Of that doesn’t work then post it to a server. If that doesn’t work then post the link here so that I can look at it.

Do you have a link or error messages from the JavaScript console?

I didn’t even realise that you could add more calendars to the old query to get more that one at a time… Interesting.

I will look into what it will take to do something similar with the current version.

I will reply back tonight or tomorrow.

I have a theory, but I will need the calendar id or link to look into it.

I can take a look. What is the url of the web page or your calendar id?

I would like to debug it but I will need more details.

The plugin has been updated to version 1.4.0 which has been upgraded to using Calendar API V3. Please update and follow the upgrade instructions. I am going to close this topic as resolved, but if you have any other issues, please open a new one.

Since this update is now live I am going to close this topic as resolved. Please start a new topic for any new issues that come up.

@gremie, The authenticated api is only going to help you if you do it on the the server since your will want to hide the private data. If you do something like that on the client then it will authenticate each user using their own Google account and give them access to calendars that you have explicitly shared with each user. That probably isn’t what you want.

Alright, I’ve updated the settings and published version 1.4.0. I have also updated the readme settings screen with detailed instructions on how to get your Google API Key and update the calendar IDs.

Everyone please let me know if it is or is not working.

There is another thread about this problem. I have a fix in a branch that you can try while I prepare it for going live.

https://www.ads-software.com/support/topic/403-forbidden-on-cal-url-deprecated-api?replies=15