On Monday, 14 May 2012 02:39:53 UTC+1, jondykeman wrote: > > Hello, > > I have a form submission problem I can't seem to figure out a way around. > > Normally, once a form was submitted I would HttpResponseRedirect() to the > main page. > > However, there is something I can't seem to make work with this approach. > > The form is being completed/submitted in the context of an "active > account" ie. there is a hidden form field "account" with value="account #" > > So when the form is submitted the view saves the data to that account #. > > Once the new form data is saved I would like it to reload to that accounts > summary page. ie. the summary view needs to be passed the account # > > This is where my issue arises. I know this would be easy to pass > the HttpResponseRedirect() the view with args=(account#,) yielding an > appropriate summary page of eg. /summary/account3/ > > The kicker is I can't pass any account information through the urls so > there can only ever be a /summary/ url. The other views all work by passing > around the account # through POST. However, using this method to end the > form save view allows the user to reload the page and resubmit the form. > > Any help would be greatly appreciated!! > > Thanks, > > JD >
Store it in the session. That's a safer way of doing it anyway, rather than making everything a POST. -- DR. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/yV61xAwxrVMJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
