JStarcher's profile - activity

See these threads: http://askbot.org/en/question/9813/integrityerror-when-updating-user/ and http://askbot.org/en/question/11848/anyone-else-see-update-user-in-admin-causing-errors/</p<>>

This tells us that memcached is running, 29483 is the process ID which isn't useful in this case. Check my post below and accept the answer if it is helpful. Cheers

This is possible using SQLite and checking the database file into git. I would advise against using thew SQLite database for anything other than development though.

This is very easy to accomplish with a Django module. Checkout the Django Blog tutorial on the Django website. You can also integrate with the Django admin for CMS functionality very easily.

I've seen this error a few times and usually its because of an import error somewhere. Based on my experience is unlikely the error has and thing to do with SMTP. I also saw this when my database was misconfigred have you made any code or configuration changes recently?

Glad this helped. Would you mind accepting the answer?

Your memcached.sock file is very likely not in that location. You can see where it is with this command:

netstat -an | grep memcached.sock

If you don't see any results then your memcached server is either not running, or its listening on a TCP port. Check if it's listening on TCP with:

netstat -an | grep 11211

If you see a result there then you'll need to change your settings to:

CACHES = {
  'default': {
    'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
    'LOCATION': '127.0.0.1:11211',
    'TIMEOUT': 18000,
    'KEY_PREFIX': 'askbot',
  }
}
CACHE_TIMEOUT = 18000
CACHE_MIDDLEWARE_ANONYMOUS_ONLY = True

EDIT: Actually, the settings.py example is completely incorrect anyway on newer versions of Django. You'll need to configure it like this in newer versions: CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': '127.0.0.1:11211', } }

I noticed that in settings.py there is a link to very old Django 1.1 docs: docs DOT djangoproject DOT com/en/1.1/topics/cache/

In those docs the recommended python bindings module is cmemcache, which has been retired since 2009 and no longer recommended.

It would be a good idea to upgrade that to 1.5 to keep people from getting confused.

There is a newsletter signup on the homepage (askbot DOT org/en/questions/) in the right rail.

I ran into this error while installing a fresh copy of Askbot 0.7.49 on Postgresql. Has anyone else had this issue? I ended up logging into /admin and creating the site manually. Before doing so, I would see this error when trying to change any setting including baseurl.

I'm having the same issue. I skipped over it and haven't found any side affects yet.

This would be an amazing app for many people. I'd love to have this.