Hi all -- I'm having trouble figuring out how to properly design this in Django. I'm using the Django user system.
I've got an application I'm writing that allows people to browse an SVN repository in Django. In order to do this, I need to hang on to their username and password so I can hand it off to the SVN site whenever they hit the backend. I *really* don't want to store it in the database, so what I'm doing is creating my own login form that stores it in their session. That works fine. However, my main application *also* needs to check when users log in, to see if they've filled in some profile data before they can access the site. I don't want to put this check in my subapp (since it's separate from the main site) but I'm not sure how else to put things. In short, is there some recommended way I can have my code override the built-in login system, so different applications can have different things run on significant events (like login, user creation, etc?) -- Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
