Hi I created a page on Facebook, and used Facebook Graph API to post photos to the page.
The post address is like:
https://graph.facebook.com/2104798556250663/photos
And Post parameters are:
message=url_encoded_message
access_token=your-access-token
url=image_url
privacy={"description":"public", "value":"EVERYONE"}
The post request was successful, as I was able to see posted photos in the "Timeline Photos" album and can see them in my timeline. If I click a photo and then click "Edit" I can see the setting is "Public".
However, when viewing without logging into Facebook, or as another account, none of the API posted photos are seen. If I went to "Timeline Photos", I can only see some wording like "25 Photos · Updated 13 minutes ago".
To further test it, I manually uploaded a photo, and the photo also went to "Timeline Photos". This time I could see the manually uploaded photo, even without logging into Facebook.
I have checked the privacy setting by clicking the triangle on upper right corner on my page, then click "Settings", then click "Privacy" on the left column, set "Public" for the "Who can see your future posts?". And uploaded new photos via API after that. Still doesn't change the situation.
To sum up, API posted photos are invisible although the setting is "Public", while a manually uploaded photo is visible.
Thank you for your time.
Sounds like your app is still in development mode - so all content created through it, will only be visible to people with a role in the app.
You need to set your app “live”, for this photo to become visible to everyone.
Related
My app uploads a picture to the user's album through graph API (/me/photos) and then grabs that picture, makes it user profile picture by sending the user to
http://www.facebook.com/photo.php?fbid=[PID]&makeprofile=1
It worked well, the user would be presented with the page that he could crop and save right away. However, just 2 days ago, the page was changed. The user will, instead, be presented with the picture in theatre mode (popup on black screen) and has to click a non-obvious link "Make Profile Picture" to crop and save.
The question is, it is the url that was just changed, or it is a new policy of Facebook. If it is a policy, I would like to have the link that this matter was announced
See the picture here, https://drive.google.com/open?id=0B0vWR6nY09_wRzhwU3VadG81TGM. It used to be like on the left but now it is the one on the right
I don't have 10 reputation points yet, so can't embed image, sorry. Please see the image that can help clarify, right away, what's wrong: http://i.stack.imgur.com/b6BbO.png
I am having issues integrating Facebook buttons on my site. I have created a FB app to use with the integration - my like button (see http://soundsviral.com/2014/02/13/tennis-court-by-lorde-45/) is working just like I want it to. However, the share button next to it returns a story like you see above. The real disconcerting piece is that the link for the "Sounds Viral" name (which is the name of the app here, not the site) links to the app itself, which I don't want users to visit at all.) How can I change this URL to be my homepage (or the link in the post below, if that's preferable?)
I also which I could change "link" here to be "song", which is a supported og:type and is in use for my "like" button. However, for the "share" button, it just says "link". But that's less important to me than the actual URL in the story.
Thanks for any ideas!
The solution is to set your facebook app to be a website app that directs facebook users to your website.
To do this:
go to you app page
go to Settings
click Add Platform button
Select Website option
Enter URL of your website and save
I'm designing a photo-oriented Facebook app that would let users tell stories in the app-specific way and advertise such stories by posting a single, preferably large, "cover" photo. Photo posting is done by the app and people that would like to see the story need an easy and obvious way of being redirected to the corresponding app-generated page. So hence is the question.
Is it possible for a Facebook app to post a maximally large (column-wide) photo on the user's behalf, so that when others (non-users included) click on the photo, it takes them to a specific page that is related to the app instead of zooming into the photo by default? If not, what would be the best workaround?
To get the maximum large photo on news feed, you should look into user generated photos, which requires two additional parameters you add to your open graph action to indicate that the user-generated photo should have maximum photo display on news feed and ticker.
Example OG POST:
https://graph.facebook.com/me/nyccookbook:cook?
recipe=http://www.yourdomain.com/pizza.html&
image[0][url]=http://www.yourdomain.com/images/my_camera_pizza_pic.jpg&
image[0][user_generated]=true&
access_token=YOUR_ACCESS_TOKEN
If the photo is not user-generated, then explicit sharing is an alternative to get maximum display size on news feed and ticker provided that you follow all the requirements and guidelines for explicit sharing.
when others (non-users included) click on the photo, it takes them to a specific page that is related to the app instead of zooming into the photo by default
This is not possible because FB users expect the behavior to zoom the photo in when clicking on it. If clicking on a photo launches an URL, it is a bad user experience because that is not what anyone expects when clicking on a photo on FB.
The best workaround I can think of is to edit the description of the image with a link to your specific page on your app, such that when a FB user sees the picture, they can click the link in the description to go where you want.
I don't see the answer I'm looking for, so hopefully someone can help.
I have a PHP script, which displays data from an SQL database. The dynamic elements are pulled in, essentially showing details of a job listing. On this page, I have a Facebook share URL.
Example:
<a title="Post on Facebook"
href="http://www.facebook.com/share.php?u=http://www.mywebsite.com/joblisting/details.php?job_id=1345488636.3750">
POST ON FACEBOOK
</a>
When the user clicks that link, they get the Facebook page to post this to their Facebook page. The page they are on pre-populates with my page title, page description, etc.
And if I have an image on my page, that becomes the default thumbnail image for the FB post. I also set a defualt Facebook image in my metatag, and that works too. I also added up to 10 other images on my page, so that the user could choose from 1 of 10 images as the default thumbnail. But...
I wanted to be able to let the user choose a thumbnail image from their desktop. Is this possible?
The image that's used in the Share dialog needs to exist somewhere on the web before the dialog is invoked, so you'd need to allow the user to upload it somewhere before popping the dialog in order to do what you're suggesting.
I have built several websites, and for some reason none of them will post to my wall anymore when I "like" a blog post, or like the site in general. (Using Iframe) Example:
http://madhatterulti.com/
http://www.reyniersaudio.com/blog/
The funny thing is, I had a friend try it, and it posted to his wall fine. Though, this person did not have timeline enabled, and I do.
Anyone have any ideas?
It appears the "like" appears in my "activity log". By default, the "like" is set to be "allowed on timeline". I am able to change this to "hidden from timeline". This setting implies to me that it should be showing up on the timeline.. yet it is not. Also, I can change the setting to "featured on timeline", but once again, this does not work.
It seems that the way the Like button works has changed (or not really!). I tried liking one of your blog posts and my own website and nothing appeared on the timeline. But reading the Like button introduction:
The Like button lets a user share your content with friends on
Facebook. When the user clicks the Like button on your site, a story
appears in the user's friends' News Feed with a link back to your
website.
And indeed, it appeared on my friend's news feed and ticker!
I suppose we cannot consider the timeline as the new news feed. Because it's not!
AND it seems that there are two ways a liked URL is going to appear on the user timeline which are
1) when the user has something to say, i.e when the user writes something along with the like:
2) if you click on the More Recent Activity block. And allow this activity to appear on your timeline.
Now maybe there are other cases (that I'm not aware of!) for a liked URL to appear in the user's timeline directly (maybe with custom Open Graph objects or a custom Facebook script that would decide for you?).
I linted one of your URLs and it states the the fb:admin and fb:app_id should be specified for better click-thru rates
Like Button Warnings That Should Be Fixed
Admins And App ID Missing: fb:admins and fb:app_id tags are missing. These tags are necessary for Facebook to render a News Feed
story that generates a high clickthrough rate
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.reyniersaudio.com%2Fblog%2Frecording-computer%2Frecording-computer-cpu-benchmarks-sandy-bridge-nehalem-and-bulldozer-processors-compared
I have timeline enabled and it did no post to my timeline at all. Strange huh?
EDIT
Based upon some comments from Roeland on other responses:
The funny thing is, this worked about a week ago. It WOULD post to my
timeline. In addition, if I go to my "activity log" it shows that I
liked something. It also supposedly lets me "allow it on the timeline"
which is the setting by default.. yet it does not show up on my
timeline
I'm wondering if it could have something to do with too many people reporting the stories as spam, or the app id was hijacked and used for spam purposes (or the domain/ip being marked as abusive, etc). Maybe this has caused Facebook to become more cautious when "showing" this liked content. ifaour has seen the content on his feed and timeline, however I could not get it to show.
My concern is that no app_id was specified and not admin was specified either. You can reuse the same app_id with many comments/like buttons (contrary to your assertion that you must have a new app id for each like button...not sure where that came from).