#342: Add a way for fields to be displayed in the admin without being editable
--------------------------------------+-------------------------------------
Reporter: Bless | Owner: nobody
Status: reopened | Milestone:
Component: Admin interface | Version: newforms-admin
Resolution: | Keywords: djangocon
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by simon):
* keywords: => djangocon
* status: closed => reopened
* resolution: wontfix =>
Comment:
I emphatically disagree - in practical terms this comes up ''all the
time''. A bunch of examples:
* You set the "date added" field automatically when something is created
but do not want editors to be able to change it because that would break
your date-based URLs - but they still need to be able to see when it was
created.
* You're implementing finely grained permissions where only certain users
can put something live on the site (by changing the published flag for
example) - a very basic workflow mechanism. Lower level users still need
to be able to see if something is published or not.
* You don't want people to be able to edit the slug once something has
been created, again to prevent URLs from breaking.
* Items in your database were created by importing data from a third party
(e.g. a sports feed, or pulling in photos from a Flickr photostream). You
want people to be able to edit certain fields that are specific to your
site, but not edit the fields that are determined by that external data
source.
* You want to automatically save "who created this", and allow that to be
viewed but not edited later.
* You're implementing a comment moderation interface. Users of that
interface should not be able to edit the IP address for a comment, but
should still be able to view it.
I've needed to do all of the above in the past. They all count as
"administering" data, but all require certain fields to be visible but not
editable.
(Plus it got a cheer at DjangoCon, so it should definitely be discussed
further as a potential feature for a future release).
--
Ticket URL: <http://code.djangoproject.com/ticket/342#comment:8>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
