Thanks for this post it really helped and I've got it working nicely
now.
Like Honza, I wondered why you copied the post data- but I'm not sure
I understood your explanation. Does it give you more flexibility to
work with a copy?
Rgds, Tim
--~--~-~--~~~---~--~~
> is there any reason why you copy the data? the form doesn't need the
> data to be mutable, so there is no need for this.
None special reasons to be honest.
> I prefer constructing a dict manually than to mess around with python
> internals, but that is really just a matter of personal preferen
On 2/10/07, Lawrence Oluyede <[EMAIL PROTECTED]> wrote:
>
> > I now want to take an existing user record and create an edit account
> > form, where the data entered by the user in the registration form is
> > represented and available to edit. Seemed simple when I set out to do
> > it, but I can't
On 2/10/07, daev <[EMAIL PROTECTED]> wrote:
>
> On Feb 9, 10:12 pm, "Tipan" <[EMAIL PROTECTED]> wrote:
>
> > else:
> > form=UserAccountForm()
> > return render_to_response('account.html',{'form':form})
> somthing like this:
> form = UserAccountForm( u
On Feb 9, 10:12 pm, "Tipan" <[EMAIL PROTECTED]> wrote:
> else:
> form=UserAccountForm()
> return render_to_response('account.html',{'form':form})
somthing like this:
form = UserAccountForm( user.__dict__ )
--~--~-~--~~~
> I now want to take an existing user record and create an edit account
> form, where the data entered by the user in the registration form is
> represented and available to edit. Seemed simple when I set out to do
> it, but I can't seem to populate the form.
It's pretty easy. You provide a page
I'm new to Django and a relatively inexperienced programmer. I've
started working with the new forms and have been able to take user
input, validate it and write it to the table. Really slick and with
minimal code. Great.
I now want to take an existing user record and create an edit account
form,
7 matches
Mail list logo
