On Nov 29, 8:26 pm, AJ <[EMAIL PROTECTED]> wrote: > James, > > Thanks for the reply, I can't tell you how many times I read over that > page in the documentation today, and didn't catch that. I think when > this problem arose I looked over the ModelForm docs and couldn't find > a solution. Thanks again for your assistance! > > On Nov 29, 6:38 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > > > On Sat, Nov 29, 2008 at 5:25 PM, AJ <[EMAIL PROTECTED]> wrote: > > > to the vairables self and commit. So as far as I can tell I can't do > > > this in the Admin. It looks like I would need to write my own custom > > > form and view. Is this correct, or is there another way to do this? > > > Consult the documentation for the admin; there are methods on > > ModelAdmin you can override to customize and control what happens > > during object saving.
Override your method and receive as a parameter the request object, so through the request object you can get access to the user logged in. > > > And in general, please consider doing some searching when you > > encounter something you don't quite know how to do; this is, for > > example, one of the most-frequently-asked questions about the admin, > > and the techniques for solving it have been covered repeatedly on this > > list and elsewhere. > > > -- > > "Bureaucrat Conrad, you are technically correct -- the best kind of > > correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---