While toying around with the new rlp-branch i ran into the following
observations:
Row level permissions work great and as described in the documentation
wiki when objects are being accessed through their admin forms via the
admin index page.
If i try to edit related objects inline (as in the example) there are
two cases that do not work as i would have expected:
class Object:
name=CharField(...)
class Meta:
row_level_permissions=True
class Admin:
grant_change_row_level_perm=True
grant_delete_row_level_perm=True
show_all_rows = False
class ObjectProperty:
object=ForeignKey(Object, edit_inline=models.TABULAR)
some_property=CharField(...,core=True)
class Meta:
row_level_permissions=True
class Admin:
grant_change_row_level_perm=True
grant_delete_row_level_perm=True
show_all_rows = False
1.) 'ObjectProperty' objects can be created and edited nicely within
the 'Object' admin form but respective 'ObjectProperty' row level
permissions are not being set automatically.
2.) When editing 'ObjectProperty' in the admin the ForeignKey <select>
box displays all possible 'Object' choices without regard to the logged
in user's row level permissions.
I tried to file this as ticket in the trac but askimet spam protection
would not let me.
Hope this is right here.
Best regards,
littleswo
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
