If you can file a feature enhancement request detailing how your backend
works and what you need, we can put this on our radar. But yeah, it probably
won't make 1.0, since I imagine we'll need to change a few things and it's a
little late in the game for some of those changes.
Christian
--
Hi,
I'm not sure I understand your problem yet. Your auth backend should be able
to set this information if you want it to. Is the problem mainly that the
appropriate fields don't appear in the preferences page? If so, it's because
we're explicitly checking the backend type in the prefs template.
On Sat, Jan 31, 2009 at 12:38 PM, Christian Hammond chip...@chipx86.com wrote:
Hi,
I'm not sure I understand your problem yet. Your auth backend should be able
to set this information if you want it to. Is the problem mainly that the
appropriate fields don't appear in the preferences page?
If you're developing code, I'd recommend getting a copy of SVN and
developing it there. Use devserver.sh (in the reviewboard directory) and
http://localhost:8080/ for the server. You'll have to create a
settings_local.py file and run ./manage.py syncdb first.
This will give you far better error
Hello.
Excuse the lame question, but how do I create and use custom auth
backends? I've created a file named foo.py located in
/usr/lib/python2.5 which looks like that:
from django.conf import settings
from django.contrib.auth.models import User
from djblets.util.misc import get_object_or_none
