Poco

I was thinking about it, and it now that they are tracking the number of queries, and the data is pretty static, it should be possible to reduce the traffic to their site by caching this on our own servers.

If anyone is concerned about more than 500,000 queries per day on their site (I’m not) then it will make sense to cache the data. Given your question about authentication, we should be able to do some sort of private authentication on the WordPress server to get the data and then surface it however you want. So both problems would be solved by doing the query server side.

It means moving the query in to PHP (I believe there are libraries available) and surfacing it through the wordpress pages using the wordpress Auth and caching the results for some time.

This might be a bit beyond the scope of what I am able to do in the near future. But if someone else wants to take it on, that sounds like a new plugin.

Ya, that is Chaser324 who started this thread 😉

I have a branch now with the first iteration of the fix. It should be good, and I have no reason to believe it doesn’t work, it just needs some settings updates and a bit more testing.

For those willing to try it out, you can download the plugin source directly from the branch found here.

https://plugins.trac.wordpress.org/browser/google-calendar-widget/branches/upgrade_to_v3

Only ko_calendar.js and ko_calendar.php are changed. I don’t know of a good way to download a branch as a zip file, so you have to download the individual files for now.

I have not added a field in the settings for entering your Google API key, so you need to manually replace the string “YOUR API KEY HERE” in ko_calendar.js with your Google API key.

To create a Google API Key, go to https://console.developers.google.com.

1. Create a project for your web site, if you don’t already have one.
2. Select “APIs” under “APIs and Auth” (left menu)
3. Enable “Calendar API”.
4. Go to the “Credentials” page.
5. Click on “Create New Key”.
6. Select “Browser Key”.
7. Add your URL to the referrer box or leave it blank to allow any referrer. I would leave it blank for testing and once you have it working change the rules later.
8. After you create the key you will be shown the full key.
9. Copy that key into ko_calendar.js by replacing “YOUR API KEY HERE”.
10. Wait a few minutes. It seems that it can take a minute or two before the key is functional on their system.

The Calendar “URL”s are now IDs so you should edit your widget settings and change the URL to an ID. The IDs look like an email address.

Give it a go and let me know if you have any trouble.

I am working on it now. No ETA yet but I will try to get it working as soon as possible.

I’m not sure I understand. It has been a while since I’ve worked on it, but I don’t recall any “view details”. My guess, however, is that even if that was there, it won’t show the same thing for other users as it does for you, since it is your calendar.

The best way to check what other people will see is to open an private browsing window (or incognito or whatever it is called in your browser) and view your page there. This will show you what people who are not logged into your Google Account will see.

That is a different calendar. It is this one without the prefix “games”.

http://www.google.com/calendar/feeds/calendar%40dbifgs.org/public/full

Good suggestion. I would be happy to consider integrating the changes if someone made it, otherwise it will have to wait until I have time.

To add more calendars would require changing the code in the plugin. If you look in ko_calendar.php for “url3” you will see where the URLs are declared and duplicated. You could either fix this to come up with a more generic system that supports any number of calendars or add to the existing urls by duplicating everywhere you find “url3” and make a “url4” and “url5”.

What I have started to do where I need multiple calendars in one is that I merge them into one new calendar in Google Calendar. If you invite a calendar “address” (Look for Calendar Address in the settings) to an event as a guest, the event will be shared in both calendars. If it is edited in one calendar it will be updated in all the invited calendars.

I have created a central calendar for my club and all events are created there. Then each individual calendar that wants to see that event is invited as a guest. This is very flexible as it means that I only have to share and display one calendar address for any individual calendar, but each one displays exactly what the users need from it.