Azwanz,
To fix the issue, you need to upgrade to JFBConnect 4.0. We've sent 2 newsletters (
eepurl.com/eNPtQ and
eepurl.com/fRGsr), created a
blog post
, and tweeted multiple times about the change to Facebook's authentication scheme. Originally, it was required in October by Facebook, but they pushed it back to last week. Now, it's required. You should feel good that it lasted this long, I think, instead of breaking back in October.
We never create JFBConnect to 'break', but sometimes, Facebook's changes cause it to do so. During your subscription period, from 3.1 to 3.2, there were huge breaking changes that occurred to Facebook's commenting system. By staying up-to-date with JFBConnect, you were likely not aware of the changes. This is part of our effort to always add new features while keeping pace with Facebook's changes.
There is no easy way to fix 3.4. It took us weeks of effort and testing to get 4.0 properly using the new system. If you want to upgrade to OAuth2 and prevent your site from running into any other issues, we recommend you resubscribe and keep JFBConnect up to date. We have year-long subscriptions, which are a 15% discount over 2- 6 month subscriptions, and we have another 10% discount if you renew while you're current subscription is still active.
Hope that all helps explain, and best of luck,
Alex