Opened 7 years ago
Closed 7 years ago
#28605 closed Uncategorized (duplicate)
Use verbose_name and localize field names in the admin history
| Reported by: | Carlos Mermingas | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 1.11 |
| Severity: | Normal | Keywords: | admin history |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
| Pull Requests: | How to create a pull request | ||
Description ¶
After an object's field is changed in the admin, the history displays Changed field name.
Here, field name is the Python class' attribute that was defined in the model.
I think that it would be better if the admin history displayed the attribute's verbose_name, if it has one, and translated it.
I am working on an app that will be used in Spanish and English. The admin history in Spanish shows sentences such as "Modificación de name y description" when it should be "Modificación de nombre y descripción". The name and description fields show their correct translations elsewhere in the admin.
Note:
See TracTickets
for help on using tickets.
Duplicate of #12952.