I didn't know about the new form wizard code, I think I'll use that!
The auth issue happens with something as simple as this:
def view1(request):
return view2(request)
view1 = login_required(view1)
def view2(request):
return render_to_response(
'view2.html',
{},
context_instance=RequestContext(request)
)
view2 = login_required(view2)
On Sep 3, 10:31 pm, Joshua Jonah <[EMAIL PROTECTED]> wrote:
> Refactoring this as a form wizard would be the right way to deal with
> it, but that might be a large undertaking.
>
> Calling anotherviewshould not log you out unless it's explicitly
> deauthing. You need to figure out at which state it's trashing the
> session. can you dpaste some code for us?
>
> makebelieve wrote:
> > Hello, I've got aviewthat serves as a hub so that a multi-page form
> > has only one url. So when the user goes to the URL it sends them to
> > the first page of the form, the first page sends back to the hub,
> > which sends them to the second page and so forth. This worked great
> > until I required the user to be authenticated. It seems that when a
> >viewreturns anotherviewthe user is signed out. Any help on a way
> > around this would be greatly appreciated!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
