Support

That's a conflict between mooTools (the JS framework used by Joomla! itself) and jQuery (the JS framework used by GCalendar). I have used GCalendar myself on a test site and all I can say is that its developer is worse in his JavaScript skills even to yours truly (and I'm no JS hotshot, quite the contrary). What he SHOULD have done is to place jQuery in "noConflict" mode. He didn't, so on any page where you have GCalendar and mooTools is loading as well (pretty much EVERY page on your site) it causes a JS error. Oops! ;)

Pardon my French, but this is a completely BS reply gCalendar's developer gave you :( He should fix his own Javascript. What he asked you to do is impossible and even if you could do that, another software would have a conflict with it and so on and so on. All he needs to do is get off his buttocks, run jQuery in noConflict mode (ideally, confined in a private object) and get done with it. I've been doing that for almost two years and, guess what, I never had any compatibility issues with properly written software.

Well, if you ask me, the best way to integrate a Google calendar on your site is to actually use the IFrame code provided by Google calendar itself. The only downside of this method is that it doesn't support HTTPS, but your site doesn't use HTTPS anyway :)

No, the IFrame method will only work with one calendar, albeit you can place it either in a component or a module position (tip: use the Wrapper component and module). Upcoming events, no it doesn't do that, unless Google itself offers such a feature and I have missed it :)

Jesus Christ, it's one thing not understanding what I said and another thing pretending that you have the absolute truth :s OK, let's try again, with instructions for idiots. If you don't mind copying and pasting between forums, Tim :)

As per the jQuery.noConflict() documentation there are two ways to use jQuery.noConflict:
1. Without passing a parameter, or passing the parameter false, i.e. jQuery.noConflict(false); This is required in order to workaround conflicts with other JavaScript libraries which are also using the $ object, e.g. mooTools. HOWEVER!!! Two BIG "buts":
a. This will ONLY work if the call to noConflict follows the loading of jQuery and BEFORE mooTools is loaded. In any other case, hell may break loose (at least that's what was going on with mooTools 1.11 and 1.2 - I don't know if it's fixed with 1.3).
b. This will work ONLY if NO OTHER copy of jQuery is being loaded on the page.

2. By passing the optional parameter, you can "trap" jQuery in an object for your liking. For example: var myjQ = jQuery.noConflict(true); From that point, all calls to jQuery have to use that object, e.g. instead of jQuery('#foobar') use myjQ('#foobar'). Why do that? Because your own copy of jQuery (this one specific version nonetheless!) is now fully private and isolated not only from other JavaScript frameworks, but also from other copies of jQuery on the same page.

The big catch is, again, that this has to be called BEFORE any other JS framework or another copy of jQuery is loaded. Obviously, using the Joomla! API to link to jQuery's minified file and then use the API to insert a script can not guarantee that, ergo is bound to cause a problem. That's why he's having a problem.

Now, if you're wondering what's the safest way to load jQuery in noConflict mode and, in fact, use a private object, the solution is simple. Always use your local copy of the jQuery minified source file with the noConflict line at its bottom. Otherwise, he can create an in-place replacement of the page source as I was doing in Akeeba Backup 3.0 and 3.1, registering on-the fly a plugin handler for the onAfterRender event. It worked perfectly with both a local copy of jQuery and fetching a copy off Google. If you want the code and can't find an old copy of Akeeba Backup, please let me know and I'll be more than happy to share.