I am trying to connect Social Connected to Facebook using Sitecore 8's (rev 5) Social Connected functionality (we are unable to use Komfo for budget reasons) however i've had a few issues. I was following this walkthrough from the Sitecore documentation site.
I was getting this error when trying to connect a Facebook account:
"Invalid Scopes: read_stream. This message is only shown to developers. Users of your app will ignore these permissions if present.
Please read the documentation for valid permissions at: https://developers.facebook.com/docs/facebook-login/permissions"
So I went ahead and did some reading and found this Stack Overflow question
which from the information there I was able to find that the particular permissions that Sitecore is asking Facebook for are deprecated.
From there I changed the permission from publish_stream to publish_actions and was able to give Sitecore the permissions it needed in Facebook. The problem is that Sitecore wanted this to be done in the browser window it provided, and so it did not acknowledge that the permissions were set in Facebook, even though they were.
I then tried to manually add a social media account from a template, hoping to input the data it would need manually now that it had the appropriate permissions. However after doing this Sitecore then started to throw an error when adding other social media accounts:
"The Social Connected Module is not configured.
There are no social networks available with applications that you can use to create an account."
Social connected is in fact configured, and before making these changes I was still able to add other social media accounts. Recreating the Applications solves this issue but puts me back at square one.
Any ideas on how we can rectify these issues would be greatly appreciated.
I managed to get around this issue. First, in the content editor, I created a Facebook application under System/Social/Applications. Then, I created a social media account under System/Social/Accounts for LinkedIn and then duplicated it, changing the configuration to suit Facebook.
Once I did this I was able to post text posts to Facebook and Twitter. I was not able to get image posts working, and by this time, we abandoned the idea.
It's worth noting that Sitecore continued to push us toward Komfo. It's pricey and is essentially an iframe placed in the Sitecore UI with limited functionality. There are other tools out there that will give you similar analytics features for a fraction of the price.
It's also worth noting that the social connected functionality in Sitecore 8.1 appears to ask Facebook for the correct permissions, so you wont have this issue. I cannot vouch for its functionality in terms of actually posting as I haven't fully tested it.
Fortunately, Facebook permissions are only string and you can easily modify it using reverse engineering. It was done for Sitecore 7 version, but I think same approach will work for Sitecore 8.
Also, you are able to create a ticket in Sitecore support and they will provide you hotfix for this issue.
Related
in order to approve your app’s continued operation on our platform.
Platforms affected: Connect URL.
Developer Policy 1.2: Build an app that is stable and easily navigable.Some common violations of this policy include:
- Broken Facebook integration (e.g. broken share, like or comment functionality)
- Broken user experience in the app (e.g. app has broken links or user interface failures)
My app:
Using https://www.npmjs.com/package/hellojs v1.18.8 to query user info from facebook.
The request URL:
https://graph.facebook.com/v2.9/me?fields=email,first_name,last_name,name,timezone,verified&access_token=.....
calling out hello.js
hello(auth.network).api('me').then(function (json) {
App has no share, like, comment functionality and not really any user interface. Just our page offers ability to fill some data with facebook and then it remembers you with cookie.
Anyone has similar e-mail and what to do?
Our app does not use share, like or comment functionality neither do we provide any user interface for users (only the o. We are using Facebook to prefill some user data on our site.
Have the same unclear message "Platform affected: Connect Url".
I asked for a more detailed answer and received an answer the next day:
Thank you for your response.
Facebook periodically reviews the websites and applications which are on it. Your application is in its review process currently. We are required to test the Facebook login functionality in order to conclude the review in totality. However, we are unable to do so.
Unfortunately, we have not been able to locate a Facebook integration (Login, Share and Like) on your submitted platform. To help us conclude the review process, could you kindly share the details regarding the location of a Facebook integration and how to navigate to it on your website URL.
This review is essential to Facebook as we want to offer the best experience to users as well as developers like yourself. Please help us in bringing your application into compliance by working with us.
Alternatively, you could aid us by sending us credentials of a test user which is already registered and connected to an FB account within the app. You can get all the information related to creating a test user here - https://developers.facebook.com/docs/apps/test-users.
Please feel free to get in touch with us regarding any doubts or queries you might have.
Thank you for your patience and cooperation.
Looking forward to hearing from you.
My app contains the functionality of a facebook login. I made an instruction and a test user of the application so that Facebook employees could test the functionality used in my application.
Normally they write down what is wrong and explain how to fix it. If you are not sure you can reply them back and ask how to fix it. I manage to fix my issue which was similar to the one explain below by emailing facebook.
https://technuisance.com/facebook/facebook-policy-warning-for-app-solved.html
I got the same message from Facebook two months ago. In my case, I didn't find a solution in time and Facebook penalize me by deactivating the app.
Therefore, you must attend to it if you do not want the same to happen to you. Facebook uses software similar to this to check for failures on your site and assigns a score according to its performance. That's why they send you such a generic message.
I suggest you use PageSpeed Insights to receive a report on the performance of your website. In addition, the platform gives you suggestions for optimization and improvement; Surely there you will find some clue of what may be failing.
I've got incoming messages working via webhook, but what I cannot understand is how I make this available to other users.
I run a SaaS that's used by many different organisations, so I want to be able to give those organisations (who each have a subdomain on my domain) the ability to 'connect to facebook messenger', so that all of the messages to their facebook page (whatever that may be), come into their portal view on my platform.
The only way I can see this working, is by getting each user to register as a developer, and go through all the set up that I did to get my test example working.
But I must be missing something? What's the workflow to enable this, simply, so that users can connect in this way?
You can have multiple Facebook pages connected to your single Facebook app. But you would require permissions from Facebook for that. You can read about permissions here: https://developers.facebook.com/docs/facebook-login/permissions/
I'm looking at setting up an Instagram app so I can push content from my app directly to Instagram. I'm already doing this for Facebook, LinkedIn, and Twitter.
I know that Instagram is in the middle of moving to the Facebook Graph API, and it seems like there are several barriers to even start developing an app.
At the top of the Getting Started link there's a blurb stating that I need to undergo "Business Verification" to use the Instagram Graph API. Do I need to do this in order to use these endpoints in sandbox mode? (Edit: I believe this must be done in order to test the non-beta aspects of the API) In addition, the Content Publishing API seems to be locked down even further, requiring parternship with either Facebook or Instagram, and neither are accepting new applications.
Is there some way to test this in sandox mode without becoming a partner?
(Edit: Testing your app Suggests that I must do business validation in order to use the non-beta aspects, and there's no permission for publish_content, leading me to believe that I must be a business partner to even test this feature. Can anyone confirm?)
Januray 26, 2021
The Content Publishing beta has ended and all developers can now publish media on Instagram Professional accounts. Refer to the Content Publishing guide for usage details.
https://developers.facebook.com/docs/instagram-api/guides/content-publishing
I have added community applications to our Dashboard by clicking on Add Apps(home page), and assigned to the people. its working fine, people able to access Community Software, but whenever we are intended to create our custom app(Jive demo sandbox) from admin panel and assigned people its not working as expected. even the admin not able to access the app it is showing message "Sorry, you can't access Jive Software because you are not assigned this app in Okta".
i have followed the integration process from
http://developer.okta.com/use_cases/integrate_with_okta/
please help me that i am missing any integrations or configurations
There is not sufficient information in this question to be able to answer. Have you tried reaching out to Okta Support? They should be able to check your configuration with your permission and help you with it.
I have done much searching but not able to find a solution.
Trying to get my Twitter to Facebook feed setup but getting this error:
"Facebook reported an error. The error has been reported to our engineering team. Please try again as it might be a temporary problem"
From what I can gather it may have something to do with an old account that has been deleted, but I have no idea how to resolve this and nor do a lot of other people.
First up: this is not a programming question since it's not related to the Twitter API but to the Twitter interface. Therefore, it's actually to be regarded as "Off-Topic".
To give you a helping hand nevertheless:
What you are describing is a known bug Twitter bug. Check https://www.facebook.com/help/community/question/?id=110412992466716 and https://dev.twitter.com/issues/998
The problem comes up when your Twitter account was previously connected to another Facebook account that you deleted/deactivated without removing the Twitter app first. Now that you try to connect to a new Facebook account, Twitter still tries to authorize using the old credentials of that other account.
Currently, your only hope is to ask Twitter to manually remove the old account credentials from your Twitter profile's backend. From what I've been reading, Twitter frequently fails being cooperative in that point... you can only ask and hope someone at Twitter is able and willing to manually correct their bug.