[Django] #25821: Add verbose_name to foreign key fields in django.contrib.admin LogEntry
Django
--------------------------------------+--------------------
Reporter: RamezIssac | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.admin | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 1
--------------------------------------+--------------------
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
--
Ticket URL: <https://code.djangoproject.com/ticket/25821>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: RamezIssac | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: contrib.admin | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 1
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Is this different from #12952? If so, I don't understand how.
--
Ticket URL: <https://code.djangoproject.com/ticket/25821#comment:1>
Django
Reporter: RamezIssac | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: contrib.admin | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 1 | UI/UX: 1
Comment (by RamezIssac):
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]
--
Ticket URL: <https://code.djangoproject.com/ticket/25821#comment:2>
Django
Reporter: RamezIssac | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: contrib.admin | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 1 | UI/UX: 1
Comment (by souravsingh):
Is the issue open? If so,I would like to work on it.
--
Ticket URL: <https://code.djangoproject.com/ticket/25821#comment:3>
Django
Reporter: RamezIssac | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: contrib.admin | Version: 1.8
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 1 | UI/UX: 1
Changes (by timgraham):
* status: new => closed
* resolution: => duplicate
Comment:
Oh I see, that was done in #25073 (will be in Django 1.9).
--
Ticket URL: <https://code.djangoproject.com/ticket/25821#comment:4>