Open Graph Actions - Submit failure issue

If you have the Publish to Wall on Login or Register functionality enabled, that's probably the problem. Due to recent changes in Facebook's App Terms of Service, the automatic post to a wall on registration or login is no longer something that should be used. Their new terms require that a user be able to edit any messages posted to their wall, which we don't currently allow.

So, if enabled, disable that feature, test your Open Graph action again (just to make sure they still work), and then re-submit.

Hope that helps explain,
Alex

How is the 2nd site configured? We've never heard of a situation where the FB Activity Log reports the action but it's not recorded by JFBConnect, so that's a unique case we'd need to know more about.

* Are you using a unique FB App ID for the new site?
* Is anything showing up in the JFBConnect Activity Log like an error for the activity, or any information, or are there no rows displayed?
* What kind of action and objects did you create?

Thanks,
Alex

There's no straightforward fix that we know of. It's a unique issue that has never been reported before. If you have a developer that's been making changes, that's definitely the first place to investigate. Our code is very linear in that we perform the Open Graph Action post to Facebook and then immediately write the response we get back from Facebook to the database. There shouldn't be much that can go wrong there.

Keep us posted, and best of luck,
Alex

Buzzy,
If you run the Autotune configuration tool, it will set your app up with the proper migration settings for February through April. New migrations and application settings are released continuously, and the Autotune tool is meant to keep your app up-to-date with Facebook's changing requirements.

As for the Open Graph actions, if it's posting to the Activity Log, that's what's important as that's the users Timeline of activity. From there, it *can* show up on activity feed/profile page/Timeline view that others see based on a lot of social criteria by Facebook.

If you're not seeing the blue popup, that's likely why it's being denied though. You'll need to investigate why that isn't showing.. delete the activity from JFBConnect and the Activity Log on Facebook and then enable the "Display Facebook API errors on Front-end" setting in JFBConnect. Then, check if blue-box appears with an error message or if there are Javascript errors on the page. In either case, you'll need to fix whatever is preventing the posts from happening.

Hope that helps get you started,
Alex

If it shows in the Activity Log on Facebook, that's the important part as it means communication is occurring and the actions are posting. For deleting actions, only the user can delete their own actions from the front-end of the site. We don't offer the ability to delete actions in the admin area on behalf of the user as that's really up to them. To delete the actions, you can create a menu item for the JFBConnect Open Graph Activity and navigate there to delete them.

If the popup isn't showing, that's likely caused by some Javascript or PHP issues with the AJAX requests. If there are any issues with the response, it won't properly show up, but the fact that the action is posting means you're pretty much there.

If you can tell me how to test the action, I can try to go the article page and get it to trigger. Leave the "Display Facebook API Errors on Front-End" setting enabled and I'll let you know what I find.

Finally, no, even if your subscription isn't active, the actions will work. We don't disable functionality at all when a subscription expires.

Thanks,
Alex