Skip to main content

Displaying Google Calendar Events on a Club Web Site

Well, it was good while it lasted… but now the v2.0 API this is based on has been partially deprecated.  I’ve started the job of migrating – but in the mean time I’ve done a quick fix described here.

In this article I will explain how I present a list of events from Google Calendar in a club web site events page. This follows on from my previous article, Adding Calendar Events to Google Calendar in C#.

I had a few attempts at making this work and encountered a few problems along the way so I’ll mention these as I go along.

Where to Find the Google Calendar Events

Having already loaded the events into the Google Calendar, the first step to displaying them is to find out where to get them from. Thankfully, this is a relatively easy task which you do from your Google Calendar by finding the Calendar Settings Page.

Finding the Google Calendar Settings Dialog

If you loaded the events programmatically as I did then you will already have this URL.

Once you are on the settings page, find the XML data feed icon and click it to see the URL for it. If your calendar is public (as is the one I used) you may as well use the public calendar feed. For private calendars there will be no public feed so you need to select the private feed. Also, if you are going to use it to write back to the calendar use the private one (see previous article).

Select the Public (or Private) XML URL

This URL can be used to retrieve a basic list of events in an XML format called ATOM and looks something like this:

For my purposes I needed to change the URL to retrieve more details and limit the results to future dated events so I replaced /basic with /full?singleevents=true&futureevents=true&orderby=starttime&sortorder=ascending (expand recurring events to multiple single events, only include future dated events, order by event start time, ascending) to get:


  1. There is an excellent reference page to the types of feeds and the parameters you can apply to them at
  2. It is also possible to request a JSON feed instead of XML ATOM format by appending &alt=json to the URL. See

Fetch Calendar Events from Google Calendar

Now that I knew where to get the events from, I needed to actually fetch them so that I could add them to the page. Oh, what fun that was…

First, I took the existing page and converted it to a PHP page. Now, I’m no PHP expert, but since I’m slowly picking it up to work with this Blog (WordPress which is PHP) so it seemed a reasonable choice.

This worked on my local PC (I tested it all under XAMPP) but meant that the page was produced in a different way to all the others (which I generate using an XSLT transform on some XML data and pages). Since I also embed a summary of the next few events in the Home page (a much more messy problem to covert to PHP) I decided that it was not the right solution for this situation.

My next attempt was to use a simple AJAX request to retrieve the data from the URL and render it in the page using JavaScript. This had the advantage that the page framework was generated in the same way as the rest of the site, but the events would be generated in real time from the Google Calendar feed.

I had a look around and found that the XMLHttpRequest object would do the trick. However, this presented two problems in quick succession; limitations on cross-domain requests and the annoying differences of the XMLHttpRequest implementations between different browsers.

The first problem was solved by introducing a PHP file on the server called events-feed.php which fetches the feed from the Google URL and passes it up to the browser on request. My first attempt used file_get_contents() ( to read the entire file into a string. This worked on my XAMPP installation but failed miserably when I uploaded it to the server. Much searching later, I realised that this is considered a security hole and that I should use the “cURL” utility instead.

The feed is returned to the browser with a content mime type of "text/xml".

After struggling with various suggestions to make the XMLHttpRequest object perform AJAX calls in more than one browser at a time, I finally gave up and switched to using jQuery instead. The end result was the following JavaScript which can be added to the <head> element of your web page – but I’ve put into a separate JavaScript file, events.js:

This code makes an AJAX call to retrieve the output of events-feed.php which will be the XML format ATOM feed of future dated events.  It calls the handleError function if anything goes wrong – or the handleCalendar method will be called with the results.

Parse and Extract Event Data

The handleError function is quite simple – here it just displays an alert box – but you could make it do anything you like.

Having fetched the event data the XML needs to be parsed and the events extracted to create the list of events. Note that the Calendar Events are referred to as "entries" in the ATOM feed.

Here, jQuery comes to the rescue again making it easy to extract a collection of event entry objects from the XML feed and iterate through them. Each event is passed into handleEvent function one at a time. This handleEvent function extracts each piece of data about the event and uses them to build the HTML for the page which it appends to the htmlEntries variable.

First, the event title. Notice that the "event" element from the XML object tree is passed in both as a parameter (not used) and as the function context (i.e. "this"). It is then wrapped by jQuery to provide the find() method:

That was nice and easy. Shame it gets a bit harder. To find the start and end times of the event the gd:when element is needed – this has attributes startTime and endTime which are standard XML Dates with optional time (e.g. "2011-10-17T22:15:00.000+01:00").

What’s so hard about that – apart from parsing dates in JavaScript, that is? Well, notice the gd: prefix in the when element. This indicates the XML namespace of the “when” element – but why is it different from the title element above?

A look at the source XML from the events feed gives a clue – the following namespaces are declared in the root element:

Namespace Prefix Definition

The elements I needed to extract include both default Atom elements and some of the gd Google Calendar elements.

It should have been easy, especially with the jQuery library, but instead we have to handle prefixes differently in different browsers. There appear to be two different syntaxes in use and the following code works out which to use as it extract the when element.

See my earlier posting on this for more details.

One final problem with the dates: all day events run from 00:00hrs on the first day to 00:00hrs on the last. This means that the event appears to have an extra day if you present it as received. An all-day event doesn’t have a time associated with it – just the dates.

After that it gets relatively easy so I’ll let the code speak for itself.

Notice that the Location is used to create an automatic Google Maps link when it is rendered. There are also a few extra functions referenced to parse and format the dates – these are all available in the JavaScript from the Thistle Society page.

One final detail worth noting: the content (eventDescription) is returned as plain text – Google Calendar doesn’t support anything else. Some solutions I have seen store escaped HTML in the description – but that is unreadable within the Google Calendar itself and messy to maintain.

I have a more elegant solution (well I think so) using the Wiki Text plugin. So here is the last part of the JavaScript:

Build the Page

The last line of the handleCalendar function (repeated below) inserts the list of events into the body of the page.

A couple more things are required to put it all together in the page.

First a few extra script elements in the page head:

This links in jQuery, the Wiki Text jQuery plugin and finally the code described above.

Finally, somewhere in the page at the point where the events should appear, the following is required:

Sample Code

Update, 3rd June 2014: I have extracted the relevant code from the Thistle Society web site and uploaded it to a GitHub repository at:

A quick way to try this out is to:

  • install XAMPP ( an open source combined Apache HTTP server with PHP and MySQL which I find ideal for developing WordPress web sites),
  • copy the “displaying-google-calendar-events-on-a-club-web-site” folder into the …htdocs folder in your XAMPP installation,
  • open a browser and navigate to http://localhost/displaying-google-calendar-events-on-a-club-web-site (assuming you left the default HTTP port as 80).
  • and then, if you are in Wigan, why not come along to one of the Thistle Society events and try some Scottish Country Dancing?


Well that’s how I went about it – this was one of my first forays into JavaScript and it’s all a bit of a mess. But it works – as you will see if you go to the page I plan to improve the page in the future and I’ve made a few small improvements while I have been writing this.

I hope this helps you add Google Calendar entries into your own pages. Don’t forget, you can also embed the calendar view directly into your page – have a look at some of the other options on the Calendar Settings page.

8 comments on “Displaying Google Calendar Events on a Club Web Site”

  1. Laura Y. says:


    The times are displayed on the web page according to which of the following timezones: a) the timezone of the google calendar or b) the timezone according to how its set on the client computer?


    1. simon says:

      I would imagine the code will display the Google Calendar time – but since the calendar is GMT and everyone I know that uses it is in the UK I haven’t had a chance to confirm that. However, the calendar can be configured in the settings to be in any timezone, and the timezone is included at the end of the date entries if they include a time (for GMT they look like “2012-02-11T17:46:27.000Z”).

      Ah, just found it – have a look at and search for “timezone”. You need to set the current timezone parameter in the query, “ctz”. This will return the results adjusted to the timezone you require.

  2. Pink Frankenkstein says:


    I was looking at your Google Calendar page and was wondering if you have a finished script available for download?


  3. simon says:

    Well, it’s not exactly a “Finished Script” but I’ve extracted the scruffy code I used for the Thistle web site and created a mini sample.

    Get the code from

    If you download XAMPP ( and copy the code into a subdirectory under the XAMPP htdocs directory then start XAMPP and navigate to http://localhost/displaying-google-calendar-events-on-a-club-web-site/ (or whatever URL you set it at) then you will see the results.

  4. John says:

    Thanks so much for posting details on your script. I wanted to let you know I found a problem you might want to be aware of. For your Google calendar, the first start date entry is coming in as:


    But for my calendar, the first entry is coming in as:


    The minus sign instead of a plus sign is making it so the page-events.js file fails on line 74. That is, m is null at that point since the regular expression match didn’t work. If you add a “-” to the regular expression on line 72, next to the “+”, is then works fine.

    1. simon says:

      Thanks – I’ve added it to the code, but not actually tested it with a negative date.

  5. John says:

    Another bug I found… for entries that are part of a series, the end time is not displaying correctly. I fixed it in the page-events.js file on line 191 by adding a last() to the call:

    var endDate = ts_parseDate(jQuery(this).find(nsgd + “when”).last().attr(“endTime”));

    1. simon says:

      Thanks for that: I had just spotted the same bug a week before – the solution I came up with was to identify the last “when” also using:

      var whenElement = $( nsgd + “when:last”, this );

      I just needed to commit the changes to GitHub…

Leave a Reply

Your email address will not be published. Required fields are marked *