Different Behavior if Using Custom Tag

Yes, we have ideas. This is unfortunately an annoying bug with Facebook, which they are being vague if they're going to fix. To fix, for now, when you use the {JFBCComments} tag, also use the href= parameter: {JFBCComments href=http://blah.com/something}

The reason is that when you use the {JFBCComments} tag by itself, we don't specify an href parameter, and Facebook rightfully assumes the comments should be on whatever page the comment is displayed on. However, Facebook recently upgraded the comment box, and if you don't specify an href parameter, for some reason, it inexplicably still uses the 'old' box. The 'old' box is the one you see where you cannot change how you post.

In the next release, we'll force the href parameter to the current URL if none is specified, but for now, the solution above is our best and easiest workaround.

Hope this helps.

Nope, the Like button has always used the URL, so Facebook doesn't have an 'old' vs a 'new' version to cause this confusion. You should be able to use {JFBCLike} without any problems. However! we'd recommend that you specify a URL to make sure that it's always the 'right' URL that someone Like's. For example, if you have SEF URLs enabled, and the night dive page is /night-dive, that page may also be reachable at /index.php?option=com_content&view=article&id=12. If someone stumbles on that non-SEF link and Like's it, that's a separate page from the SEF version, in Facebook's eyes, so you'll be splitting your Likes.

However, however! If you're using the Open Graph tags on the page to specify the URL of the page (the canonical URL), then even if on the non-SEF version, Facebook will know that the Like is intended for the SEF URL specified in the Open Graph Tag. This is why the move to the 'new' comment box is a good thing, because the comments are attached to a URL, which can be manipulated with some of the Open Graph stuff.

Finally, our JFBCContent plugin to automatically insert comments/likes into articles will always insert a URL for the page the widget is being added for, so the comment issue isn't a problem for that.. only when you use the {JFBCComment} tag or Module with no URL specified.

Whew.. confused yet?

P.S. I want to go on a night dive! Haven't been on one in 10 years, but loved it.
P.S.S. Your engageyourdivers.com site, using chrome, is showing the TapThemes template. Not sure if that's intentional, since that's for mobile stuff mainly, but thought I'd call it out.

Thanks for the review. Always appreciated.

You can change reviews, but unfortunately, you have to contact the JED team. It's pretty inconvenient, and we wish people could update reviews easier, but as far as we know, that's the only solution.

Regarding the OG tags, any {JFBCGraph ...} tags on a page take precedence. The ones in the admin area are defaults and used whenever per-page overrides are not set. Even for things like images, for which you can specify multiples of, if you have a default, we'll still include it, but it will be the last image tag so that the JFBCGraph image=.. tag comes first (and is used by default).

Really do want to get back into diving. Long time ago, I dove Belize (only time I've done a night dive), and about 6 years ago Cozumel, and about 3 years ago (for my honeymoon) went in Bali, which was awesome. All fun, but not nearly enough, and haven't been since. Enjoy your night dive for me!

Correct. That's the order we've shot for, so let us know if you see different behavior. Seemed the right way to us to allow the maximum flexibility without too many headaches..