#33171: Invalid link for readonly fields in django admin with missing
permissions
-------------------------------+--------------------------------------
Reporter: Ron | Owner: nobody
Type: Bug | Status: closed
Component: contrib.admin | Version: 3.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
Rendering of read-only fields as navigable links was a
[https://docs.djangoproject.com/en/3.2/releases/3.2/#django-contrib-admin
new feature added in Django 3.2 (release notes)]. See also #31181.
Rendering is independent of whether the user has permissions to view the
related object. This is consistent with the existing behaviour of `raw_id`
fields, and was
[https://github.com/django/django/pull/12343#issue-551969369 considered in
the design phase]. To summarise, it was not considered practical (or worth
the complexity) to pass the `request` down to `AdminReadonlyField`, as
would be required to allow conditional rendering.
--
Ticket URL: <https://code.djangoproject.com/ticket/33171#comment:2>
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/064.48cf16a795edf81bbd7a8cb7e03125c5%40djangoproject.com.
