Opened 9 years ago
Closed 9 years ago
#25821 closed Cleanup/optimization (duplicate)
Add verbose_name to foreign key fields in django.contrib.admin LogEntry
| Reported by: | Ramez Issac | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.admin | Version: | 1.8 |
| Severity: | Normal | Keywords: | |
| Cc: | ramezashraf@… | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | yes |
Description
Use case: using LogEntry in the admin , while another language then English is active; EntryLog Admin show English names for ForeignKeys names as their verbose_name is not specified.
Solution: Add verbose_name to ForeignKeys in django.contrib.admin.models.EntryLog
Change History (4)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Yes.
What i mean is adding verbose_name to LogEntry model itself, (user and content_type) fields
https://github.com/django/django/blob/stable/1.8.x/django/contrib/admin/models.py#L30
Version 0, edited 9 years ago by (next)
comment:4 by , 9 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Oh I see, that was done in #25073 (will be in Django 1.9).
Note:
See TracTickets
for help on using tickets.
Is this different from #12952? If so, I don't understand how.