I'm trying to submitting built-in like action.
First time, I used a button on my site labeled with 'like' and without any logo and linked it to the action, but I've got the following feedback:
Your Like or Recommend button branding conflicts with Section 5.6 of
the Facebook Terms and Section I.8 of the Platform Policy
(https://developers.facebook.com/docs/guides/policy/examples_and_explanations/branding/).
Please resubmit with a different graphic that reflects your own
branding and the ux of your site.
Then I change the button text to 'Useful?', but I've go the following feedback:
Your action conflicts with section IV.3 of the Platform Policies
(https://developers.facebook.com/policy/). You must make it clear to
the user that you will be publishing a story to facebook and get their
permission before actually publishing the story. Additionally, your
action must not be confusing or misleading and should accurately
represent the action the user took within your app.
This confusing, I'm not sure what the problem is, please help :)
Thank you in advance.
It's all explained near the bottom of the the Facebook branding page. On your first attempt you used 'like' and that is not allowed on your custom button. The second time you used 'Useful?' and that is not clear enough and is confusing.
I suggest you read the branding policy examples and the other material.
Section 5.6 of the Facebook Terms
You will not use our copyrights or trademarks (including Facebook, the Facebook and F Logos, FB, Face, Poke, Book and Wall), or any confusingly similar marks, except as expressly permitted by our Brand Usage Guidelines or with our prior written permission.
Section I.8 of the Platform Policy
You must not use or make derivative use of Facebook icons, or use terms for Facebook features and functionality, if such use could confuse users into thinking that the reference is to Facebook features or functionality.
Section IV.3
If a user grants you a publishing permission, actions you take on the user's behalf must be expected by the user and consistent with the user's actions within your app.
Related
I'm looking to have a share to Facebook button in my app but, I'm looking to have a way that when the screen comes up to share that it'll include the current article and the picture that is in the article too. I'm trying to do this is swift. If someone could please give me a hand with this that would be great!
I experienced that. The following passage was quoted from developers.facebook.com.
After discussing this with our team regarding stripping the
pre-filling message area of text, this is actually BY DESIGN with the
new share extension.
Pre-filling texts violates Platform Policy 2.3
(https://developers.facebook.com/policy/) to pre-fill the message area
with text for people to edit, which is why we strip the text. We know
this is a pain point for developers but this is about ensuring that
users are sharing exactly what they want to share on Facebook, and not
being able to accidentally share text they did not approve of. So in
all enforcing policy 2.3 is a feature and not a bug.
Other services may allow you to accomplish this pre-fill but we have
updated the share sheet implementation to adhere to the same rules as
you would have when sharing directly using the iOS Facebook
Application instead of the native share sheet.
https://developers.facebook.com/bugs/949486035103197/
I have like/share buttons on my website and am not currently using an appid. Finding information on whether this is a necessity for the above configuration is difficult to confirm. When going through the Facebook app "create" forms, I'm really confused by a lot of the requirements as it seems to be more focused around actual apps rather than websites, which login via fb etc.
In the past I have created an app for one of my other websites and I don't believe there was any verification/submission process at this point (about 2-3 years ago). Reviewing my old app configuration now I can see that it is not "live" - does anyone know whether Facebook implemented this submission process in the last couple of years, and then de-activated any live apps that were created prior to this?
I now want to setup a new app for my new website and I'm unsure what the different 'action types' mean and what I would need to simply use like/share buttons on the website. Could someone give me a quick run down of what I'd need and what they are?
Any other info/tips people can provide would be greatly appreciated. I'm finding that the like/share DO still work without the app, but sometimes the share button doesn't work properly (I have a feeling this is something to do with the app).
Thanks
If you are just using the Social Plugins, you don't need to have a Facebook App ID.
If you want more integration, it will be required. Creating an App ID is like registering your App, wether an iOS or Android App or just a website, so that you can make Graph API calls for it.
The easiest way to register your website is to go the quickstart: https://developers.facebook.com/quickstarts/?platform=web (or https://developers.facebook.com/apps). There you can type a name and follow the steps.
You can then follow the "Sharing best practices" (https://developers.facebook.com/docs/sharing/best-practices#tags) on how to use the App ID. For example, by including an fb:app_id meta tag on your pages.
There is a review process, since last April, but that is only needed if you use permissions for your App. If you just use the plugins, that is not needed.
Can you explain more what is exactly not working?
Update
The time you create a page the Facebook crawler does not know yet what the Opengraph data for that one is. This will happen after the first share, but if you want to ensure it is correct from the first share on, you can force a re-scrape.
This section explains how that works:
https://developers.facebook.com/docs/sharing/opengraph/using-objects#update
When an app triggers a scrape using an API endpoint This Graph API
endpoint is simply a call to:
POST /?id={object-instance-id or object-url}&scrape=true
It's a violation of the Google Adsense TOS to refresh the page several times because I have to try out changes on it?
https://support.google.com/adsense/answer/48182?hl=en
Clicks on Google ads must result from genuine user interest. Any
method that artificially generates clicks or impressions on your
Google ads is strictly prohibited. These prohibited methods include,
but are not limited to, repeated manual clicks or impressions,
automated click and impression generating tools and the use of robots
or deceptive software. Please note that clicking your own ads for any
reason is prohibited.
Can't you turn off Adsense while you are testing changes? Or at least turn them off in your development enviroment.
Or, you could add a rule not to show them when your ip visits the site.
I'm using a plugin called FooBox for wordpress that puts share buttons on top of images within a Pop-Over.
Within the settings of this plugin is an option to:
Enable Facebook's new feed dialog way of sharing, rather than their old (and deprecated!) sharer.
Please note that this method requires a Facebook App Id in order to function!
I'm not exactly a developer... so I cannot determine what this means, if its better, how so..
Could someone explain in laymen terms what this is?
Thank you
The old sharer method is no longer deprecated, as Facebook have recently updated it (and removed the deprecated notice that was on their site for ages). Both methods have pros and cons. This is my understanding:
FaceBook Sharer
Easy to implement and no facebook app id needed in order to setup
Can share to personal timeline as well as other facebook pages you are admin for
Sharer recently was updated (Feb/Mar 2014) and no longer accepts custom images and overrides anything you pass it with the image opengraph tags used on the page you are linking to. This is a major problem when used with lightbox solutions like FooBox, because the specific image that is shared no longer gets recognized by facebook.
Feed Dialog
More involved to setup and get working. An app ID is required and the app ID cannot be shared across domains.
It only allows you to share to your personal timeline. No support for sharing to pages that you are an admin for.
It accepts custom images, so FooBox works and the specific image that is shared is the image that is shown in the user's timeline.
I am the developer of FooBox and will be updating the plugin soon with an updated explanation to help users on learning what the difference is.
And since Facebook have removed support for custom images since Mar 2014, we will no longer recommend the sharer, but rather push the feed dialog.
More Info
Facebook documentation page on the sharer. (further down the page under the FAQ section and hardly mentioned)
Facebook documentation page on the feed dialog.
Response from facebook about no longer supporting the custom image for the sharer.
What's better?
Login Button
OAuth Dialog
I like the Login Button because it shows profile pictures of the user's friends who have already signed up for your application and it opens a dialog overlay instead redirecting to a new page as does the OAuth Dialog.
But, I think the OAuth Dialog is newer. Which should we use?
Also, the Login Button is XFBML. Apparently, Facebook is in the process of deprecating FBML. Does that mean XFBML is being deprecated too?
It isn't that one is better than the other - they are intended to accomplish different things.
The login button is used for external websites to allow Facebook-based social elements and community within that site. You can then add other plugins such as comments, the like button or the face pile to further integrate the Facebook social networking aspects, with the login button acting as the authentication mechanism.
The OAuth dialog is specifically for FB apps that run within the Facebook canvas, and allows you to request Graph API permissions from a user which will grant you access to various parts of their profile and additional channels of communication.
While Facebook is deprecating FBML, they are not including XFBML elements that support social plugins, such as the login button. See here for more info.
I think Daniel hit the nail on the head.
I have just started reading up on Facebook Development, and it seems they are providing a great set of tools to do very powerful things, but they aren't particularly explaining which bits do what.
I think you need to be sure of the difference between; a) creating a web app that will leverage the facebook api to enhance its functionality (i.e. using the login button to allow a user to login/create a profile on that website) and b) creating a Facebook app that makes use of the api to simplify development (i.e. authorize and authenticate a facebook user for an app request)
I don't think they have outlined that distinction very well throughout their documentation
The oAuth button is decidedly and absolutely better for a simple reason - it is documented and relatively stable.
The Login Button has nearly no documentation right now ( https://developers.facebook.com/docs/reference/plugins/login/ ), and the behavior has slightly changed several times.
The documentation for the login button is currently limited to how you can :
change the appearance [ width, show faces , rows ]
specify scope
specify a registration-url
For the last several months ( ~Jan - July 2012 ), the documentation has not included anything concerning the flow of information or status -- ie, what actually happens on a successful or failed login.
While there are answers to these questions on StackOverflow , and mentions of other parameters that seem to work when passed in, Facebook does not mention or document any of this functionality at all, so it is essentially use at your own risk. The LoginButton is essentially a black box of mystery, that people just seem to have working thanks to undocumented features, and with functionality that will change/cease on random weekly updates.
tl;dr - stay the f(*& away from the Login Button and just use oAuth