Re: Row-specific user permissions
Thank you Alex, this is an excellent article. On Jul 18, 5:55 pm, Alex Gaynorwrote: > On Sat, Jul 18, 2009 at 4:23 PM, nkulmati wrote: > > > Hi Django users, > > > It's been a while since I used Django, so I need an update on the > > following question. > > > Has anyone found a generic solution to django-admin's huge flaw - > > specifically, not being able to limit view/edit/delete activities > > based on object-specific (not model-specific) characteristics and user > > permissions? > > (For example. limiting what *instances* a user can see/edit/delete to > > only those he has created.) > > > Or do I still have to reinvent the whole admin application just to > > incorporate the feature? > > (Which, by the way, is a must for any collaborative online > > publication.) > > > Thanks to all who have thought about the same problem. > > Take a look at this:http://www.b-list.org/weblog/2008/dec/24/admin/ > > Alex > > -- > "I disapprove of what you say, but I will defend to the death your > right to say it." -- Voltaire > "The people's good is the highest law." -- Cicero > "Code can always be simpler than you think, but never as simple as you > want" -- Me --~--~-~--~~~---~--~~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Row-specific user permissions
On Sat, Jul 18, 2009 at 4:23 PM, nkulmatiwrote: > > Hi Django users, > > It's been a while since I used Django, so I need an update on the > following question. > > Has anyone found a generic solution to django-admin's huge flaw - > specifically, not being able to limit view/edit/delete activities > based on object-specific (not model-specific) characteristics and user > permissions? > (For example. limiting what *instances* a user can see/edit/delete to > only those he has created.) > > Or do I still have to reinvent the whole admin application just to > incorporate the feature? > (Which, by the way, is a must for any collaborative online > publication.) > > Thanks to all who have thought about the same problem. > > > Take a look at this: http://www.b-list.org/weblog/2008/dec/24/admin/ Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Voltaire "The people's good is the highest law." -- Cicero "Code can always be simpler than you think, but never as simple as you want" -- Me --~--~-~--~~~---~--~~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Row-specific user permissions
Hi Django users, It's been a while since I used Django, so I need an update on the following question. Has anyone found a generic solution to django-admin's huge flaw - specifically, not being able to limit view/edit/delete activities based on object-specific (not model-specific) characteristics and user permissions? (For example. limiting what *instances* a user can see/edit/delete to only those he has created.) Or do I still have to reinvent the whole admin application just to incorporate the feature? (Which, by the way, is a must for any collaborative online publication.) Thanks to all who have thought about the same problem. --~--~-~--~~~---~--~~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---