'Link' to website from Facebook not right...

We haven't used that specific metadata plugin (and we'll be adding some similar features to an upcoming release of JFBConnect), but what you're describing is expected behavior.

Basically, Facebook lets you add meta-data to your page for link, image, description, etc. If Facebook detects this information on your page, they're smart enough to say "This must be exactly what the owner of this site wants to represent this page". In that case, the share information is 'fixed'. If there is no meta-data, then Facebook tries to let the user decide what's pertinent on a page. Since there may be images in a sidebar, or your logo, or other non-essential images, this is nice because hopefully, the user can figure it out better than a computer.

Hope that makes sense from an overview. So, the plugin your using is automatically creating the meta-data, which is then being automatically picked up by Facebook.

Our plugin will work similarly with some components out of the box, but we're anticipating a way to let you override any defaults by our tagging system. For example, in your Zoo article, you can put:
{JFBCMeta title="My Event" image="http://...image.jpg"}

It's not available yet, but with that system, we will try to guess the best metadata (as I'm assuming the plugin you're using does), but you'll have full control over it on a page-by-page basis.

This should be in JFBConnect 3.1 (mid-November).

Hope this helps clear up your question, and let us know if you have more!

We don't give timelines for multiple-point-release-in-the-future extensions. We have a hard enough time hitting our targets for the 'next' release, that we try to be vague when giving those timelines out too.

As for Zoo, I can't say I've used it before, but we agree, it's definitely one of the most popular CCKs, so it won't be neglected.

Definitely appreciate your feedback/suggestions, and glad you're happy with the feature-set already included.. but rest assured, improvements are always on their way

The 'random' image thing will be correctable in the 3.1 release of JFBConnect by letting you specify the image on a page by page basis (as described above). That image is Facebook making it's best guess as to the image that represents the page.

As for the Like functionality, yes, it should work just like you describe. I just wrote a long post, then looked at your page further.. yes, it seems like the query string is not working with the Like functionality. Let me look into it more. In the meantime, something you may want to try is using the url parameter in the {} like tag, like so:
{.JFBCLike url=http://www.swindonacademyofdance.co.uk/index.php?option=com_content&view=category&layout=blog&id=1&Itemid=77#}
The reason this may be good for you, either way, is because you're using a blog layout on your home page. In that case, if there are multiple like buttons shown (1 for each article), the {} tag will simply use the 'current' page for each of them, which, would be the home page. We're (admittedly slower than we'd like) working on a content plugin that will insert the Like and comments automatically into an article.. just not out yet.

The url tag will work from any page that's showing that Article's like button. Not the most convenient, we'll agree since it's manual per article, but should get you closer to what you're looking for for now.

Hope this helps!

Unfortunately, no ideas. We'll do more testing with the url tag and see if we can get it to break, there's always a chance we missed something. If you can paste the exact tag you're trying to use here, that may help us to diagnose what might be going wrong.

Thanks

The code in the article is what we replace the {} tags with, so that's expected. Obviously, the URL is not being replaced properly, but the rest looks correct.

We'll do some testing with that code and see if we can recreate the issue. Hopefully, it's just something silly on our end. We'll let you know what we find!