#1688: Permissions don't get translated in admin interface
--------------------------------------+------------------------------------
Reporter: Rudolph Froger | Owner: hugo
Type: defect | Status: new
Component: Internationalization | Version: 1.2
Severity: normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Sebastian Rode):
I looked into #26756 as part of a Django sprint, it seems like the
underlying problem is the same. In both cases the verbose model_name is
written as permission.name to the database when creating it. This is not
updated when the verbose_name changes. The existing PR from a previous
author uses the migration plan to update the permission name explicitly
when any changes of verbose name happen. In my opinion the approach here
of not hard-coding the verbose model name to the database, is good, but
might have the potential of introducing breaking changes. I cannot really
judge this. Would be good to get some input.
--
Ticket URL: <https://code.djangoproject.com/ticket/1688#comment:15>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d37534779-903284b5-6c6c-495f-9a07-ac6cbd325b88-000000%40eu-central-1.amazonses.com.
