Changing the hash on the iframe where your application is running clears a security token that the application uses to make calls back to orkut. By changing the hash, you eliminate the security token and subsequent requests fail.
The team is looking for ways to work around this, but for the time being, you should not change the hash value on your iframe or else the opensocial calls will start to fail. ~Arne On Sat, Mar 29, 2008 at 12:24 AM, Neil Sheth <[EMAIL PROTECTED]> wrote: > > Ok, turns out, I get an error from my newDataRequest. Removing this > line causes the newDataRequest to succeed. Still at a bit of a loss > as to how one affects the other . . . > > On Fri, Mar 28, 2008 at 11:27 PM, nsheth <[EMAIL PROTECTED]> wrote: > > Seems odd that this wouldn't work, but after going through my code > > line by line, it seems like this was the offending call: > > > > window.location.hash='#myanchor'; > > > > I was getting odd js errors down the line, but removing this line > > fixed things. Any thoughts? A bit stumped . . . > > > > > > -- OpenSocial IRC - irc://irc.freenode.net/opensocial --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Orkut Developer Forum" 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 -~----------~----~----~----~------~----~------~--~---
