Hi Jerry,

   Shindig has a bug tracker available here:  
https://issues.apache.org/jira/browse/SHINDIG
where you should report such issues.

Thanks,
~Arne



On Dec 27 2007, 1:41 pm, jerry <[EMAIL PROTECTED]> wrote:
> I am running into a problem using Shindig that I think may be able to
> be addressed here. I have installed Shindig on my dev box and have
> gotten simple gadgets to work and am very excited by the possibilities
> of an open source/open social container like this.
>
> Now for the problem:
> When I add a call to _IG_RegisterOnloadHandler to my gadget I get the
> following javascript error through firebug:
>
> missing ) in parenthetical
>
> [Break on this error] (uiv="Content-Type" content="text/html;
> charset=ISO-8859-1"/>\n
>
> 6gZqwg2JpuM.js (line 84)
>
> This may look like a silly syntax error on my part, but when I paste
> the same xml into the Google Gadgets Editor it works just fine. Also,
> I have a sandbox on Orkut so I uploaded my gadget's xml file 
> tohttp://jerry-google.googlecode.com/svn/trunk/gadgets/xml/salon.xmland
> added it as an application to Orkut and it also works just fine.
>
> It seems to me the syntax error is 
> inhttp://gmodules.com/ig/extern_js/f/CgJlbhICdXMrMAE4ACw/6gZqwg2JpuM.js
> and I'm not entirely sure where to file the bug. Any suggestions?
>
> Oh, and the reason I have CoreJsFeature in the subject line is that
> this is the class in Shindig that has the url to 6gZqwg2JpuM.js
> hardcoded into it. I will happily fix this class and submit a patch if
> someone will point me to a javascript file from gmodules that works.
>
> Thanks in advance for any help.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"OpenSocial API Definition" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/opensocial-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to