esse's profile - activity

Tags are not correctly displaying in side bar. Only the first tag is displayed, while all the rest are in the html they are not visible. I inspected them via my browser and I can not figure out why they are not appearing? Any suggestions or others that have had similar issues would like to hear.

outside of some of my own mistakes no :) I have installed askbot from both the pip install askbot and from the python setup.py develop via a virtualenv. In either case you will need to run pip uninstall django after install then run pip install django=1.3.4. If you install via python setup.py you can also modify askbot/__init__.py REQUIREMENTS to have 1.3.4 as the required django.

I have been reading the Django documentation lately and I notice that sometimes they have the SessionsMiddleware before CommonMiddleware, despite their documentation that I linked to. Still not 100% sure about it all.

I noticed that the order recommended by askbot for MIDDLEWARE_CLASSES has:

'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',

whereas django documentation and default settings has:

 'django.middleware.common.CommonMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',

If i change the order to match what Django recommends it takes the site down ... the ordering of middle ware always confuses me a bit, but I am wondering why the difference and if it has any side effects for other functioning?

I am running askbot 0.7.44 with django 1.3.4 and it appears to be working well.

I have integrated askbot into a pre-existing project. In that project i have MEDIA_* variables set as follows:

MEDIA_ROOT = os.path.join(PROJECT_DIR, 'media')
MEDIA_URL = '/media/'

The issue is that with those settings if I try and upload an image with a question in askbot it attempts to write it at <project_dir>/media/

I would rather it write to <project_dir>/askbot/upfiles as it would if I used the default settings askbot generates:

MEDIA_ROOT = os.path.join(os.path.dirname(__file__), 'askbot', 'upfiles')
MEDIA_URL = '/upfiles/'

I know that I can create new variables and use those, but I was wondering if there was an easy way with askbot to have askbot use the path it wants to go to upfiles and the rest of my project to use the paths I have already defined.

I saw this question but ASKBOT_FILE_UPLOAD_DIR does not change things, and I noticed that django.core.files.storage.get_storage_class is used in store_file so it is using the MEDIA_ROOT and MEDIA_URL there. Not sure if there is a nice way to have askbot point to a different location.

Thanks for pointing me in the right direction. It was a combination of python path and Apache mod_wsgi variables not being set correctly. Things are working well so far. Thanks.

Any suggestions?

The apache log states mod_wsgi compiled for python 2.7.2+, my system python is 2.7.3. I have libapache2-mod 3.3-4build1 installed.

When running via django runserver it appears to work fine. That is I have not had any hanging issues while running via django server.

I have been working on integrating askbot into a project I am working on and all has appeared to work well while running it through Django during development. I deployed the site on my server running apache and all appeared to work until I tried to ask a question. When asking a question the site page just hangs, with no response and the rest of my site hangs.

I logged into postgres and performed a couple select statements on the DB just to make sure things were working for that, no problems.

I edited my profile through askbot to make sure that posts were taking place, no problem.

But if I try and "ask your question" it freezes my whole system!!!!

Any ideas?

I am having the same issue while running it through django server, have not tried to deploy it yet. I am running this on Ubuntu 12.04 with python 2.7.3 and have tried it with both Django 1.3.1 and 1.3.4 and get the same errors.