FB-Comments gone after upgrade

Alright.. yes, we (and Facebook) screwed up a little bit here.

Facebook announced early last month that they were changing how Comments worked. Previously, they required a unique 'id' for a page's comments, which was passed from in XID parameter. As of the end of April, they will require the URL of the page. We like the new method much better because it works better and is more logicial. They do, however, have a backward capable mode to allow the continued use of the XIDs.

We still support this XID method, with the backward-compatible additions that are required. However, the only way we currently support it is through the tags {JFBCComment xid=12345}. If you guys are using the JFBCComment Module, we should be able to whip up a module that has a switch for "Use XID" option, and things will go well.

If you're using the JFBCContent plugin (to automatically put the Comment box in articles), that's harder. Mainly because JFBConnect has no way to know what was 'old' legacy XID content vs new content. On new content, we'd want to use the href parameter, on the old content, continue using the XID parameter. This is so that your definitely compatible going forward. In addition, Facebook hasn't answered the question of 'If new content is created after April 27, and it uses a XID, will it be ignored'? There's some that think they'll only allow content with Comments on it to use the XID method after that date.. other content will throw an error. We don't know the answer though, and won't till the end of this month.

So please, let me know how you're implementing the Comments on your site. We can get you setup no matter how you use it, but just want to caution you that Facebook can decide to remove the backward compatibility at any time. They are (thankfully) standardizing all of their modules on the href parameter, so we think this is the long-term solution for them.

Hope this helps explain. It certainly wasn't something we like to do, but we could have noted it much better. For more information on this change from Facebook, see:
developers.facebook.com/blog/post/472

Regarding some of the other questions I missed above:
* The comments are not saved at all in your local database. They are all stored in Facebook. Before it's asked, Facebook has no way to import comments into a page, and there's no way to say "This href was that XID, link them up". Again, we wish this was a smoother process from them.

* The Configuration Guide has been revamped for 3.2. If there's a setting you don't understand or want information about a section, check it out, and you should find your answer. If you can't figure something out, definitely let us know and we'll revise it.

Thanks!

We're working on an updated JFBCComment module with a "Use Legacy Mode" option. It will be out in the next few hours. We'll post here, and would love your feedback once it's available.

Also, were you specifically specifying the XID in your module, or were you leaving that parameter blank, so that it was automatically generated?

pietklerckx,
I'm attaching a new build of JFBCComments to this thread, v3.2.1. It has an option for "Use Legacy Mode" at the bottom. Simply enable this, and a XID will be auto-generated OR if you want to specify your own XID, just put it in the href field. Hope that makes sense.

Unfortunately, you may not be able to use this right now. Facebook, last night, seems to have broken the migrated support. There's a long thread about this (unrelated to JFBConnect), and hopefully it will be fixed soon. We tested this module to make sure the XID parameter is the same as it was previously, but were unable to test due to this bug.
forum.developers.facebook.net/viewtopic.php?id=95474&p=1
forum.developers.facebook.net/viewtopic.php?pid=332481#p332481

Issues like this are part the reason we made a harder break from the old code than some would have liked. Facebook isn't always great at keeping support for old features around.

Please give your feedback on the module, we'd like to hear your experience. The link above will be valid for a while, but we're not going to include that module in the JFBConnect package just yet.

Good luck!