Hi, Ahmed. Your suggestion makes sense, but I think that, being called *Session*WizardView, it's very likely that this information is already stored in the session data.
The question is how could I "redraw" a concrete step, filled with the data previously entered by the user. I'm sure it's possible, but I can't figure out how. El domingo, 2 de febrero de 2014 15:30:28 UTC+1, Asad Jibran Ahmed escribió: > > We had a similar requirement in one of our products. We solved it by > assigning the user a unique transaction id when they start the process, and > saving all data in a temp db (redis) until the user completed the process. > And whenever the user accessed a page with the transaction id in the get > params, the data was autofilled in the form. > > Maybe you can do something similar by saving data for each part of the > wizard in a temp db under one key and using that to pre-populate the forms? > > Also, we used keys that woyld expire after some time, thus if the user > didn't complete the process, our db would start filling up with stale > transaction data. > > Hope that helps. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/57fd5ab6-716e-4ba4-aa55-a5c94b1d63f5%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
