JFBCComments with RokGalery

Walter,
It's a bit of both. The problem is the ?page=1 that gets added when you click the next button. Facebook Comments are attached to a specific URL, and that ?page=1 is making the URL look different that the URL that the comment may have been originally posted on (if you go directly to the image, vs the Next/Prev to go to the image).

There's a few ways to fix this:
1) Get in touch with Rockettheme and see if they can use the same link for Next/Prev
2) Alter the JFBCComments tag to include the actual URL. This would depend on how you're including the comment box.. are you using the JFBCComments module or {JFBCComments} tag in the template somewhere?
3) Ask us nicely and we can give you some code to remove the ?page=xx variable from the comment URL. We don't want this in the code for everyone, so it'd be a specific change for you. Many multi-page articles should have unique comment boxes on each page. Making this change would be very easy.. but you'd need to make it with each new release (annoying).

Alex

To strip the page variable, you'll need to edit the /libraries/sourcecoast/utilities.php file. Around line 172, you'll see:Simply add the following line underneath that:That's it Please realize that that will make any multi-page content on your site use the same comment box/like button, etc. It will work for all of our social plugins that use a URL for a reference. While I think this will be fine on your site (actually desired), I just want to let you know.

Obviously, test. Any comments that were left on ?page=1 images will be lost. You'll only see comments that were left on pages without that tag.

Please let us know how that goes!
Alex

Walter,
The Open Graph tags on the page are including an empty Facebook App ID and Admins list. In the Open Graph area of JFBConnect, did you set these defaults? If so, can you remove any lines in the defaults box that look like:

admins=
app_id=

If you didn't add those tags, we'll need to understand why they are being set to blank for that page. Currently, if you run your page through the Facebook URL Debug Tool, it's throwing an error because of those values, and is probably causing problems with scraping the information about your page.
developers.facebook.com/tools/debug/og/o...eld-trip-report.html

Another possibility is that you have some 'image scraper' prevention going on. I know you had something that was preventing right-clicks on the page before. If you have anything like that at the server level, it could be interfering with Facebook downloading the images.

Hope that helps get you started!
Alex