On Sat, Dec 6, 2008 at 3:15 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> Would have to look at how FormPreview's work, but I agree.
>
> So far what I've done with the wizard is remove all of the data from
> the session as much as possible. It calculates cleaned_data at the
> very end and only s
On Wed, Dec 3, 2008 at 8:34 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> So far I've refactored a bunch of the methods to store less in the
> session, and generate more on demand (otherwise you could change the
> method and then session data represents inaccurate information). I've
> completedl
On Wed, Dec 3, 2008 at 7:50 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> So I needed the ability to specify initial data for a wizard, and I
> also liked the idea of storing it in the session (vs the POST). I was
> pointed to the SessionWizard patch, and I believe this was a
Would have to look at how FormPreview's work, but I agree.
So far what I've done with the wizard is remove all of the data from
the session as much as possible. It calculates cleaned_data at the
very end and only stores the POST values (still need to solve a
potential exploit). One thing I didn't
On Thu, Dec 4, 2008 at 03:34, David Cramer <[EMAIL PROTECTED]> wrote:
> When the done() method is called, the session is also cleared unless
> done(). Maybe this should only happen if say a ValidationError isn't
> raised? Maybe a setting that makes this not happen? In all of my
> situations it mak
t have
to call methods manual. Let's decide which is more common.
On Dec 3, 7:50 pm, David Cramer <[EMAIL PROTECTED]> wrote:
> So I needed the ability to specify initial data for a wizard, and I
> also liked the idea of storing it in the session (vs the POST). I was
> pointed t
So I needed the ability to specify initial data for a wizard, and I
also liked the idea of storing it in the session (vs the POST). I was
pointed to the SessionWizard patch, and I believe this was a 1.1
possibility as well, so I figured I'd bring up the numerous issues.
First and foremost
