Yeah that's one of the changes to the opengraph tags they made. It didn't used to be that way. I'll try to overhaul the OG properties this weekend if time allows.

@panjabi
Yeah they did change the way likes vs. shares work. Shares are actually depricated. The like feature "should" show up on your wall (in my tests with my gallery it does on mine). The problem however appears to be a hangup somewhere in the processing of the like. The same thing happened for me when the recently made changes to the news feed. My own personal likes via the zenFBSuite wouldn't show up on my newsfeed, however my test account and other facebook user accounts would show up properly. Try removing your app from your app settings, then reconnecting to it.

@micheall: Have your plugin add the following attributes to HTML tag?

xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml"

the problem is there's no easy hook to add those to the html tag, I have them on my theme and still had the issue with the author tag, that problem is from them changing the opengraph and how they're restricting it. When I added the author bit it was more of a hack than anything to provide it so I needed to revisit it later anyways.

But yeah, when I retouch the plugins I'm going to add that to the instructions, I knew I was forgetting something.

micheall: the 'like' does show on my wall, but its not appearing on the news feed which is visible to all for some reason. The 'share' feature does both, which would mean the 'share' feature is a better option to attract more traffic to our galleries via facebook.

I think the problem is as ReeRee described. Using the debug tool i get the following;

Errors That Must Be Fixed:

Object Invalid Value: Object at URL 'MY URL' of type 'article' is invalid because the given value 'Admin' for property 'article:author' could not be parsed as type 'profile'.
Missing Required Property: The og:url property is required, but not present.
Missing Required Property: The og:type property is required, but not present.
Missing Required Property: The og:title property is required, but not present.

Warnings That Should Be Fixed:
Extraneous Property: Objects of this type do not allow properties named og:author.

So that sounds to me like it's having issues because you haven't filled in the options on the zenFBCommon portion. You need to do that as the zenFBCommon is partly what drives the OpenGraph metatags. The question I have is how those aren't being populated with default info because there should have defaults and those should be loading in your theme because the plugin makes a call to the theme_head hook. What version of Zenphoto you running?

As far as the like vs share, Facebook itself deprecated the share function. It would make sense that you're not having info populating to your news feed though because your opengraph tags are messed up somehow.

The options within zenFBCommon have been filled in.
I'm using the latest version of zephoto and the default theme.

I wouldn't say the share function has been depreciated given that sites like YouTube are still using it as well as fb recently added the option to share status updates. 

Also I've tested your demo site with 2 accounts, both fail to show the like on the news feed, only visible on profile. Surely it can't be just me having this issue, or are others not concerned about the like appearing in news feed? 

Perhaps I'm not being clear, Facebook has deprecated the share function, meaning it no longer supports it. It still functions, but there is no support for it, and it receives no further development.

Perhaps a link to your site so I can look at it/test it?

I get this message now on images with no comments:

Warning: this comments plugin is operating in compatibility mode, but has no posts yet. Consider specifying an explicit 'href' as suggested in the comments plugin documentation to take advantage of all plugin features.

I noticed one fix that says you might lose previous comments if you fix it. Is there is anyway we can have our wine glass full and our wife drunk?

See: http://stackoverflow.com/questions/8417170/how-to-migrate-comments-from-using-url-property-to-href

Also, glad to see your site back up again finally!

`
// Output Button XFBML
if ($comments_open) {
$zenFBComments_html = '';
echo $zenFBComments_html;

            unset($zenFBComments_html);

`
It looks correct to me the code. href is pointing to $URL and URL: doesn't exist. Sigh.

Here is another site with a solution, but not sure how that applies here: http://www.iannpurugganan.com/2011/12/fix-specifying-explicit-href-facebook.html

@lkjs yeah I noticed that myself. I'm working to see if there's a way. Problem seems to be that Facebook is storing the old format comments separate from the new format, so if I update the plugin to the new format (to remove the warning), then the comments disappear. Still working on it.

It also seems that with the eventual release of the timeline interface they're retouching the code on all the social plugin components. So inevitably we're going to have to succumb to some changes here. The joys of working with Facebook is the magic changes that get sprung on people.

Yea, so weird. Facebook reminds me a lot of American law. You need a lawyer, its expensive, it always changes, and there is no documentation that makes sense, only cryptic case analysis from time to time.

I think it is great that they like to push things forward, but they don't seem to do it with a lot of notice or understanding of what is going on in the real world.

Wait, it reminds me of the recent Final Cut Pro X too. :-)

@lkjs the problem comes from the new format they're using for the code of the plugins now. Instead of that version I'm going to have to update it to something similar to this:
`

`

I don't understand why they have to make a public warning notice to scare your users. Why can't they just tell you in developers section it is changing and that you need to as well...

Is there a quick fix that will work losing all the post data? I sure hate to lose it especially since google now can read iframes and indexes the comments.

What is weirder is that anything with a comment doesn't have this stupid warning. I'm all for progress but not unneeded error messages for users!

lkjs email me (contact on my site) I'm gonna send you an updated zenFBComments.php to test with

Sent, cheers.

Looks bad for the old comments, but new plugin solves error message, at least until Facebook decides to change it again.

Yeah, I'm still working on trying to dig up an answer all. Basically, if you used the plugin and used the "migrate" option that Facebook included to transition old comments from the FIRST plugin to the second, you might end up losing comments on upgrade, however upgrading is the only way to get rid of the Warning message. I'm still working on it though, so keep your fingers crossed...

Let us pray.

Hey micheall,

I'm unable to get zenFBLike to display on my website. I just tried to send you an email using your form on your website but I'm not sure if you received it (no email was sent to me as a result). My email is chris[at]ckgd.net

Thanks!

Hey Chris, thanks for alerting me that you sent an email, it reminded me to add that account to my email client. I had reformatted and not added it. I have responded so will help you there.

-mike