I'm using newforms-admin
This is a very common situation:
on saving a Post
wish to set the author to be request.user
wish to set created_on and updated_on
perhaps wish to set request ip address
but it is actually the form object that does the saving.
but IMO none of these things are on the form or should be and aren't
the domain of the form itself (which is an interaction with a user on
a webpage and is principally about input validation).
they are the domain of the admin class (which handles the crud-life of
the object which is what is happening here)
I would suggest:
ModelAdmin
def save_add(self, request, model, form, formsets,
post_url_continue):
...
new_object = form.save(commit=False)
self.will_save(new_object,request)
new_object.save()
form.save_m2m()
def will_save(obj,request):
pass
so that our ModelAdmin subclasses can just implement
def will_save(obj,request):
obj.author = request.user
obj.last_modified = datetime.datetime.now()
obj.last_IP = request.IP
btw. I've looked through many solutions for this (eg.
http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser ) and
various tricks involving hidden fields or setting the author field to
be not required so as not to disturb the 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
-~----------~----~----~----~------~----~------~--~---
