#33171: Invalid link for readonly fields in django admin with missing permissions --------------------------------+------------------------------------------ Reporter: Ronny Vedrilla | Owner: Ronny Vedrilla Type: Bug | Status: closed Component: contrib.admin | Version: 5.1 Severity: Normal | Resolution: wontfix Keywords: | Triage Stage: Unreviewed Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 --------------------------------+------------------------------------------ Changes (by Sarah Boyce):
* resolution: => wontfix * status: assigned => closed Comment: Been discussing this quite a bit, I will close as: - a person can use [https://docs.djangoproject.com/en/5.1/ref/contrib/admin/#django.contrib.admin.ModelAdmin.get_fields ModelAdmin.get_fields] to remove any field a user doesn't have permission to view - this was [https://github.com/django/django/pull/12343#issue-551969369 previously considered] and is consistent with raw_id fields - the current solution adds some complexity I think the root of the problem might be elsewhere and we first need to agree what does it mean when you can't "view" (should the field be there at all?) I don't think we thought of something strong enough to revert the decision that "it's not worth it". -- Ticket URL: <https://code.djangoproject.com/ticket/33171#comment:8> 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 django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/0107019271c5991f-0d38666f-c512-474e-970c-09d41fad9441-000000%40eu-central-1.amazonses.com.