What is the proper google ID?

The proper google ID is the ID of your agenda (found with parameters / details) :
– [email protected] (or the email adress you use as login) if it is your own private agenda linked to your account (it is not possible to delete it)
– [email protected] if it is another agenda your created on your account

In your case, it is [email protected]

Thanks Gremie! I gave that a try initially as well… still the wheel of death. ??
The API is set to the new protocol, but still no joy. Any other ideas folks?

@seandulany, Do you have a link you can post so that I can help you track it down?

If not, check the debug console in your browser for errors (I will be posting an update which will include more information for errors) and search your network traffic for “batch” to see if the response has any errors.

Hello Poco,
Link to the page in question is:
Here.
Thanks for your attention. Appreciated greatly!

I have discovered two problem.

1. The link you sent was https and Google doesn’t like mixing http with https.

Below is the output of the browser console. This shows that it won’t load the Google client.js because it is http instead of https. This can probably be solved by changing the “https://apis.google.com/js/client.js?onload=ko_calendar_google_init” to “//apis.google.com/js/client.js?onload=ko_calendar_google_init”. Removing the protocol will default to the same protocol as the parent page. Please let me know if this works and I will update the plugin.

This is the output from the console (you can see it yourself in most browsers by opening the debugger or dev console (F12 in Chrome).

Mixed Content: The page at 'https://runsra.org/training-programs/' was loaded over HTTPS, but requested an insecure image 'https://runsupersunday.org/wp-content/uploads/2013/10/Reg_now.jpg'. This content should also be served over HTTPS.
runsra.org/:1 Mixed Content: The page at 'https://runsra.org/training-programs/' was loaded over HTTPS, but requested an insecure image 'https://runsupersunday.org/wp-content/uploads/2013/10/Spacer.jpg'. This content should also be served over HTTPS.
runsra.org/:1 Mixed Content: The page at 'https://runsra.org/training-programs/' was loaded over HTTPS, but requested an insecure image 'https://runsupersunday.org/wp-content/uploads/2013/10/10k-Am-I-registered.jpg'. This content should also be served over HTTPS.
runsra.org/:1 Mixed Content: The page at 'https://runsra.org/training-programs/' was loaded over HTTPS, but requested an insecure resource 'https://apis.google.com/js/client.js?onload=ko_calendar_google_init&ver=4.0.1'. This request has been blocked; the content must be served over HTTPS.
(index):528 Mixed Content: The page at 'https://runsra.org/training-programs/' was loaded over HTTPS, but requested an insecure image 'https://runsupersunday.org/wp-content/uploads/2013/10/Reg_now.jpg'. This content should also be served over HTTPS.
(index):529 Mixed Content: The page at 'https://runsra.org/training-programs/' was loaded over HTTPS, but requested an insecure image 'https://runsupersunday.org/wp-content/uploads/2013/10/Spacer.jpg'. This content should also be served over HTTPS.
(index):530 Mixed Content: The page at 'https://runsra.org/training-programs/' was loaded over HTTPS, but requested an insecure image 'https://runsupersunday.org/wp-content/uploads/2013/10/10k-Am-I-registered.jpg'. This content should also be served over HTTPS.
(index):1 Mixed Content: The page at 'https://runsra.org/training-programs/' was loaded over HTTPS, but requested an insecure script 'https://apis.google.com/js/client.js?onload=ko_calendar_google_init&ver=4.0.1'. This request has been blocked; the content must be served over HTTPS.
et-ptemplates-frontend.js?ver=1.1:109 Uncaught TypeError: undefined is not a function

2. When I switch to using the http version of your web page there are errors downloading the calendars (visible in the browser debugger looking at the response from the content.googleapis.com/batch query. Please see the plugin FAQ for the steps to get a valid key.

--batch_oHCmwhF2u1A_AAgSsYORaMU
Content-Type: application/http
Content-ID: <response-514302532>

HTTP/1.1 403 Forbidden
Content-Type: application/json; charset=UTF-8
Date: Wed, 26 Nov 2014 07:27:46 GMT
Expires: Wed, 26 Nov 2014 07:27:46 GMT
Cache-Control: private, max-age=0
Content-Length: 744

{
 "error": {
  "errors": [
   {
    "domain": "usageLimits",
    "reason": "accessNotConfigured",
    "message": "Access Not Configured. The API is not enabled for your project, or there is a per-IP or per-Referer restriction configured on your API key and the request does not match these restrictions. Please use the Google Developers Console to update your configuration.",
    "extendedHelp": "https://console.developers.google.com"
   }
  ],
  "code": 403,
  "message": "Access Not Configured. The API is not enabled for your project, or there is a per-IP or per-Referer restriction configured on your API key and the request does not match these restrictions. Please use the Google Developers Console to update your configuration."
 }
}

--batch_oHCmwhF2u1A_AAgSsYORaMU--

Poco,
The removal of the http: did indeed do the trick. The widget is back up and working as it should.
Thank you for your attention!

We can mark this one as RESOLVED!