FB Requires Changes to my READ action

Spike,
My immediate guess is that you have the "New User Post to Wall" or "Returning User Post to Wall" feature enabled in JFBConnect. In the v5.0, we added more text to the 'post to wall' settings page describing some changes that Facebook has made to their App Policies. Basically, the Post to Wall on registration or login feature likely violates their new terms, and we don't recommend using it anymore. Their new terms state that any status posts to a user's wall must be editable or approved by a user beforehand, which JFBConnect does not do during registration or login.

Open Graph Actions are a completely different beast, and what Facebook recommends if you want to post 'actions' to a user's wall, like 'reading an article'. Those are not status updates though, and so do not violate the terms noted above when posted.

It's a bit confusing, but hopefully, that explanation helps. In short, if you'd like to use Open Graph Actions, we'd recommend disabling the New/Returning User Post To Wall feature and submit again. When the FB testers are testing, if they see that post on their wall, they're going to assume you're doing something wrong or triggering actions incorrectly.

The rest of what you state *should* be correct if you've set the action timeout to something more than 10s and followed our other guidelines in our configuration guide. Frankly, for approval, it's not a bad idea to set the action timeout to 25s or something (just to be very careful). You can always change settings after approval as it's not monitored continuously, but we wouldn't ever suggest to modify the settings after approval to a way that would violate their policies.

Hope that helps explain, as always, but if you have questions, just let me know!

Thanks,
Alex

You shouldn't set the 'publish_stream' permission unless you are using the New/Returning user Login message or if you have the JomSocial Activity Stream plugin enabled to post user status from JomSocial to Facebook. If not using those, remove that permission and let JFBConnect automatically configure the permissions required.

Beyond that, I'd keep the timer at 25s, do some quick testing to make sure nothing, other than actions you've configured, are posting to your FB Activity Log. If not, re-submit and basically answer the statements above with "We are not posting unless the user is aware. We make them aware with a blue popup in the bottom right where they can choose to delete the action just posted..." etc.

Hope that helps,
Alex

No problem, as always. It's what we're here for. Definitely keep us posted on the new submission. Facebook approvers look at *a lot* of submissions each day, so if things are detailed perfectly, getting a denial isn't uncommon. So, have some patience. They're generally pretty quick and willing to read whatever your explanations are to get past any issues.

Best of luck,
Alex

Sandbox mode should definitely be disabled. Are you adding the URL for the Privacy Policy in the Facebook Developer area or using Autotune? Either should work, but that will help us understand what might be going wrong. Also, for the URL, make sure you've included the full path (eg. yoursite.com/privacy-policy). Save that and then try to disable sandbox. Don't do both in the 'same save'.

As for the Read Action, showing up in the Activity log is the most important. Reads won't usually post on the user's Timeline due to recent changes by Facebook for 'automatic' type actions, like reading, listening, watching, etc. However, they are still used in the Ticker and can show up in friends news feeds for what that user is doing. All you can do is look at the Activity Log to make sure it is actually working.

Hope that all explains, but as always, if not, let us know.

Thanks,
Alex