I have just had my first go at setting up the new Open Graph Actions, following the information on this website. I submitted to Facebook and got the following reply so wondering if anyone knows what this means / what I didn't do correctly ?
"Your code is currently configured to publish a stream story. You must change your code so that when the test user triggers the action it produces an open graph story. "
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,
Have tried to get open graph working on a second site and while I have managed to get some activity to the activity logs on FB, the activity log in the back-end refuses to display.
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?
Tried 2 dedicated apps, but nothing shows up in Activity Log.
I have checked everything and cross referenced against the other site.
Suspect it is something my coder colleague has done. (He's not involved with the site that works)
Had hoped there was a straightforward fix, but will take matters up with him first.
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,
Ok so did that (maybe that should be mentioned in the tutorials) and got one step further - Facebook report it doesn't work since it doesn't post to the timeline of the test user. What I see is that it is recorded in the log in Joomla extension and also it does show on the Activity log of the test user in Facebook, however it does not appear on the test users timeline / profile page. I notice also that I never get any pop up as mentioned in the configuration guide.
What I also have now in addition is another message from Facebook that I need to update my app for the 'February 2013 Breaking Changes' which I have no idea what that means?
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.
Hope that helps get you started,
So couldn't see how to delete activity from JFBConnect app (in the OpenGraph log page it seems you can only delete entries that show as errors, not entries that show as successful) Anyway deleted the test user and created one fresh, when I log into my website with this user using the Login with Facebook button that works (and I get a popup window telling me it is logging in). When I perform activity on the my website I see it being logged as successful in the JFBConnect log and also as showing up on the test users Activity Log in Facebook, yet it never seems to show in their time line and I never get any pop up box (with or without errors) even with the "Display Facebook API errors on Front-end" option set.
Must admit I am beginning to think I will give up on this, it doesn't seem as straightforward as you imply on your website! My subscription recently ran out for this (JFBConnect) so could that be why it doesn't work?
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 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.
Well, perhaps rather foolishly I decided to delete everything and start again. Having done that I find now that I still don't get the pop up on the sites web pages. The action is recorded in the JFBC log page but now nothing is showing on the test users log activity on Facebook.
Here is info for testing :
Log into Facebook with test account
Go to www.punya.co.uk and log in using the Login with Facebook button on the left hand side
Click on the Menu item 'Therapies' then 'Reiki'
This should trigger the posting to Facebook after 15 seconds
Open Graph Test User
email [email protected]
Uncaught TypeError: Object [object Object] has no method 'fade'
However, if I load your page with a different template by adding ?template=atomic to the URL, the popup works as expected. I'm not sure what's causing the problem, but I'd recommend either disabling modules and plugins to see which one is interfering with the Mootools library. Hopefully, you can narrow it down to one other specific extension and then we can help you figure out where the conflict is coming from.
Hope that helps get you started,
OK fixed the web site issue and now I do get the pop up on the site web page but it still does not show up in the Facebook activity log even though I get everything ok on the my web site (pop up shows, the user account has the activity listed and it shows in the admin log on the web site) ?
Please check out the thread below.
http://www.sourcecoast.com/forums/jfbco … tivity-log
Basically, Facebook is providing conflicting information about the news.reads action right now. All their documentation states to use it. However, a bug report response says that built-in actions shouldn't be used anymore. It makes no sense, and we're waiting for clarification.
Hope that helps,
Thanks for the reply. It explains it thanks but of course doesn't really help, but that's a Facebook issue ! I guess the good news is I probably have it all set up and working correctly configuration wise, but the bad news is after all that setting up it might now be something you can't do any more!
I have noticed that even though I run the 'auto tune' I still get the message on Facebook developer that my app needs to be updated to the "Feb '13 breaking changes" and am guessing it is all linked to this issue?
Many thanks for all you help and feedback so far.
No problem for the help. Fortunately, Facebook re-opened the bug report from the other thread and clarified their position. It sounds like news.reads will start functioning again soon, but will display differently than they do now. That's not terribly surprising, but we're still unhappy with how the change was [not] conveyed.
As for the breaking change migration, not sure either. The change went into effect fully today, so it's on either way. Again, it shouldn't change the behavior of your app. Test, as always, but you shouldn't run into any other issues.