The current admin (and the newforms one) doesn't allow enough
customization to make it user-friendly. That may be a feature, but
that is really boring to need to write its own admin because of the
limitations of the existing one.
In my case, I just have a ForeignKey to an User. At the first save,
user is automatically filled with the request.user. But after that, I
would like to display the author on the editing page, for information.
Simple (and generic) demand, and that patch allows it.
I am just against the special "readonly_fields" because that would
prevent us to organize fields like we want.
I would prefer that, imo :
fields = (
(None, {'fields': ('title','url','text')}, {'readonly_fields' :
('author')}),
(_("Options"), {'fields': ('date','lang'), 'classes':'collapse'}),
)
On 16 avr, 11:47, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-04-16 at 08:58 +0000, [EMAIL PROTECTED] wrote:
> ...
> Why is this needed? The field is marked as *editable*, hence it's not
> read-only. The admin app is for trusted users to edit records. If you
> want fine-grained control where administrators should not be editing
> particular fields that they could edit when they are not administrators,
> write a custom form. Even the current admin application allows custom
> forms for model editing and newforms-admin will, presumably, as well.
>
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
