#9931 closed (invalid)
outdated description in Django admin site documentation
Reported by: | gaumann | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.0 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The second sentence in the Django admin site documentation (http://docs.djangoproject.com/en/dev/ref/contrib/admin/#ref-contrib-admin) begins: "It reads metadata in your model to provide a powerful and production-ready interface that ..." I am just learning Django but it seems to me that this describes the old admin approach and now it reads metadata primarily from an Admin class. If my understanding is correct this sentence should be modified to reflect the change in 1.0
Change History (4)
comment:1 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 16 years ago
But the metadata is no longer in the model, now it is in a ModelAdmin class.
follow-up: 4 comment:3 by , 16 years ago
Data is still read from the Model itself, for example for the model the admin gets the types of fields, so it knows when to use the date time widget.
comment:4 by , 16 years ago
Replying to Alex:
Data is still read from the Model itself, for example for the model the admin gets the types of fields, so it knows when to use the date time widget.
I realise that it is reading some metadata from the model. However the way the documentation is written it is effectively saying it reads metadata only from the model. However in newforms it is reading metadata from both the ModelAdmin
class that is registered with the model and the Model
class. Hence I still think the documentation is confusing and it would be better to change it.
That sentence is still valid in 1.0. The admin is still reading metadata (being fields for example) to construct an admin interface. An admin class is not required for the admin to work.