How to Force JFBConnect to Grab K2 Item Title

When you create a K2 Object Type of Item and then select the Category, this means that JFBConnect will figure out the correct Open Graph tags for any K2 items within that category. That being said, our K2 Open Graph plugin isn't actually setting the og:title on the page. For title, JFBConnect is using the value from the current page's HTML title tag, which K2 sets for items and categories.

I hope this clarifies our behavior, but let me know if you need any help.

Thanks
-Melissa

The problem was that you had set a default Title tag in the Open Graph -> Configuration area. Those values are used as fallbacks in case a more specific tag is specified by an {SCOpenGraph title=..} tag on the page or a better tag generated by an Open Graph plugin. Our K2 plugin doesn't set the title, it just always uses the current page title.. which means that JFBConnect will assume you'd prefer the Default tag you provided to be used instead.

I removed that tag from the Default area and title is not being set properly. It may take a few days for Facebook to see the changes.

I hope that helps,
Alex

The defaults are what are used when no more specific tag has been set on the site. It's a way to override our automatic 'fallback' tags that are applied on every page. For title, we always fallback to whatever the page's meta title is. For some Open Graph plugins though, we will explicitly set a 'better' title for the page because we may know something more about the extension (like forum discussion topic) and use that instead of the meta title. For K2 though, since that extension always sets the meta title to the article title, which is a great Open Graph title as well, our Open Graph plugin doesn't set a title.... we let JFBConnect use the automatic meta title. In that case, if you have a default tag set, it means that the default would be used instead as you saw in your case.

image, site_name, description

Image can always have a default because that tag is allowed multiple times on a page. In fact, we recommend having a default as JFBConnect will ensure it's the last image tag set, which means Facebook gives it the lowest priority. That's great for a logo or other 'ok' image for any page of your site.
site_name is great to have a default as well. No Open Graph plugins set this, so the default is what should always be used
description can be set with a default, but generally, it's probably best to let JFBConnect take the meta description for the page and use that as it's likely more relevant than a generic 'default' description that applies to your site, but maybe not the specific page being viewed.

Whew! I hope that helps explain, but if you need anything else, just let us know!

Thanks,
Alex

Thanks for the explanation Alex. This must make writing documentation pretty difficult, because there are so many exceptions depending on the Joomla components installed like K2, EasyBlog, JomSocial, Community Builder, etc.

Documentation is always difficult because everything on the social network's side is usually in flux. For the K2 title issue, we have an issue in our tracker to set that properly in the next release to the item title so that the OG Default won't be used. However, we still wouldn't recommend setting an og:title default since that's really something that JFBConnect can generally guess better than have a generic default site-wide value.

Now I am getting this:
...
Is this because Facebook is in the process of reviewing the app?

On that page, the Open Graph 'type' is set to:It seems like you've un-checked the "Built-In Open Graph Object" setting in the K2 object configuration. If you're using an 'article' type, that box should be checked.

As always, you can run your pages through the Facebook Open Graph Debug Tool, below, to immediately test any changes you make. Use the "Fetch new scrape information" so that it's not showing it's cached results.

The benefit of that tool is that it automatically updates Facebook's cached values instead of having to wait days for them to re-scan that page. You may not be able to do that with all of your pages, but can manually update a few key pages (and be confident that the rest should work when the automated re-scan happens as well).

I hope that helps, but if you need anything else, just let us know.

Thanks,
Alex