Been fixing some issues with our "Like"-buttons on several sites, since apparently you need to post them via an Open Graph application since Nov. 7th?
One of the requirements so it seems is to create a page for your application, but we've already had a Facebook page for our blog. Is there anyway I can merge them? I see no use for keeping a separate App Page next to our default page?
Related
I have a Blogger website. I want when users click any links to open any page or post it should open abother link in a new window and at the same time it also should open the main link of that particular post or page. This should auto update to every links on the blogger website. Is there is any way. The link it should redirect is a ads link. That's why I need it. This problem is hard to describe.
This is not an actual answer,
Opening multiple links at the same time will destroy all of the user experience and your website's reputation as well. And if you are redirecting for some ads website then it will be of no use since now a days AdBlocker is installed by majority of users.
You can serve non-intrusive ads and maintain over user experience as well. like facebook and google does.
I would like to delete thousands of old posts on a Facebook page made by another (discontinued) application.
From what I gather reading the documentation an application can remove only the posts made by itself. This is a reasonable default, but it prevents the development of any kind of administrative or cleanup applications, so I wonder if this is really the case.
Is there a way to mass delete posts made by an application? (If not through the API, perhaps through the UI?)
You just have to go through the page feed with /page-id/feed and delete them one by one: https://developers.facebook.com/docs/graph-api/reference/post#deleting
You are right though, you can only delete posts made by that App - most likely for safety reasons. A malicious App could just delete all Page entries.
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
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.
I am trying to create a sweepstakes application.
I am trying to copy wildfire.
But I am unable to create facebook applications dynamically like they are doing.
I checked it they are using graph api to show on front end but there is no method available in graph api to create applications dynamically.
Can anyone please guide me how wildfire is doing dynamic app creation. Is there any alternative available?
In general, they are likely not creating new applications for each client. Unless you can show us evidence of this, it is the same application being installed many times onto their client's Facebook Pages.
The application script can detect the Page ID and change the display logic appropriately. Seen here:
Get Facebook fan page ID
If you really want to create applications for your clients, take a look at this thread:
http://facebook.stackoverflow.com/questions/6264080/create-a-facebook-application-programmatically
EDIT (Not being able to comment is horrible) in response to J's post:
There is not a way to create applications entirely programmatically, but you can get really close creating a user-flow around:
https://www.facebook.com/connect/create_app.php?api_key=[key]&name=app_name
Where [key] is the api_key of the parent application. It isn't documented anywhere so you should have a manual fall back in place. The link above does work to create a new Facebook application tied to the currently logged in user (the parent api_key does not seem to have any effect but it is required).
To determine the api_key of the application created, ask the user for the appropriate permission and query /accounts to retrieve a list of Facebook applications the user owns. Do this before and after the user clicks the above link to determine which one was just created. From there, have the user get a new access_token and get the appropriate permissions to modify application settings. You should then customize the newly created application.
Mike
This has been mentioned several times in the old Facebook forum.
Wildfire, North Social et al, do not create applications dynamically. It's the same application being installed by many clients.
How is this possible? Well, when a Page loads a tab application, Facebook pass you a signed_request parameter. When you decode this signed request with your application's id and secret, you will find inside the page id from where the tab application is being called. You can then use this to work out which of your clients is making the call to your code and therefore what content to deliver to the browser.
There have been changes to the Graph API recently to allow you to manage applications once created but you cannot (and likely will never be able to) create applications programmatically through the Graph API.
The second thread mentioned by Mike mentions child applications but this was deprecated from the Facebook code base some time ago and would not actually allow the creation of applications in the way I assume you want.
J