Hi Brad,

Not sure if we're talking about the same thing (I wasn't clicking a reload link, just hitting the reload button on my browser), but it sounds like the root cause of what we're both seeing is the same. I'll keep checking back for any updates but I'll also poke around and see if I can figure it out.

Thanks again!

This worked great at first, but after a few reloads it seems to be hanging up (only displays "Loading GMgcal..."). Could that be related to the caching functionality? Can the cache be cleared/expired?

Thanks for a great script!

I already found that my previous post's "fix" for the date offset does not work around the clock, so please DO NOT implement that gmtOffset fix. Disregard my previous post entirely.

Thanks rich5813! :)

I also found a quick fix to meno like-bugmenot's problem with the full-day events being displayed with a date on day after the actual event. The problem (as far I've been able to deduce) comes from the getTimezoneOffset() function. That function seems to return an absolute value, so those in the GMT -# timezones get a positive value. My one-line fix was to change a line in the parseDate(TS,debug) function.

Original line:
parsed['gmtOffset'] = date.getTimezoneOffset();

New line:
parsed['gmtOffset'] = (date.getHours() - date.getUTCHours());

This has gone through some very minimal testing, but it's behaving pretty well for me. I'll post back if I find any bugs.

Hope that helps!

I fixed my copy of the script with a very small change.

Line 219 currently reads:
bmkURL = responseDetails.responseText.match(/\.\/url[^ \n\r"]+(?=.*id=bkmk_href)/);

My change was to add a quotation mark after the 'id=' portion. In other words:

bmkURL = responseDetails.responseText.match(/\.\/url[^ \n\r"]+(?=.*id="bkmk_href)/);

Give that a shot and see if that helps. The script is working great for me now.