Re: fb login issue

The version of social auth you are using is ancient, and most probably not work anymore. try: > social-auth-core==1.7.0 > > social-auth-app-django==1.2.0 > > -- Best Regards, Christian Ledermann Newark-on-Trent - UK https://uk.linkedin.com/in/christianledermann https://github.com/cleder/

Re: fb login issue

Somewhere in your code before signing in, you're expecting an integer value in a variable, but it is in fact None. Adding None and an int will get that error. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and

Re: fb login issue

Hi Mikhailo, I'm using *python-social-auth==0.2.21, *python 2.7 and django1.11 On Fri, Jul 20, 2018 at 4:06 PM Mikhailo Keda wrote: > show full traceback, what packet are you using for fb authentication? > what version? What version of fb api are you using? > > -- > You received this message

Re: fb login issue

show full traceback, what packet are you using for fb authentication? what version? What version of fb api are you using? -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send

fb login issue

Hi all, I am signin using facebook authentication in local using SSL for https. i'm getting the below error. *TypeError at /complete/facebook/* *unsupported operand type(s) for +: 'NoneType' and 'int'* -- You received this message because you are subscribed to the Google Groups "Django

Re: tracking down a login issue (django 1.2)

On Tue, Sep 14, 2010 at 3:09 AM, Cindy wrote: > OK, I have figured this out myself -- is there somewhere I should put > in a bug report? Almost certainly yes -- but based on the details you provide, it isn't clear that the right place is Django's Trac instance. Django doesn't

Re: tracking down a login issue (django 1.2)

OK, I have figured this out myself -- is there somewhere I should put in a bug report? It seems that if you are using the ldap authentication backend, setting AUTH_LDAP_FIND_GROUP_PERMS can result in generating sql that tries to look up group membership in an empty set. When this value is true,

tracking down a login issue (django 1.2)

I'm not completely certain what is going on here, but somewhere in the authentication stuff, a bad MySQL query is being generated: ListType TupleType args [] charset 'utf8' db exc exc_info query '\n SELECT ct.`app_label`, p.`codename`\n FROM `auth_permission` p, `auth_group_permissions` gp,

tracking down a login issue (django 1.2)

I'm not completely certain what is going on here, but somewhere in the authentication stuff, a bad MySQL query is being generated: ListType TupleType args [] charset 'utf8' db exc exc_info query '\n SELECT ct.`app_label`, p.`codename`\n FROM `auth_permission` p, `auth_group_permissions` gp,

Re: Login issue

Hi Bret, Can't see that anyone else has responded to this. Bret W wrote: There are many times when I can enter a username and password, click the "login" button, and get the username/password don't match error. The error page (/accounts/login, using example template from docs) automatically

Login issue

I have a login form on my homepage: Username: Password: The homepage uses template fragment caching, but this block is not cached (although I don't know why it couldn't be). I'm not using CSRF middleware. There are many times when I can enter a username and password, click the "login"

Re: 0.96 login issue with cookies

No, the cache was off all the time. On Oct 19, 8:44 am, web-junkie <[EMAIL PROTECTED]> wrote: > Did you activate the cache in Django? I once discovered an issue with > that.. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the

Re: 0.96 login issue with cookies

Did you activate the cache in Django? I once discovered an issue with that.. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com

Re: 0.96 login issue with cookies

I got the same problem 2007/10/18, Jarek Zgoda <[EMAIL PROTECTED]>: > > > Robert Šmol napisał(a): > > > I have HomePage with login bar with a form for user to log in. I use > > django.contrib.auth.login to log user in. When I enter it from the > > /accounts/login/ page it works ok. However

Re: 0.96 login issue with cookies

Robert Šmol napisał(a): > I have HomePage with login bar with a form for user to log in. I use > django.contrib.auth.login to log user in. When I enter it from the > /accounts/login/ page it works ok. However trying to login from homepage > is not working. I have to do it twice (always). On

Re: 0.96 login issue with cookies

Hi Robert, I had the same problem. Since I switched from FCGI to mod_python the problem disappeared. I still don't know what was the _real_ reason for that. However, I noticed it was possible to get rid of the problem temporarily by clearing the browser cache (or cookies). I bet it was caused by

0.96 login issue with cookies

Hello, I have HomePage with login bar with a form for user to log in. I use django.contrib.auth.login to log user in. When I enter it from the /accounts/login/ page it works ok. However trying to login from homepage is not working. I have to do it twice (always). On django# there were more users

login issue

Hi, I just read chapter 12 in djangobook.com on authentication: http://www.djangobook.com/en/beta/chapter12/ I am creating a new user in response to a registration form I've made, doing something like this: from django.contrib import auth from django.contrib.auth.models import User def