We have done this before by creating a second model with a different fields definition in the Admin class, and then assigning the model to the same database table by specifying db_table in the Meta class. This allowed us to specify separate access permissions on each model, even though both models were manipulating the same table.
Kind of a hack, but it worked. (This was actually the impetus for submitting http://code.djangoproject.com/ticket/1766 ) On Jun 15, 10:04 am, andyhume <[EMAIL PROTECTED]> wrote: > Hello all, > > Other than writing a new view for the change form, is there anything I > can do to stop certain users or user groups from being able to edit a > particular field of the model in the admin? > > Cheers, > Andy. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
