On Wed, 2009-02-18 at 18:07 -0800, adelevie wrote: > According to Djangobook, the philosophy of the admin site is that all > users of it are "trusted" not just "authenticated," meaning you will > trust them to do the right thing.
That's not an argument against a read-only display of information. The admin interface trusts everybody equally. However, some information that is stored in models is simply not designed to be edited. This is already part of the admin design, since you can configure which fields are in a form. That does not mean, though, that the non-editable information is not meant to be read. For example, imagine a model that fetches syndicated feeds from the web. Fetching can be disabled via a boolean in the model. If a permanent HTTP error occurs, fetching is automatically disabled. Now, an admin interface to edit feed location and the "fetch it" boolean makes sense. If the fetching has been disabled due to an error, displaying the HTTP error code (which could be stored as an attribute on the model) is very important, since it will help explain what sort of error was happening. That's not editable information (it's controlled by another source), but it is necessary to be able to read it. Regards, Malcolm = --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
