Is GroupForm a ModelForm? If not where is it supposed to be saving?
What I don't understand is why this information is being adding to the
cleaned_data outside of the form. Why don't you create a custom save
function in the form and have the form handle this. Then there is no
need to manipulate class variables outside the class. I understand why
there is outside access to cleaned_data from outside the class, but I
really think that manipulating it inside of views should be avoided.
You can pass request in the _init_ or to the save and have it
availible when you are actually saving the item you anticipate it
should be saving.
Michael
On Tue, Apr 1, 2008 at 11:14 AM, timc3 <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I thought that I could add in some additional information to a form
> before it gets saved as a new object in the database but the following
> isn't working:
>
> def groupadd(request):
>
> if request.method == 'POST':
> form = GroupForm(request.POST)
> if form.is_valid():
> data = form.cleaned_data
> data['group_owner'] = request.user.id
> data['group_members'] = request.user.id
> data['group_admins'] = request.user.id
>
> newform = GroupForm(data)
> newform.save
>
> newform = GroupForm()
> return HttpResponseRedirect("/group/list/")
> else:
> form = GroupForm()
> return render_to_response('groups/group_add.html', {'form': form})
>
>
> It doesn't return any error and it doesn't save the new object. Is
> there anyway of sending additional data with a form?
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
