-
Notifications
You must be signed in to change notification settings - Fork 174
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
Github signup does not work #98
Comments
@synox Is this still the case? |
When you refresh the site, have you been added to the signatories page? |
No, still not on the list |
@jroper Any ideas? |
Hi @synox, I can only reproduce this if I try to access the website using https, GitHub sign in redirects you back to the http site which is not allowed to access the window opener because it was https. Doing so however requires ignoring an SSL error saying that the domain name is wrong. Did you do this? Or do you plugins that might be automatically switching you to https? We don't support https on reactive manifesto at the moment. Other possibilities include using a different domain name to access the site (though I'm not sure how you could have done that accidentally), having a JavaScript disabled (though this would probably have prevented you from even attempting to log in in the first place), or having some weird browser security configuration that's blocking child windows from accessing their opener. If it's none of the above, then can you answer the questions below:
Cheers, James |
I did some more testing. I did't have a "Name" in my Github Account. When I add a name in the profile it works! Does a missing name trigger an error? |
Thanks @synox, that would likely explain it, our parsing of GitHub profile data assumes that the name field will always be present. I'll update it to make it optional, and I'll also update the UI so that it renders any errors encountered at this step, this will make diagnosis of similar errors easier in future. |
Issue fixed here: reactivemanifesto/website-manifesto@e4af5af Also, now error reporting is better, this is the message you would see now (if I hadn't have fixed the bug): |
I get redirected to an empty page after github auth.
The text was updated successfully, but these errors were encountered: