Hi Shishir,

root.friendPicUrl doesn't work.  But in another application we have used
${root.content.root.friendPicUrl}, which absolutely works fine.  But the
error here seems to be for the url, and the app got rejected.

In our testing in sandbox, we are unable to get this 404 error at all.

"HTTP Error: HTTP/1.0 404 Not Found
http://www.sandbox.orkut.gmodules.com/gadgets/proxy?refresh=86400&container=orkut-sandbox&url=http://fbapps.postalz.com/meethabomb/orkut/null&gadget=http://fbapps.postalz.com/meethabomb/orkut/meethabomb.xml&fp=45508&refresh=86400&sanitize=1&rewriteMime=image/*
"

Is this some container related issue?

Regards,
Rajeev

On Fri, Jun 5, 2009 at 12:56 PM, Shishir Birmiwal (Google) <
[email protected]> wrote:

>
> The culprit is this "<img src = ${root.content.root.friendPicUrl}>"
> Last I remember, shindig only supported 1 level of nesting (ie.
> root.friendPicUrl).
>
> Cheers,
> Shishir
>
>
> On May 29, 6:17 pm, Dhaval Pancholi <[email protected]> wrote:
> > Hi i had given my application xml to orkut for approval but it was
> > rejected saying it had 404 errors our testing team has detected no
> > broken links in the application.
> > IN firebug also i cannot see any 404 errorrs .
> > My application xml url ishttp://
> fbapps.postalz.com/meethabomb/orkut/meethabomb.xml
> >
> > The url send by orkut team is
> >
> > http://www.sandbox.orkut.gmodules.com/gadgets/proxy?refresh=86400&con...
> >
> > here in the url it sayshttp://fbapps.postalz.com/meethabomb/orkut/null
> > but i could not find any link pointing to this url. Can u please give
> > me in detail description to the broken link error.
> >
>


-- 
Regards,
Rajeev

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Orkut Developer Forum" 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-orkut?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to