SA Facebook Integration

[SA™]

i guess so they just want to veryfi your not a sheep or somthing

[Silvershark78]

OK it is working sometimes. it posts to other peoples feeds but not mine. where it says facebook user id in the admin panel, who's id do i use.

edit. app submitted

I can't get it to publish to the page or to my feeds. Ive tried to get it to post to the page in every which way i can set it up I am willing to bet it is because the app is not submitted. just a thought
If i hit the reccomend button, it posts to other peoples feeds but not mine.

[Silvershark78]

ok i tried to associate my account with facebook and got this error? any thought on that one. Is it maybe because I don't seem to have a ww.mysite.com/forums all I have is ww.mysite/forums/index.php

Given URL is not allowed by the Application configuration.: One or more of the given URLs is not allowed by the App's settings. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App's domains.

note that I never had the opportunity to do a canvas url

[Silvershark78]

OK well I just went ahead and posted all the images that it required and submitted it. I still cannot get threads to publish on my feed. sometimes they publish on other peoples feeds, sometimes not. And I cant get posts to show up on the page. The only thing that shows up is reccomendations and facebook comments from the bottom of the thread screen. And I still cant associate my accounts.

oh and I still dont know what it requires for facebook user id. who's do I use? and is there a way to get this stuff to post to my group instead of feeds, or both even

Thats all the questions I have. if you could help me out with these last few and trouble shoot with me, then it is all setup and ill be good to go

[Kindred]

if you want posts from the forum (as determined by the 4th(?) tab in the settings) made to your personal feed or your page feed, you set it in the 3rd(?) tab.

I don't know if this mod handles posting to a GROUP as opposed to a page

[Silvershark78]

Got this one too. This happened when I clicked "publish"
and thank you.

An error occurred. Please try again later.

API Error Code: 191
API Error Description: The specified URL is not owned by the application
Error Message: redirect_uri is not owned by the application.

[Silvershark78]

i know yo8u said that it is just .../forums/ but it doesnt seem to be working if you look at those few errors. are you sure I don't need to use .../forums/index.php? its not recognizing the domain from what i can guess

[SA™]

no one said use just forums/

use the full url
http://hyundaimotorclub.com/forums/

use that and see how it goes

[Silvershark78]

No you misunderstood me...lol...i did the whole thing LOL...sorry i confused the issue. What I was wondering is if it should also include /index.php...haha...no I got that part im good.
It seems to be rejecting one of the url's in some fashion. not sure why.

[SA™]

aha

so you get this error right

Given URL is not permitted by the application configuration.: One or more of the given URLs is not allowed by the App's settings. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App's domains.

Website with Facebook Login
     Site URL:

what url do you have in that part? in your facebook app

[Silvershark78]

well, it was hyundaimotorclub.com/forums. I added the forward slash at the end and hit save. I noted in the op that you said some of the settings require it to end that way. is that the problem?

EDIT*
ok tried to hit publish and got this error again

An error occurred. Please try again later.

API Error Code: 191
API Error Description: The specified URL is not owned by the application
Error Message: redirect_uri is not owned by the application.

[Kindred]

Redirect URL?   I think you entered something in the wrong spot...

[Silvershark78]

let me ask you this, what are the correct settings inside smf?
for instance, if I want to post to profiles, what facebook address do i use? Same if I were to set it to "page"
and what is the "user ID" for facebook inside smf? Could I have something wrong there?
I will post a screen shot of the settings inside the app un a few minutes

ok its going to be hard to read. Since I submitted the app for approval, it is blanked out and I cant change anything unless I cancel the submission. The approval is pending. see if you can read it

[SA™]

try removing the www. from he url's

[Silvershark78]

Leave the http:// or no?

[SA™]

Leave the http:// or no?

try removing the www. from he url's

leave it there

[jan.van.gent]

Hi there,

What's up with this update of facebook which is coming? Will SA facebook integration still works? Will there be an updated version?

Your app, .... has not enabled the migration for the July 2013 Breaking Changes.
Once you have confirmed your app is compliant or unaffected by the July 2013 Breaking Changes, set the migration setting to "Enabled" in the Geavanceerd section of the App Dashboard. This will apply the July 2013 Breaking Changes to your app and prevent you from receiving future alerts about these changes.
..., is currently using the following deprecated features:
Social Plugins (Like Button, Like Box) without absolute URL's in their `href` parameter.
These changes will be permanently enabled for all apps in 72 days on woensdag 10 juli 2013.

The following changes can be enabled/disabled using the "July 2013 Breaking Changes" migration until July 10th when they will go into effect permanently for everyone:
New APIs for comment replies
As announced here, this migration enables the updated comment APIs.

Social plugins will require an absolute URL in the 'href' parameter
Social plugins, such as the Like Box and Like Button, will require an absoute URL in the 'href' parameter.

Stream table will throw exception with invalid filter_key
Query stream_filter table for a set of valid stream filters. The stream table will throw an exception if called with an invalid 'filter_key' option.

Removing 'publish_checkins' permissions
Publishing a Checkin object is deprecated in favor of creating an Open Graph story with a location attached. You can also create a Post with a location attached using the 'publish_steam' extended permission.

FQL Checkin table 'page_id' change
We are renaming 'page_id' to 'target_id' for the Checkin table.

Removing 'version' field for Groups
We introduced 'version' field to indicate whether the group was created prior to launch of the current groups product in October 2010. We are removing this field as all Groups on Facebook are now the same version. This impacts both Group Graph API and Group FQL Table.

Photos will no longer return larger sizes than the uploaded version
'images' field in photos and photo_src table will no longer return image sizes larger than the original uploaded version of the photo.

Can not create multiple create actions for the same Open Graph object
We are no longer allowing multiple create actions for the same Open Graph object, as documented here.

Deprecating 'comments' field from 'stream' FQL table
We are deprecating the 'comments' field from 'stream' FQL table. Please select the 'comment_info' column to fetch the 'can_comment' and 'comment_count' fields (formerly called 'can_post' and 'count'), and use the comment table directly to retrieve the list of comments.

Removing 'xid', 'reply_xid', 'username' and 'comments' from 'comment' FQL table
We are removing the fields on the FQL 'comment' table that were used exclusively for legacy Comments Plugins -- 'xid', 'reply_xid', 'username' and 'comments'. We now treat comments the same across plugins and within Facebook. Please query for comment replies left on the plugin the same way as you would for other comments.

Removing 'count' from 'comments' Graph API connection
We are removing the undocumented 'count' field on the 'comments' connection in the Graph API. Please request '{id}/comments?summary=true' explicitly if you would like the summary field which contains the count (now called 'total_count')

The following changes will go into effect on July 10, 2013:
Mobile App Install Ads change
We are updating the Creative Spec parameter 'app_platform_type' to 'mobile_store'. The possible values for mobile_store are now "itunes", "itunes_ipad", and "google_play".

Conversion spec and tracking pixel ID changes
We are deprecating the use of 'tracking_pixel_id' when specifying the desire to track a conversion pixel in an ad. You should instead specify the pixel in the newly launched tracking_specs field. We are also deprecating the use of conversion specs in bid types that are not optimized for actions (e.g. CPM, CPC, and oCPM when no bid value is placed on actions). You should instead use tracking_specs to track conversions for these bid types.

Custom Audiences change
We have changed the targeting spec parameter 'excluded_user_adclusters' to be 'excluded_custom_audiences'. Additionally, the endpoint to create and retrieve your custom audiences is now: https://graph.facebook.com/(act_adaccountid)/customaudiences.

Accessing link stats change
App access tokens will be required for accessing the link_stat FQL table. App access tokens will also be required for retrieving data from Graph API endpoint for link stats, ie: https://graph.facebook.com/?id=http://example.com.

Graph API search changes
App access tokens will be required for all search Graph API calls except Places and Pages. Search for application will no longer be supported.

Open Graph apps using custom actions for fitness, books, movies, and TV
As announced in March, any apps that previously used custom actions to represent this type of sharing will need to move common actions by July 10, 2013.

Removing 'page_friends_of_fans' metric
We are removing the metric: 'page_friends_of_fans' from the Insights Dashboard and the Insights API.

Removing the ability to "Select All" or "Pre-Select" for Requests
As part of our efforts to improve user sentiment, we have updated our platform policy so that apps may not offer a select all option or pre-select multiple recipients to receive requests. Other Request dialog functionality will remain the same.

[SA™]

i think most of it would still work but other parts will need updating wouldent take too long to get it upto spec 

[Silvershark78]

OK I removed the www. I get this when I try to associate my account-

Given URL is not allowed by the Application configuration.: One or more of the given URLs is not allowed by the App's settings. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App's domains.

and I still get this when I try to publish-

An error occurred. Please try again later.

API Error Code: 191
API Error Description: The specified URL is not owned by the application
Error Message: redirect_uri is not owned by the application.

Any other ideas. Ive done everything I can think of. I have no clue what the issue is. Ive followed every direction given to the T. Help! LOL

[SA™]

do you want me to take a look at your app settings for you?
would reqire you adding me as a developer of your app you can remove me after

i kinda know what you have done you maybe did a few more things than i said you didnt realy need to sub,itt your app just need to set it up to use the api