We had a site where we needed a wizard with the ability to go back and forward and store files. Only allowing files in the last step really isn't an option imho, that just avoiding the problem ;-)
What we did was simply store the files in a temporary folder and have a management command to clean them up when needed. (The files where stores with a timestamp in the name so we knew when they where old). I'm for having a better form wizard in django. +1 On May 30, 11:15 am, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > Hey Steph -- > > I've had a chance to play with your code, and I'm impressed and > generally +1 on replacing formwizard with yours. > > I couldn't tell from my quick play, though, if there were any > backwards-incompatible changes. There's a fair bit of code churn (in a > good way :), so before we could merge this I'd like a sense of what > any backwards-compatibily concerns would be. > > Thanks! > > Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
