-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oauth2-client-configuration error #276
Comments
Hi @hilalh are permalinks working properly? |
Also, I see this template is using Nginx. It might be something related to that. The plugin declares some custom routes, |
I tried to repro but I cannot installe it, I am having this error |
I suspect Nginx as well but I couldn't get to the settings of it through the repo I used. |
When I try to setup it manually (no internet connection) everything goes well until the migration stage of the admin user. When I am asked to choose a password I get the following error (top one only) |
That is a real bug :P I will try to take a look tomorrow. In the meantime, can you check if there is any connection created by the plugin (it should be named Also, can you share your account name? |
do the following, go to the configuration under the basic tab, and make sure there is no client_id configured. if there is one, delete and save and try again |
That worked out! Make sure to include this in the documentation as it could be confusing. I deleted both the client secret and client id and went through the manual wizard again. |
The thing is that when the client_id is configures, it assumes you are trying to update the api token, but I agree it should be more explicit. Thank you for the feedback and sorry for the trouble. |
Hello, I have my WordPress setup on Heroku using https://github.com/xyu/heroku-wp as my template. I've been getting this error whenever I am trying to go through the social setup wizard
![image](https://cloud.githubusercontent.com/assets/3894104/22180883/c4fef6b8-e032-11e6-9965-e1255a72fbcb.png)
The text was updated successfully, but these errors were encountered: