okay, so i was wrong that it's not supported; but i agree with the sentiment here; it'd be nice if this worked out of the box by default.

I don't think it's possible today to use a manual avatar...

Any thoughts on recommended 'minimum' system requirements? how much memory / disk space?

And MANAGERS

What does the 'ADMINS' option in settings.py actually do?

i agree; nice to have, but not priority. :)

It's possible to set only 'posts per page' to 10 30 50; some hard coded value.

It would be nice if more posts were just automatically loaded as the user scrolled through them and got close to the bottom.

:)

Something like this perhaps?

http://palewire.com/posts/2010/11/07/django-recipe-twitter-style-infinite-scroll/

What about adding to User Profile, users Interesting Tags and Ignored tags (optional to share/not share in settings?)

eg, so other users can see the tags that another user has added to his Interesting Tags and Ignored tags lists.

Why? so people can know what tags another user is following and therefore what tag they can add to their post to raise the chances that it will be seen by the target reader.

Have you tried 'Interesting Tags' on the right hand sidebar? Make sure your mail is set-up on your server. Set mail delivery options in user profile. I'm think it works so that when you have an interesting tag set and your settings are right, you get a mail when posts with that tag get updated/created.

I've seen similar (exception None has no attribute get_snippet) issues after clearing the 'awards' table through the admin site and then opening up user profile page. But i can't seem to reproduce it again... just fyi.

I'd like to be able to disable the default 404 template 'Other Things to Try' section all together (or customize), because it hard-codes a link back to external site: google search. The ask bot service i'm working on lives within a vpn intranet, eg, google doesn't index the site anyway.

Obviously, it's possible to simply update the template code manually, which i've done, but perhaps it could be made possible to diable/enable this 'feature' (customize the 'Other Things to Try' section of 404) like is possible with the header/footer settings options?

Fixed the importerror... silly me. It's not cachedb but cacheddb... now checking if this fixes the other issue. Nope. Doesn't seem to make a difference.

maybe i know what it's about? I changed SESSIONENGINE = 'django.contrib.sessions.backends.cachedb' to SESSIONENGINE = 'django.contrib.sessions.backends.cache' because when i have the former (cachedb) set i get a traceback ImportError: No module named cache_db

If i hit 'start over' (?start_over=true) then click on the same tag that i was previously clicking on and seeing the 'no results' page, i get results as expected.

I'm definitely seeing it though even when running 'runserver' mode. All i do is click randomly the various Interesting Tags i have set-up and after a few page loads, i start seeing only 'You can expand your search by starting over'

nothing special. http://pastebin.com/1Cv7EHgB

Yup, seems to work for me. Sweet!

Just wanted to point out some Deprecation warnings i'm seeing in the logs that i didn't see anyone else point out yet. I suppose these are 'known issues' already?

[Tue Dec 13 06:12:39 2011] [error] /usr/lib/python2.6/site-packages/django/db/__init__.py:60: DeprecationWarning: Short names for ENGINE in database configurations are deprecated. Prepend default.ENGINE with 'django.db.backends.'

[Tue Dec 13 06:12:39 2011] [error]   DeprecationWarning
[Tue Dec 13 06:12:41 2011] [error] /usr/lib/python2.6/site-packages/django/contrib/auth/models.py:393: DeprecationWarning: The user messaging API is deprecated. Please update your code to use the new messages framework.
[Tue Dec 13 06:12:41 2011] [error]   category=DeprecationWarning)

[Tue Dec 13 06:12:41 2011] [error] /usr/lib/python2.6/site-packages/django/core/context_processors.py:27: DeprecationWarning: The context processor at `django.core.context_processors.auth` is deprecated; use the path `django.contrib.auth.context_processors.auth` instead.

[Tue Dec 13 06:12:41 2011] [error]   DeprecationWarning
[Tue Dec 13 06:12:42 2011] [error] /usr/lib/python2.6/site-packages/django/db/__init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated; use settings.DATABASES instead.

[Tue Dec 13 06:12:42 2011] [error]   DeprecationWarning
[Tue Dec 13 06:12:42 2011] [error] /usr/lib/python2.6/site-packages/django/db/__init__.py:60: DeprecationWarning: Short names for ENGINE in database configurations are deprecated. Prepend default.ENGINE with 'django.db.backends.'

I'd like to be able to 'subscribe' to tags too so i'm notified by mail when posts are created/updated that also contain specific tags. I'll test the 'interesting tags' to see if this is what i'm looking for, which it seems it should be.

Using kerberos authentication makes it unnecessary for users to sign-out. Users either log-in or they are denied access to the site. Given this set-up, 'sign-out' has little use. It would be nice to have an option available in settings that would allow me to 'disable' sign-out option (from showing up on templates). Temporarily, i've just manually commented out the links in the template. ./templates/widgets/user_navigation.html

I see the issue when SESSION_ENGINE = 'django.contrib.sessions.backends.cache' is set and when it is not. I'm running with apache+wsig+memcached. In fact, i just tested using the built-in 'runserver' mode and i'm seeing the issue there too, which if i understand correctly, doesn't use cache at all?

Any suggested solution? When i set CACHE_TIMEOUT = 0 on my deployment (apache+wsig+memcached) i'm still seeing the issue?

Try this:

Go to http://askbot.org/en/questions/

Add several different 'Interesting Tags' to the right side bar (eg, bug accessibility login) if you don't already have some.

Then just quickly click through each of them randomly (one click per complete refresh).

eg, start by clicking 'bug' tag (refreshes url to http://askbot.org/en/questions/?tags=bug) then click 'accessibility' tag then click login, and repeat over and over at random.

Eventually, you'll get stuck. Either the page will continue to show the contents related to the previous tag you had selected (not the current) or you'll see simply no results and the message 'You can expand your search by starting over'

It seems to work the first few times, but something eventually gets confused... cache?

I saw this first on my local install, where i'm running memcached. I tried disabling cache (or rather, setting CACHE_TIMEOUT = 0) but i'm still seeing the issue.

Whatever the function 'start over' (url .../questions/?start_over=true) does seems to fix the issue.

I have "Maximum number of tags per question" set to 10 in settings.

But when i write a new question, i see

"Tags are short keywords, with no spaces within. Up to five tags can be used."

"five tags" where I believe it should be 'ten tags', given my settings.

It it possible to include tags with spaces? I believe the answer is no... but i'd like to be doubly sure.

When i update a user profile to include date of birth, the profile page shows

'age: 27 age unit'

Probably 'age unit' should be 'years'

Doesn't seem possible to disable 'share via mail'? ie, i'd like to remove the entire line "Know someone who can answer? Share a link to this question via email." and i would think by disabling all share options this would happen, but i can't find how to disable the 'by mail' option.

The result? 'impossible to use livesettings without memcached' ... we found it out on our own, but the livesettings author confirms it to be the case too.

https://bitbucket.org/bkroeze/django-livesettings/issue/32/impossible-to-easy-use-livesettings

"If the cache backend configuration is "locmem", it works good only with development server. For production with multiprocess deployment it is necessary to use memcached, otherwise old values can be randomly used so long, until the CACHE_TIMEOUT expires. It is very annoying if a change have been saved and shortly other change should be submitted, because the old vaue can remain in the form and be resubmitted back."

There are probably a few quirks that will need to be ironed out, since when this is enabled globally, you log in automatically... so for example, 'log out' doesn't work as expected... you just stay logged in :) but yes, otherwise, it seems to work like a charm.

mod auth kerb

I'll send you my settings, but yes, i used askbot-set.

https://bitbucket.org/bkroeze/django-livesettings/issue/21/values-are-not-saved-in-the-database-in

I'm seeing this issue too when trying to update settings. Did you ever find a root cause? I have a fresh install (followed instructions from your docs) , on a freshly installed system. Sometimes i don't see the error at all, but when i try to 'save' settings, the page appears to refresh but the setting doesn't appear to have actually changed... not sure what's going on, it's late but just wanted to see for now if you've seen this again since this question came up a while ago...

Seems it works with Django 1.3 out of the box, in fact! :) With the right apache config + instructions from django docs. eg,

https://docs.djangoproject.com/en/dev/howto/auth-remote-user/

and in your httpd/conf.d/askbot.conf

...

AuthType Kerberos

AuthName "YOURDOMAIN.COM Kerberos Login"

KrbMethodNegotiate On

KrbMethodK5Passwd On

KrbAuthRealms YOURDOMAIN.COM

KrbVerifyKDC off

Krb5Keytab /etc/krb5.keytab

KrbServiceName HTTP/YOURDOMAIN.COM

require valid-user