I have an application where I need to allow users of various levels
access to the same data. For example, I want to render a form
representing an employee profile to be displayed to the employee, his
supervisor, and the manager. All the fields need to be visible to each
of those different types of users, but only certain fields will be
editable by each; ie, the supervisor needs to be able to update the
pay grade of the employee, and the employee needs to be able to see
his pay grade, while being able to edit other things.
I've considered multiple approaches to accomplish what I need:
1) Add a method to the form class such as:
# forms.py
class ModelForm(ModelForm):
def check_permission(self, user, field):
# do test here
if failed_test:
return False
return True
class EmployeeForm(ModelForm):
...
The idea here was to use something along the line of {% if
form.check_permission user field %} within my template. Of course,
templates can only use methods which have no arguments, so this
approach quickly failed.
2) Add a method to each field after instantiating the form in the
view:
# views.py
def employee_detail(request, name):
...
def check_permission(self, user):
# do test here
if failed_test:
return False
return True
form = EmployeeForm()
for field in form:
field.check_permission = check_permission
...
Of course, this also runs into the problem where templates can't pass
arguments to methods, but the idea was to use {% if
field.check_permission user %}. A second issue with this approach is
that the template doesn't "see" new attributes/methods added to the
form fields in this fashion. So even if I modified this approach to
somehow be able to find the user object without it being passed as an
argument, I still can't use custom attributes/methods on form fields
in the template for some reason.
3) Create custom form fields that derive from a common custom form
field class which has the ability to be disabled at will through a
simple argument-free method call. This is not feasible simply due to
the sheer amount of coding that it would require for such seemingly
simple functionality.
The desire to display form fields in a disabled state based upon
certain conditions has got to be a common issue, but I was unable to
find anything helpful in extensive searches on google and on this
list, so I am hopeful that someone will have a suggestion about what I
can do. Probably I've missed something simple, as I tend to over-think
my problems quite often.
Thanks for any input.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
