views:

174

answers:

3

Hi,

UPDATE: this has just started happening again, would appreciate any help.

I am using server fbml to render an Invite Friends iframe and it was working fine up until two days ago. Basically, after submitting the form, a java action should be invoked where I get all the id's of the user's invited.

However, I now notice that an "invite by email" popup is showing up and, most importantly, my java action isn't being hit at all. When I inspect the form in firebug, I notice that the action is always empty (though all other parameters are preserved correctly).

I've tried setting email_invite=false on the multi-friend-selctor but to no avail.

My code looks like the following:

    <fb:fbml> 
        <fb:request-form action="http://localhost:8080/myAction.do?method=someAction" method="POST" invite="false" target="_top" type="invite" content="CONTENT_GOES_HERE" > 
            <fb:multi-friend-selector showborder="false" actiontext="Invite your friends to use our app." target="_top" email_invite="false"> 
        </fb:request-form> 
    </fb:fbml>

</script>

Any help would be greatly appreciated on this.

UPDATE: this has just started happening again, would appreciate any help.

Thanks, gearoid.

+1  A: 

Facebook have recently added an extra step into the multi-friend selector process, which is what you're seeing. There isn't, as far as I know, any way to stop this from appearing.

However, you should still be getting the result of the selector sent to you once the user navigates away from the "invite by email" popup.

Facebook's latest update can be seen in this status post.

Cyphus
Thanks but it seems as though the action attribute in the form is never getting populated regardless of what I enter. If I use firebug to enter in my action after page load then the action gets hit correctly. Any idea why this is happening?
Gearóid
A: 

Is there a solution to this? I am seeing the same problem

Matraax Coe
It turned out to be my mistake. I had an incorrect appId set in the fb-root javascript. So double check your appId is what I'd say to you!
Gearóid
A: 

I had an incorrect appId set in the fb-root javascript. This caused the error.

Gearóid