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

2016-03-20 Thread Nandakumar Chandrasekhar
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

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

2016-03-19 Thread jorrit787
As an aside, it looks like you're including CommonMiddleware twice. -- 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 an email to django-users+unsubscr...@googlegroups.com.

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

2016-03-11 Thread nav
Setting the key CACHE_MIDDLEWARE_ALIAS to 'default' fixes the issue Cheers, Nanda On Thursday, March 10, 2016 at 5:02:37 PM UTC-8, nav wrote: > > Sorry forgot to add the traceback I am getting: > > Internal Server Error: / > Traceback (most recent call last): > File >

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

2016-03-10 Thread Nandakumar Chandrasekhar
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)

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

2016-03-10 Thread nav
Hi, I am configuring the memcache backend to use with django and have the following things setup: CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': '127.0.0.1:11211', } } CACHE_MIDDLEWARE_ALIAS =