#1688: Permissions don't get translated in admin interface
-------------------------------------+-------------------------------------
Reporter: Rudolph Froger | Owner: Emme
| Bravo
Type: defect | Status: assigned
Component: | Version: 1.2
Internationalization |
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
-------------------------------------+-------------------------------------
Changes (by Thibaud Colas):
* owner: hugo => Emme Bravo
* status: new => assigned
Comment:
Yes Sebastian that’s right!
As part of Djangonaut Space, team Neptune worked on the prototype together
and we arrived at this new version:
[https://github.com/django/django/pull/18885
https://github.com/django/django/pull/18885]. This extends the previous
POC to demonstrate that this approach works even for custom permission
names (at least as far as we can tell so far).
Assigning to @emmebravo to take this from quick POC to a fully-fledged PR
with unit tests, docs changes and all.
---
As far as we could tell, though what’s described in #26756 would
technically still apply, the changes as part of ticket #1688 would make
#26756 any further changes redundant. And for #27489, I believe it
wouldn’t fix that ticket / might help a bit but not much.
--
Ticket URL: <https://code.djangoproject.com/ticket/1688#comment:16>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019393ec1fe7-82686af6-9246-413b-aeca-32bc77f56b35-000000%40eu-central-1.amazonses.com.
