Got stuck somewhere configuring JFBC Open Graph

Paul,
You'll definitely need to change these settings:

Again in OG, I configured the action 'news.reads' to 'allow multiple', multiple frequency to 1 minute, users can disable, automatic actions to 'on page load' and the timer value to 0.

A setting of 0 for the timer triggers the action completely differently since we don't need to use Javascript at that point. As Buzzy mentioned, I'd recommend at least 1 for testing, but you might as well just set it to (at least) 10 so that testing is as similar to 'final' as possible. Then, of course, switch the "allow multiple" to "Only once" or whatever. Multiple won't even work since Facebook will simply decline the additional attempts as news.reads actions are required by them to be 1-time only.

For Sandbox mode, we don't generally recommend using it. First, we can't set (or even see) that value in Autotune, which makes it prone to being left on.. and causing issues. 2nd, Sandbox mode prevents registrations, which can be nice, but that's about all it does on live sites and since we can't detect if it's enabled, our SCLogin module will go ahead and show the Login with Facebook button to everyone.. and then Sandbox mode will just throw an error if someone tries to use it.

So, with all that said, I can't see what's going wrong with the action. JFBConnect won't needlessly add Javascript to the page to trigger the action if the user isn't logged in, and I can't find the Login with Facebook button on your site. I'm also assuming it won't work if your site is in Sandbox mode. Additionally, the Open Graph data that would help me understand your action/object configuration isn't working (for me):
graph.facebook.com/schema/og/fb/kaleidoscoop-web

Finally, one thing to test is enabling the "Display FB Errors on Front-End" setting in the Facebook API tab of Configuration. That may show more information. Also, check the OG Activity Log in JFBConnect to see if anything is being written there. That will display success or errors, either way, which can help diagnose things.

I hope the above explains a bit. If we can login to the front-end of your site to test/see things, that would help us narrow down what's going wrong.

Thanks,
Alex

Paul,
It seems there's a bit of confusion reading through your posts. At the beginning, you're talking about Open Graph Actions. These are 'events' that you create on your site that a user can trigger.. reading an article, uploading a photo, joining a group, etc. In addition to Open Graph *Actions*, there's simply Open Graph tags, which describe your pages to Facebook. Those tags are used by a variety of things in Facebook, not limited to just OG Actions. Things like the Like button or Comment box will also use the Open Graph tags when a user Like's or Comments on a page from your site.

From your last post, it sounds like you simply want a Like button on your content. For that, you should enable the Open Graph plugins we have, but you don't need to create "Actions" as described in our long Open Graph Actions in Facebook guide. You simply need to add the Like button to your content, which can be done using the Content Plugin.

So, it sounds like you've already successfully added the Like button and hopefully have the Open Graph tags setup. Now, you're just getting the strange behavior when clicking the Like button (the confirm button and having to click it again). That is likely because your site is new. Facebook can show the "Confirm" link if it thinks the page being Like'd is suspicious (malware, spammy, porn, etc). Also, if your site is new, it may not know enough about your content and so it shows the Confirm button then as well.

What you can do is run your pages through the Facebook Debug Tool . That has Facebook scan your page and will point out any problems. As FB sees more content, they can properly categorize if it's 'bad' or not, and the 'Confirm' link should go away.

Finally, if you're just using the Like or Comment features of JFBConnect (not Actions), you don't need to use a Test User. You can do all the testing with your real Facebook account. You only need to use a test user for Actions, since they have to be approved by Facebook.

I hope that all makes sense and better explains things,
Alex