JFBConnect 3.2 problems

Morpheus,
Definitely agree the forums are a better place for this discussion. It's much easier for me to keep track of, and appreciate you moving it here.
1) You mention this is fixed
2) The Open Graph image needs to be set for whatever page the Like button is... Liking. I'd recommend opening the code for the page where the Like button is. Search for fb:like. If there's an href parameter, look at that page for the og:image tag, and make sure it's set. If there's no href parameter, check the code on the current page for the og:image.
If you can't find it, that means you either haven't set a default for your entire site, or haven't set one for that page. You'll need to do that, and it should work. If that doesn't, then post a URL to a page that the Like isn't working how you'd expect, and we'll look into it further.
3) Like text/width overflow - We'll have to investigate this more. This may be a bug with Facebook, as we have little control over this. They just updated the look of the Like button, and this may be broken with this update.
4) Yes, we get some requests here and there to improve validation. None of the warnings should cause any issues with your page, and when we've tried to fix some of them in the past, that's actually caused other issues with SEF components. Many of the errors are actually because we use & in javascript variables for URLs instead of &. Any browser can easily handle either case though.
5) Connect this to your Facebook account - We're looking into this. We have a rollup fix for 3.2.1 that will probably be released later this week, and this should be in there (along with a few other langauge string misses).
6) Same as #5

Finally, regarding the jfbclike in an id, you're absolutely right. This will definitely be fixed in the next release and was a dumb mistake on our part. To fix, you can edit the /plugins/system/jfbcsystem.php file. All of the social widgets appear to be using id, but we'll move them all to class for the next release. Feel free to do this now.

Thanks

1) The OpenGraph tags can be set to defaults in the admin area of JFBConnect. Click the social configuration area and then the OpenGraph tab. In there, put something like below. Also, make sure the Open Graph tags are enabled.
image=http://linktodefaultimageforlikes.png
This will set a site-wide image for all likes. Then, on individual pages, you can simply type {JFBCGraph image=http://betterimageforthispage.png}
That will use a better image for that page. You can either do that in the article text, use a CustomHTML module assigned to that page, or multiple other methods depending on the page.
2) Facebook scans pages about every 24 hours for images. If your page was liked before you updated the image tag, and then you Liked it again, it may still use whatever was the last image. Facebook will pick up on the preferred image shortly. Feel free to check your HTML for the og:image tag and make sure its there, and use the Facebook Linter to see how Facebook views your page:
developers.facebook.com/tools/lint/
3) This update will be in the 3.2.1 release later this week
4) Will check in a bit. We had this issue before, if I recall correctly. Do you remember what fixed it before?

We'll have to see what's up with the avatar setting. That's not something we can recreate on our test systems at all, so something it configured differently. Not sure what. Can you PM us a set of admin credentials that we can test with on your site?

The Open Graph stuff works for the Like button. You can either set the image, link, and other info on a site-wide basis in the JFBConnect admin area, or you can individually set those per page by using the {JFBCGraph ...} tags. You can use the linter (linked above) to see how Facebook sees any of your pages, which is what it uses for comments, likes, and other social activities that get posted back to Facebook.