Open GoogleCodeExporter opened 9 years ago
This does not help:
https://code.google.com/p/restylegc/issues/detail?id=41
It completely stops my calendare from loading .
Original comment by albernd1...@googlemail.com
on 19 Nov 2014 at 4:34
You are not the only one with this issue. All of mine do the same as yours. A
few others I checked out had the same problem. Google undoubted changed
something. I hope someone on this board can figure it out.
Original comment by yanacek...@gmail.com
on 19 Nov 2014 at 11:27
[deleted comment]
I am also having this issue. Navigating either direction in a month hangs with
a small red box that says "Loading". The calendar no longer shows events.
Google on the 17th shut down the version 2 api:
Quote: "This API is a subject to the Deprecation Policy and will be shutdown on
November 17, 2014. Please use APIv3 instead."
https://developers.google.com/google-apps/calendar/v2/developers_guide_protocol
Original comment by cpierc...@gmail.com
on 21 Nov 2014 at 9:53
Same here. I was actually resolving the v2 API issue when I came to this
solution. All was perfect, until the dreaded "Loading" red box.
Hope someone shows with the cache to solve this one. I'll give it a whirl
myself now that I see this.
Original comment by pr%ehc....@gtempaccount.com
on 21 Nov 2014 at 10:02
My solution: Not use restylegc.
In the iframe code the part where you have in the iframes "src=" delete the
following up to the question mark. Mine looked like:
'/my_path_to/restylegc/restylegc.php?', delete it and put in
"https://www.google.com/calendar/embed?". Should keep your calendar working,
maybe not as pretty as it once were but your customers will have a working
calendar.
Original comment by cpierc...@gmail.com
on 21 Nov 2014 at 10:33
As others have suggested, looks like google deprecated older versions of the
API and with that introduced stricter cross-site scripting rules. If you use
debugging tools in your browser you'll see some "403 Forbidden" responses to
HTTP requests generated by google's calendar js code.
I have a workaround that appears to function ok (as best I can tell).
In source file "restylegc-js.php", comment out line 43.
In other words put two forward slashes at the beginning of the line so that it
looks like this:
//$buffer = preg_replace($pattern, $replacement, $buffer);
This stops restylegc from modifying the domain of URL's in google's source
code. It has the side effect of causing a bunch of "404 not found" errors
during loading of the page which most users will never see. Google's js code
seems to recover elegantly from these missed URL hits without any apparent
issues.
Interested to hear if this works for others. It has to be said that proxying
google's code was always fraught with peril since they are at liberty to make
changes as they see fit. If this fix works for you, recognize that restylegc
is still living on borrowed time.
Original comment by hoscwebm...@gmail.com
on 22 Nov 2014 at 5:52
Regarding my comment #7 and proposed fix... I now realize the flaw in this.
Although the calendar no longer hangs with a red "Loading..." box and will
allow you to change months or views, there's actually no data loaded for any
dates outside the initial range that was specified. So in effect the calendar
looks OK but is not terribly useful if you want people to be able to scroll
ahead or back and actually see events.
Sorry for the false hope. I don't know if there'll be a good workaround for
what google has done this time.
Original comment by hoscwebm...@gmail.com
on 22 Nov 2014 at 6:03
Can anyone recommend a calendar program that is formatted similar to Google?
I'm tired of messing with this just so I don't have to have a pale -blue
calendar. Any recommendations would be appreciated.
Original comment by yanacek...@gmail.com
on 23 Nov 2014 at 10:02
Restylegc seems to be working again - I did not change anything, but I can
forward and backward the months again now.
Original comment by albernd1...@googlemail.com
on 27 Nov 2014 at 2:22
Agreed. It is back to working.
Original comment by yanacek...@gmail.com
on 28 Nov 2014 at 9:24
Original issue reported on code.google.com by
albernd1...@googlemail.com
on 19 Nov 2014 at 3:12