There's a branch of Django called NewForms Admin 
(http://code.djangoproject.com/wiki/NewformsAdminBranch 
) which will make it much easier to do what you're trying to do. From  
murmurings on this list it seems that branch will be merged into trunk  
before too long (in fact, there's a distinct whiff of 1.0 on the air  
these days), so it's not worth writing your own patches. Either switch  
to the nf-admin branch now, if you're in a hurry, or wait until the  
branch is merged.

Yrs,
Eric


On Apr 15, 2008, at 2:41 PM, dimrub wrote:

>
> (I will continue talking to myself here for a while)
>
> So, I've located the key passage in the django book:
>
> == quote ==
> Another implication is that the permission system, while powerful, has
> no support for limiting access on a per-object basis as of this
> writing. If you trust someone to edit his or her own stories, you
> trust that user not to edit anyone else's stories without permission.
> == end quote ==
>
> To the best of my understanding, the book tells me "Indeed, there is
> no way to do what you want to do, and there is a reason for it".
> However, it is an absolute must for my application, and I wouldn't
> want to give up on Django and its admin interface because of a small
> issue like this. Hence, a question: suppose I provide a patch that
> solves this problem (for example, a new field in the models class that
> is called, say, filter_by_user, and whose value is the name of the
> field which is a foreign key into the User table, and a corresponding
> code in the admin views that filters by this field). Is this patch
> likely to be excepted into the django's main version tree? If not, I
> will not bother (the solution above works, even if it's a kludge).
>
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to