I would like to install Next Scripts: Social Networks Auto Poster, using wordpress and facebook. I did everything as described here
http://www.nextscripts.com/instructions/facebook-social-networks-auto-poster-setup-installation/
I am doing this for community in facebook. Everything was okey, but when I click "Authorize Your Facebook Account <=== Авторизировать ваш аккаунт ===",
I get this error:
Invalid Scopes: user_groups. 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
I authorized by a single login everywhere in facebook. The above link did not help me too.
Maybe somebody knows how to fix it?
user_groups got removed with v2.4 of the Graph API, you can´t use it in new Apps anymore. The replacement would be user_managed_groups. you may need to talk to the script creators about that, they have to change the permission.
Btw, "autoposting" scripts are usually not allowed, be careful with those and don´t spam.
Related
The custom domain wizard in firebase cannot go in the "verify ownership" stage. When I look at the web dev console I see a lot of 503 errors.
Is the spark plan not enough to have a custom domain ? Is the system broken ? Have I skip a step ?
For anyone else who ends up here, I did forward this on to Firebase Support.
They responded with 'That error appears when developers have a GSuite account. To solve the issue, reach out to your GSuite organization admin/owner to get the Search Console enabled. The following Google support article will provide the steps to enable the Search Console.'
Indeed, after enabling the Google Search Console, it did proceed to the Verify Domain step.
I got this error when I try to connect my wordpress site with Facebook API using SNAP auto Poster plugin.
Invalid Scopes: publish_actions, manage_pages, publish_pages,
user_managed_groups, user_posts, user_photos. 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
I already read this article in stackoverflow. And read this article in facebook about login permission. But still not find a clue on how to solve this.
I've also tried to remove the scopes one by one, but still facebook gives that error message.
The publish_actions permission has been removed. Apps that have already been approved for publish_actions can continue using the permission until August 1st, 2018. If you want to provide a way for your app users to share content to Facebook and Instagram beyond this date, we encourage you to use our Sharing products instead.
https://developers.facebook.com/docs/graph-api/changelog/breaking-changes#4-24-2018
I made a mobile app and used Firebase for backend and authentication. When I use firebase's built in email verification, the email always goes to the junk folder / spam.
Does anyone know how to fix this?
That's weird. Firebase made restrictions to avoid this problem. Check here
Spam filters normally look for these things:
Subject Line: looking for common words and phrases associated with spam.
Content: looking for suspicious links, low text to image ratios, and other spammy hallmarks.
Metadata: looking at the To/From/CC fields, the sender’s domain, and embedded code.
IP address: looking for IPs that have been flagged frequently as spam by both filters and recipients in the past.
More Info
Ill suggest using your own domain to send emails. You can check this article on how to do this. You will also get the extra benefit of looking more professional.
Hope it helps :)
Have a look at the headers of the received email message. Typically, Antispam tools use headers to add the detail of the scoring elements that lead to the message being flagged as spam. This will give you insights on why this happens since reasons can be multiple and cumulative (Title, content, DNS, DKIM, etc.)
I had the same exact problem,
The problem is that your sender name is noreply#project.firebaseapp.com
and that made all my emails going to spam.
What I did was to visit my console
https://console.firebase.google.com/project/project_name/authentication/emails
which is the template tab of the Authentication page.
Click on the pencil icon and click on the Customize Domain
enter image description here
Add and verify your domain.
That will solve the problem
I fixed this issue by only changing the project name.
Go to your firebase project > Project Settings > Main page.
There you'll see some public settings, change the name of your project, the default will show something like "project-(yourProjectId)", put for example "Project Name".
We running a wordpress website use google oauth for third-party social login. (via WP Social Login plugin.) Former engineer is leave, and we cannot have past google account credential.
We face a problem shows:
Error 401
Error: deleted_client
The OAuth client was deleted.
but we can only see old client id and secret from website admin panel.
I wanna to know,
if we set up a new google oauth application id/secret, will it make user crash from login website?
Or, is it possible for us to restore/retrieve former application ownership and make it live again?
This happened to me when I was working on an Add-On (maybe not completely related to this question but similar). I mistakenly deleted a Client ID that I thought we weren't using.
How I solved it:
Created a new project in Google Cloud
Associated the Apps Script project (Add-on) to this new Google Cloud project
Then I re-associated the App Script project with my previous Google Cloud project
The previous step will re-compile, create and associate the Client ID to the App Script project. It will contain all settings from the Client ID manually created and associated with your project in the code.
Maybe this will give some light to anyone having a similar problem.
Here use this link:
https://support.google.com/cloud/answer/6251787?hl=en
You have to reach google and they will help you out, this is the only solution you can do.
In my case, the simplest/only path (though certainly not ideal) ended up being to create a new Firebase project and start using that.
This of course can be problematic if you have a lot of data to move and/or a nontrivial data schema - say, with nested collections. For me, it was worth the effort to get unblocked from Sign-In suddenly failing to work.
... ah, OAuth fun
=======
If you are trying to make the new Client ID work .. though it's not a total solution, but after searching for a while, found this config option in Firebase console - where you enable Google Sign In.
So if you generate a new OAuth Client ID, update the ID & secret there.
After I did this, it went from a 401 error to a 400 mis_direct , which I think was step in the right direction.
I'm looking into an issue where a clients LinkedIn feeds on their website have stopped showing. Debugging the problem I've found that I get a 403 error shown below:
Member xxxxxx does not have permission to get company xxxxx
As the LinkedIn authentication process can be quite difficult to comprehend, I had a look online to see if others have had the same problem, and managed to find this. It suggests there have been recent changes to the LinkedIn API and users are now required to be the administrator of the company. What exactly does this mean?
From the very beginning we have simply been accessed the feeds by generating a url like this:
https://api.linkedin.com/v1/companies/xxxx/updates?oauth2_access_token=ACCESS_TOKEN
This has worked in the past. Do we need to regenerate the Secret and API keys?
Update
Looking at the announced changes here:
https://developer.linkedin.com/support/developer-program-transition
It suggests that the following endpoint will still work (which is exactly what I have):
/v1/companies/{id}
So I'm not sure what I'm missing.
is the access token generated by a account witch is Admin of that company page?
If not hen you will get 403.
The requester needs to be admin of that comapny page in order to get company updates.