On my Joomla website, there is a small blog (straight Joomla). I would like to have the headlines of these articles posted to the FB timeline of people reading those articles. It seems to me that JFBC contains all the nice features to make it work, but at the end...
I followed the Open Graph documentation step-by-step. This is how it went:
Facebook have been making changes and there is some 'confusion' now as to what of these sort of things will work. I'm hoping for a nice message soon from Sourcecoast explaining all the Open Graph stuff just as soon as they understand what Facebook is doing!
http://www.sourcecoast.com/forums/jfbco … -read-news
Ah, might have missed that bit. The changes Facebook made mean I think it won't get posted to their page, however if what you are saying is that you don't get the popup on your own web page when they look at the blog page that is something else. I note you say you have the timer set to 0 but as I understand it that would not be allowed by Facebook so you may need to change that anyway.
I did not get the pop up on my pages initially and found it was down to having jQuery enabled on the template settings I was using. Even though I didn't get the pop up though the action was still being recorded in the OpenGraph activity log in JFBConnect - do you see anything there?
I know that I'll have to change my timer setting beyond 10 seconds before submitting to Facebook, but for the time being, as long as it should work on JFBC I thought it to be OK to wait a bit shorter. According to the documentation, JFBC should accept these values.
Anyway, I'm not using jQuery on this website; just the Joomla standard MooTools are loaded. I don't see anything in the activity log either.
Might be worth trying changing the timer from 0 to at least 1 just to see if that is the problem but other than that Ok, well I'll have to leave it to the Sourcecoast people to give you an answer hopefully.
You may want to see the actual page that is target for an auto 'like' action: http://www.kaleidoscoop-web.nl/index.ph … -een-feest.
You'll definitely need to change these settings:
Again in OG, I configured the action 'news.reads' to 'allow multiple', multiple frequency to 1 minute, users can disable, automatic actions to 'on page load' and the timer value to 0.
For Sandbox mode, we don't generally recommend using it. First, we can't set (or even see) that value in Autotune, which makes it prone to being left on.. and causing issues. 2nd, Sandbox mode prevents registrations, which can be nice, but that's about all it does on live sites and since we can't detect if it's enabled, our SCLogin module will go ahead and show the Login with Facebook button to everyone.. and then Sandbox mode will just throw an error if someone tries to use it.
Finally, one thing to test is enabling the "Display FB Errors on Front-End" setting in the Facebook API tab of Configuration. That may show more information. Also, check the OG Activity Log in JFBConnect to see if anything is being written there. That will display success or errors, either way, which can help diagnose things.
I hope the above explains a bit. If we can login to the front-end of your site to test/see things, that would help us narrow down what's going wrong.
Thank you for your patience. I've tried everything you suggested, but alas without any positive results.
Let me explain what I want to achieve: I want a simple 'share' button on my webpages. I learned from an earlier reply from you, that the FB share button is a depreciated feature and that the 'like' button with Open Graph customization is the way to go.
My website has no visitors logon, nor any other front-end logon. I think that I have no need for the SC logon on this particular site, do I? Does that limit any of the JFBC functionality?
I've the like button added to the web pages by the JFBC Social Content Plugin. This seems to work more or less OK. However, when pressing the like button, there is a strange series of events.
It seems there's a bit of confusion reading through your posts. At the beginning, you're talking about Open Graph Actions. These are 'events' that you create on your site that a user can trigger.. reading an article, uploading a photo, joining a group, etc. In addition to Open Graph *Actions*, there's simply Open Graph tags, which describe your pages to Facebook. Those tags are used by a variety of things in Facebook, not limited to just OG Actions. Things like the Like button or Comment box will also use the Open Graph tags when a user Like's or Comments on a page from your site.
From your last post, it sounds like you simply want a Like button on your content. For that, you should enable the Open Graph plugins we have, but you don't need to create "Actions" as described in our long Open Graph Actions in Facebook guide. You simply need to add the Like button to your content, which can be done using the Content Plugin.
So, it sounds like you've already successfully added the Like button and hopefully have the Open Graph tags setup. Now, you're just getting the strange behavior when clicking the Like button (the confirm button and having to click it again). That is likely because your site is new. Facebook can show the "Confirm" link if it thinks the page being Like'd is suspicious (malware, spammy, porn, etc). Also, if your site is new, it may not know enough about your content and so it shows the Confirm button then as well.
What you can do is run your pages through the Facebook Debug Tool. That has Facebook scan your page and will point out any problems. As FB sees more content, they can properly categorize if it's 'bad' or not, and the 'Confirm' link should go away.
Finally, if you're just using the Like or Comment features of JFBConnect (not Actions), you don't need to use a Test User. You can do all the testing with your real Facebook account. You only need to use a test user for Actions, since they have to be approved by Facebook.
I hope that all makes sense and better explains things,
You're right about the confusion. Adding the Like button was straightforward and easy, as is managing nearly all of JFBC functionality. I'm more struggling o figure out how I should configure Facebook to get a 'Share' button functionality without the former 'Share' button itself.
What I want to achieve is the following:
There isn't a direct replacement for the Share button of old. WIth Open Graph, Facebook gives you (the site owner) the power to describe your pages and have more control over what a user's feed post about your page will look like. You can set the title, description, and image that are used when a user clicks the Like button. For the user, when they click the Like button, they get a comment box popup and a "Post to Wall" button where they can add their own comment and choose to post the Like on their wall.
The closest thing available now is a different type of popup for posting to a user's feed, which you can see below:
https://developers.facebook.com/docs/re … logs/feed/
With that, you (the admin) still have to specify the title, description, and image that are used. The user still has the option to add a comment and click a button to post to their wall. There is no method to select an image though. Additionally, since that's not using the 'Like' button, there is no counter of popularity of that page. It's a one-time use share, whereas the Like button can draw more users in by having a higher Like count.
Hope that explains. Of course if you have any questions, just let us know.
Thanks again for your explanation. I start to realize, that I've to dig deeper in Facebook, before I can make effective use of it. I just ordered some books on the Facebook API through Amazon to get a better foundation.
The thing that keeps really nagging me, is that I cannot use the like button when I'm switched to another page of mine. Only when I'm logged on to my personal page, I get to like things. Yet, I also have a page for my company and I like to keep things separated. With the depreciated share button, this used to be no problem. From one of the FB tech pages, I understood that apps making use of Open Graph require authentication, and therefore I can imagine that I can only use those functions from my personal profile. But, FB also states that the standard social buttons, such as like and send, do not depend on authentication. Yet, I still have to switch to my personal profile before the like button is shown.
Thanks and regards, Paul
Hopefully you don't need to know too much about the underlying Facebook API unless you want to develop or add new features. There is a lot to learn, no doubt, but for the social widgets (Like, Comment) or features we already support in JFBConnect, you can always rely on us to try and help explain and clarify whenever we can.
As to your specific question on why you can't Like from a Page, that's a restriction from Facebook. FB wants all Like's to be 'organic' and tries to prevent abuse as much as possible. Since one user can create unlimited Pages, those Pages can't be allowed to then go Like everything for the user. It'd be ripe for abuse, and would ruin the Like counts for a lot of sites. By tying Like's to a "Real" person, they eliminate that problem and it's much easier for them to track abuse.
Hope that explains why Pages can't Like content on sites. If you need more explanation or help though, just let us know.
Thanks again for your support. I'ld only wish that FB was so understanding. It seems to me that a part of the attractiveness to separate concerns by using separate pages is now lost in an attempt to mitigate abuse. I think I start to understand why organizations sometimes create a company profile as if it were a real person.
For the time being, I'll stick with the like button. Related to that, I've one more question. In the social plugin, a meta-tag og"description" is set. What are the means to control the length of the snippet? It seems that it is now about 50 characters; could I easily change that into 50 words or something?
Thansk and regards,
Yup, using a single user profile can help with some issues, but there's big limitations on that as well. First off, friends are 2-way connections, which means you'd have to approve people whereas anyone can 'Like' a Page. I don't know what the current limit is, but I think there's a cap of friends around 1000. Also, the JFBCFan module, to show the stream and 'friends' of a Page only works with Pages.
So, Facebook definitely wants people to use Pages for businesses, products, etc and Profiles for 'friendships' only. What you choose to use is what is best for your needs.
As for the og:description, that's done automatically be JFBConnect if you haven't gone into the Open Graph settings and created an "Object" for the page you're looking at. The default for Joomla articles is the first 10 words. If you create a new Object and set the category to your top-level category, you can then set the Description settings (in the right-hand side) to be 50 words or 500 characters or whatever would work best for you.
If you need help with the above, just let us know.
I've been running lots of experiments, using all your tips and advice, but I'n not getting where I want to be. Maybe I'm just rying to beat some Facebook strategy. I hope that you can tell me.
What I want to achieve is the following: on my website I've a blog. As soon as I have a new entry, I want to post a teaser of some sort on a page on Facebook. Facebook like would be ppropriate. I can post such teasers on my profile page, but not on any other page. The next thing I thought I could try was to post on my profile page and then like it from the other page. Alas, I can like many thing, but not this particular post. My spouse also liked the article from my blog, and again, I can share that like on my profile page, but not on any other page.
What is your strategy? Do you have any means to post something to a Sourcecoast page on Facebook?
Thanks and regards,
Sorry I didn't get back to this post. I think we're covering your question in the other topic you created:
http://www.sourcecoast.com/forums/jfbco … ebook-page
I'm going to close this post so it doesn't get too confusing and we can continue the discussion of this topic in that other thread.