Re: Unable to parse connection string: "" when using django cache

Thanks I had not caught that but I am not sure if that is the issue. On Thu, Mar 17, 2016 at 7:39 AM, wrote: > As an aside, it looks like you're including CommonMiddleware twice. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django users" group.

Re: Unable to parse connection string: "" when using django cache

Sorry forgot to add the traceback I am getting: Internal Server Error: / Traceback (most recent call last): File "/Users/nchandrasekhar/PycharmProjects/horizon/.venv/lib/python2.7/site-packages/django/core/handlers/base.py", line 88, in get_response response = middleware_method(request) Fi

Re: Setting an unusable password on an existing user

: On Sat, Sep 22, 2012 at 3:18 PM, Nandakumar Chandrasekhar wrote: Thanks Andrew but I have a requirement where I have to programmatically set it to an unusable password based on a particular condition. Andrew's given you the answer - it's just not clear that you've understood wha

Re: Setting an unusable password on an existing user

Thanks Andrew but I have a requirement where I have to programmatically set it to an unusable password based on a particular condition. I know this is a rare requirement but in the context of the application I am building it makes sense. :-) nav On Friday 21 September 2012 12:22 PM, Andrew M

Re: Setting an unusable password on an existing user

Thanks Paul, I have tried this on the Django shell and works for me as well. Since I am using some third party software to do social site authentication I might have made a mistake and not accessed the actual django user object. Thanks once again. nav On Friday 21 September 2012 03:17 PM,

Re: Django development running on 127.0.0.1:8000 not accessible from same machine

Chris, Thank you for your email. I had cleared my cache quite a number of times before. What is interesting is that if I start a new Django 1.4.1 the browser finds the server running at 127.0.0.1:8000 and says it worked. The application I am working on however still redirects to www.127.0.

Re: Django development running on 127.0.0.1:8000 not accessible from same machine

Hi Jirka, That does not seem to be the case. I set rhe proxy server settings to no proxy and it still prepends a www in front of the IP address. I could investigate this further but I am little pressed for time at present. Thanks, nav On Tuesday 28 August 2012 10:39 AM, jirka.vejra...@gmail.