hi,
Now its different i am getting 502 errors

not even able to open sandbox url .
please help
Thanks
Dinesh

On Jan 24, 2008 1:10 PM, Marc Wessely <[EMAIL PROTECTED]> wrote:
> Hello Arne,
>
> I am still getting 404 error, when i have added setprefs and tabs library
> but i need that for design of the gadget.
> I moved now to hi5 container but would prefer continuing development on
> orkut since hi5 is missing some features i need.
>
> i think also others realized that all gadget api libraries dont work at the
> moment.
>
> marc.
>
> 2008/1/24, Arne Roomann-Kurrik (Google) < [EMAIL PROTECTED]>:
>
> >
> > Hey, sorry about the delay in responding to this thread!  This push
> > was the initial migration to have Orkut running on the Shindig project
> > and there were a few issues introduced that were not expected.  The
> > team has been quite busy locking these down and it looks like things
> > have stabilized a bit.
> >
> > RE: makeRequest() padding - The sandbox has been pushed again with
> > fixes to the makeRequest() function calls that don't require you to
> > pad return data.  Currently, there's a known issue when requesting
> > FEED type content, but if your server is returning JSON, then you
> > should be able to get data back to your applications now.
> >
> > RE: Sandbox 404s and donut errors - The recent push should have
> > addressed some of these issues, except for a known bug with type=url
> > gadgets.   If you are getting consistent 404s/no donut errors (not
> > related to type=url gadgets), please post here again.
> >
> > RE: Changes from 0.5 to 0.6 - We've updated the Orkut Developer's
> > Guide to show you how things have changed.  Please check
> > http://code.google.com/apis/orkut/docs/orkutdevguide.html for this
> > information.  Post new threads about any code that you can't get
> > working under the new API and we'll try to help you out!
> >
> > ~Arne
> >
> >
> > On Jan 22, 12:58 pm, TylerKeen <[EMAIL PROTECTED]> wrote:
> > > Hello?....... Google? Feel free to jump in here anytime.
> > >
> > > On Jan 22, 1:33 am, Rajat < [EMAIL PROTECTED]> wrote:
> > >
> > > > I give up...
> > >
> > > > even if I try to send 27 chars before my actual data which clears up
> > > > the previous errors it still is expecting data in a very specific
> > > > format which is no where documented in the specs. From the following
> > > > code it seems that it is expecting json in the format of
> > > > {original_url: {body: 'actual data'} }
> > > > which seems insane. Before going to make changes to my app I would
> > > > request someone from google to confirm whether this is a bug which
> > > > will be corrected or is it the way we will have to implement our
> > > > apps ???
> > >
> > > > And for a change it would be nice to get a official response to this.
> > >
> > > > 586 var data = eval("(" + txt + ")");
> > > > 587 data = data[url];
> > > > 588 var resp = {
> > > > 589 text: data.body,
> > > > 590 errors: []
> > > > 591 };
> > >
> > > > Regards,
> > > > Rajat
> > > >  www.toostep.com
> > >
> > > > On Jan 21, 3:36 pm, Rajat <[EMAIL PROTECTED] > wrote:
> > >
> > > > > This is still a problem... I have changed my widget to use
> > > > > opensocial.makeRequest even then I see that the JSON object that I
> > > > > return is causing javascript error at the  container as I have
> > > > > mentioned earlier... Also after changing my code to use
> > > > > opensocial.makeRequest instead of _IG_FetchContent it is now caching
> > > > > the request and no matter even if I use bpc=1 it is still using the
> > > > > cache.
> > >
> > > > > Is anyone else facing such problems or is it me doing something
> > > > > stupid? Has anyone found any alternative to get JSON strings to be
> > > > > sent to the widget code?
> > >
> > > > > Regards,
> > > > > Rajat
> > > > >  www.toostep.com
> > >
> > > > > On Jan 17, 7:30 pm, Rajat < [EMAIL PROTECTED]> wrote:
> > >
> > > > > > Also adding <Require feature="analytics"/> is causing no donut for
> you
> > > > > > page that I was getting earlier. Is analytics no longer supported
> in
> > > > > > OS?
> > >
> > > > > > On Jan 17, 7:28 pm, Rajat <[EMAIL PROTECTED]> wrote:
> > >
> > > > > > > I think I have found the problem that is causing my widget to
> fail...
> > >
> > > > > > > following seems to be offending code and it is causing my JSON
> string
> > > > > > > to give error...
> > >
> > > > > > > txt = txt.substr(UNPARSEABLE_CRUFT.length);
> > > > > > > // TODO: safe JSON parser.
> > > > > > > var data = eval("(" + txt + ")");
> > >
> > > > > > > Can this be corrected???
> > >
> > > > > > > On Jan 17, 12:41 pm, Rajat < [EMAIL PROTECTED]> wrote:
> > >
> > > > > > > > Hi,
> > >
> > > > > > > > Is this push done? I can;t seem to add my application with
> either
> > > > > > > > <Require feature="opensocial-0.6"/> or <Require
> > > > > > > > feature="opensocial-0.5"/>
> > > > > > > > It just goes to no donut page.
> > > > > > > > My earlier added app which was running on 0.5 gives me 404 in
> canvas
> > > > > > > > mode.
> > > > > > > > Can someone please check and let me know.
> > >
> > > > > > > > Regards,
> > > > > > > > Rajatwww.toostep.com
> > >
> > > > > > > > On Jan 17, 2:50 am, "Arne Roomann-Kurrik (Google)"
> > >
> > > > > > > > <[EMAIL PROTECTED]> wrote:
> > > > > > > > > As originally announced in this thread:
> http://groups.google.com/group/opensocial-orkut/browse_thread/thread/...
> > > > > > > > > the Orkut sandbox is going to be updated with the 0.6 API
> today.
> > >
> > > > > > > > > Please respond to this thread with any discussion or
> problems related
> > > > > > > > > to this push.
> > >
> > > > > > > > > Thanks!
> > > > > > > > > ~Arne
> >
> >
> >
>
>
>
>  >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Orkut Discussion" group.
To post to this group, send email to opensocial-orkut@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/opensocial-orkut?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to