It would work, but there it's not very flexible. The current show_all_rows setting uses the change permission to determine if the object should be shown on the change list. Which makes sense, since the objects listed on the change list are those the user is able to edit.
For a related object in a select field it might require a bit more flexibility. For example, if we had a CMS where users can add articles, and there was a category model related to the article model. The administrator might create a list of categories that he does not want to be modified by other users. But he does want it set up so only certain users can post to certain categories and can not modify those given categories. It would work where the user has change permission or view permission. Maybe it's an addition that would only be used in a few extreme cases, if so there isn't much point in having it. For now, I'm working on modifying the code to use hte change permisison, but I'll allow it open to be extended to include a view permission depending on the feedback. Cheers, Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
