Utp,
I'm not sure what's wrong from that message either. Can you let me know:
* Have you been able to test, using the test user account, the posting of actions to the test user's Timeline?
* When you log in with the Test User account you created for your Facebook Application, is there any indication that the user is logged in? Mainly, are you using the SCLogin module or some other module that would say "Welcome Mark" or another type of notification that the user is logged into the site?
Those are the questions that Facebook is asking. If you haven't created a Test User for your Facebook App, you'll need to create one. If you can't see the action posting to the Test User's activity log from multiple pages, then something is wrong and we can help. If you aren't using something to note that the user is logged in vs not logged in, you'll need to add it.
That last point about showing the user is logged in is something we've never seen a denial for before. These are not our restrictions that we put on the actions, they are Facebook's, and unfortunately, they do change their requirements. We have many user's getting actions approved every day. JFBConnect does support what Facebook requires, but we can't test each action for our users.
If you have any questions, let us know. If you aren't able to post actions to your Test User timeline, that's the thing we can help with most because that would be a direct result of a JFBConnect configuration problem. The other issues are simply hurdles that Facebook is making you jump through. When we we released in November, there were less hurdles. Every few weeks, it seems they add more, and there's not much we can do about that other than provide assistance and clarity where possible.
Hope that helps explain. Definitely let us know if you need assistance from us and what specifically we can help you do.
Thanks,
Alex