like the button not displayed

Very odd. We'd recommend you use JFBConnect's integration as well, but good to know it works with sh404SEF's. Can you do the following:
* Enable sh404SEF, open the HTML on your page and search for "og:". Copy the block of code you find there with the values they set. Do the same with JFBConnect. That will help us compare.
* Disable JFBConnect's Open Graph integration. Then, re-run the debugger and let us know if that works. We need to eliminate if it's our Open Graph tags that are a problem, or something else.

We're extremely curious about what the cause is for this. We've never seen this before, and would like to get it fixed for you in case it happens to others. Additionally, if there is some conflict with our OG tags, we want to know.

Thanks, and sorry for the troubles!
Alex

Alez,
I just responded to your PMs with an email address to send the files to me. The forums stripped much of the tags, and it's much easier to compare real files instead of cut/pasted text. If you can save the HTML from the page directly from your browser and send that, it'd help a lot!

Thanks,
Alex

Alez,
Thanks for the files. The only difference I see is what I mentioned above that seems odd. On the JFBConnect page, the Open Graph value for "type" is set to "website". That shouldn't be like that on an article page. Normally, JFBConnect will set your homepage to a type of "webpage" and all other pages will be of type "article". The HTML file you sent me using the sh404SEF tags properly had the type set to "article".

Can you look into why the type value is being set to website on all your pages? This is likely a default in the Social -> Open Graph tab of JFBConnect that simply needs to be removed. If not, let us know.

Thanks,
Alex

The ordering inside the head area should not matter at all. That's basic HTML coding, and it's never mattered on any other sites. The xmlns for .../2008/fbml also doesn't deal with the Open Graph tags, so that *shouldn't* matter. We removed that namespace tag over a year ago as it's not recommended by Facebook any longer to be included.

The only other differences I see in the Open Graph output on your page now is:
* sh404SEF isn't including the OG app_id parameter: meta property="fb:app_id" content="103990813004897"
* The locale is it_IT vs it_it. The it_IT is definitely wrong as Facebook used to throw a warning if the language wasn't all lowercase.

However, you can try adding the following defaults in the JFBC Open Graph tab to see if it makes any difference:
locale=it_it
app_id=1234

The app ID will be wrong there, but it's worth testing with a bogus ID just in case somehow your app is configured to not allow scraping (mainly, if it's in sandbox mode). We can also help you to remove the app_id tag altogether in case that doesn't work so that we're pretty much in parity with sh404SEF.

Please let us know if that helps. Still very confused as to what's wrong as nothing looks wrong and you're the only user reporting this odd issue. You did mention at the top that you upgraded JFBConnect and this problem happened. I never really did ask, do you know roughly what version you upgraded from?

Thanks,
Alex

Alez,
We're not giving up yet, unless you are. Would it be possible to send us Admin credentials for your site? If possible, we'd like to get in to make some minor modifications to JFBConnect and see if we can narrow down what setting or other feature is causing the problems you're having. We don't like that you're running into trouble and it's best if we can find the issue before it affects others as well.

If you can't send super admin credentials, we understand and can provide some more ideas for you to test out as well.. that may just take longer.

Thanks,
Alex

Alez,
Just wanted to circle back on this one more time. We've found multiple other reports in Facebook's bug tracker of this issue now:
developers.facebook.com/bugs/130242697118406
developers.facebook.com/bugs/367507079985361
developers.facebook.com/bugs/182306028567936

Facebook has said they're looking into the matter, but one suggestion that's been mentioned to work is simply changing the fb:app_id Open Graph tag. sh404SEF doesn't include that OG tag, which would explain why it works there. I did mention trying to change it to 1234 above before I read these posts, but I'm not sure if you ever tried that.

Please note, you shouldn't change the Application ID parameter in the Configuration -> Facebook API tab. In the Social -> Open Graph tab, simply add the following:
app_id=1234
That *should* override our insertion of the App ID. If you look at the source HTML and it doesn't though, let us know and we can tell you how to remove the app_id tag altogether until Facebook fixes things on their end.

Best of luck,
Alex