login page keeps reloading
I have a problem with my login/signup page, it keeps on reloading, i think it's something wrong with the javascript. try it here , just go to the signup page.
3 Answers
- Sort by
oldest newest most voted
1
Facebook login does not work, I think that in your case callback url entered into Facebook app is incorrect.
Can you tell what it is? Go to your app setting in your facebook account and check your "site url" parameter.
I've tested google and simple password logins on your site. Both work.
Comments
I have this issue too. My facebook login works (I think) because I created an account through Facebook on my site.
I disabled facebook login and this still happens.
In fact, I disabled all providers and this still happens.
This is a critical bug. I had the same issue. I was unable to login at all using regular email. Whenever I used to login it used to come back to the same page. Currently I'm exploring the codebase and will update soon on this. ;)
Check this - http://askbot.org/en/question/8345/unable-to-login-to-my-askbot-site-as-admin/
I have the same issue. Cleared all cookies and go to /account/signin/ still get the constant refresh.
1
I just cleared my cookies, and that seemed to clear things up. My guess is that it has to do with a conflict between the cookies generated when running the test server on port 8888, and the cookies generated on the production server.
This would explain why we administrators would have the problem but not other users we send to our site to check things out.
EDIT: Sorry folks, that didn't fix it after all---or at least, it is also related to Facebook logins. I tried to add Facebook logins back, and once I added that key to my login set, the reloading started again.
Comments
the reloading code checks if both Facebook keys are there. see provider_javascript.html in skin/common/template/authopenid, so you have to remove one of the FB keys to prevent autoreload
Oops, made a comment response in a wrong place - see the one under my answer. Thanks for pointing this out.
0
Will this error be fixed in the next release? I guess the next release will be the django 1.4 compatibility release.
Comments