Opened 16 years ago
Closed 9 years ago
#7923 closed New feature (fixed)
Add links when using raw_id_fields in admin
Reported by: | Julian Bez | Owned by: | Hugo Osvaldo Barrera |
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | Normal | Keywords: | admin raw_id_fields |
Cc: | bthomas@…, hugo@… | Triage Stage: | Accepted |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
When using raw_id_fields in the admin application you get a field with the id and a link for looking up an id.
Already 'selected' objects are written next to the field for your information, but are not linked.
The patch improves that. You can browse through the objects now.
Attachments (6)
Change History (29)
by , 16 years ago
Attachment: | admin-rawid-link.diff added |
---|
comment:1 by , 16 years ago
milestone: | 1.0 beta |
---|
comment:2 by , 16 years ago
milestone: | → post-1.0 |
---|---|
Triage Stage: | Unreviewed → Design decision needed |
comment:3 by , 16 years ago
Cc: | added |
---|
by , 16 years ago
Attachment: | patchtest.diff added |
---|
comment:4 by , 16 years ago
comment:5 by , 16 years ago
Status: | new → assigned |
---|
I think I followed the behavior of the magnifying glass. That is always there and results in a 404 if the object does not have an admin page. This should then be fixed, too.
comment:7 by , 15 years ago
Cc: | added |
---|
comment:8 by , 15 years ago
I've updated the code to recent trunk at http://github.com/mrts/django/tree/ticket7923 . One thing that needs to be resolved is whether the link should open in a pop-up. I personally prefer the current behaviour, but a pop-up would be more consistent with how the magnifying glass and + works.
comment:9 by , 15 years ago
milestone: | → 1.2 |
---|---|
Triage Stage: | Design decision needed → Accepted |
by , 15 years ago
Attachment: | ticket7923-3.patch added |
---|
Fix a copy-paste from test output that hardcoded admin media prefix.
comment:10 by , 15 years ago
The patch has been merged into the patch attached to #7028 as both issues are tightly related. Will not update the patch here any more.
comment:11 by , 15 years ago
Cc: | removed |
---|---|
Resolution: | → duplicate |
Status: | assigned → closed |
See #7028
comment:12 by , 14 years ago
Here's a snippet that adds links to ManyToManyField too: http://djangosnippets.org/snippets/2217/
comment:14 by , 9 years ago
Easy pickings: | unset |
---|---|
Severity: | → Normal |
Type: | → Uncategorized |
UI/UX: | unset |
Some of the latest patches from #7028 don't include this functionality any more - aside from the fact that the other issue has stagnated for a year now.
Can we reopen this, since it's simpler to implement alone? I'd be willing to work on it myself.
comment:16 by , 9 years ago
Cc: | added |
---|
comment:17 by , 9 years ago
Has patch: | unset |
---|---|
Resolution: | duplicate |
Status: | closed → new |
Type: | Uncategorized → New feature |
Seems fine to me. What about if the user doesn't have the "change" permission though? In that case we'll be outputting a link that leads to a "Permission Denied" page. It's not immediately obvious to me if there's a way to address that.
comment:18 by , 9 years ago
We can check if the user has change permissions before rendering the link.
We already do this to show the magnifying glass, I just need to dig into it a bit. I'll get back on this ASAP.
comment:19 by , 9 years ago
We already do this to show the magnifying glass, I just need to dig into it a bit. I'll get back on this ASAP.
Scrub that, the magnifying glass to select a related model is also shown if there are no permissions. There seems to be no clean way of avoiding a link to a 403 page - but it *is* consistent with the rest of the widget's behaviour (it's also a bit debatable if it's right to exclude the link or not).
I'm attaching an updated patch (GitHub is down ATM). It also uses the current admin site, rather than the default admin instance (which I noticed right away on my test app which uses several admin instances).
by , 9 years ago
Attachment: | 0001-Add-links-when-using-raw_id_fields-in-admin.patch added |
---|
Patch updated to apply on current master
comment:20 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:21 by , 9 years ago
Has patch: | set |
---|
Submitted a PR: https://github.com/django/django/pull/6054
comment:22 by , 9 years ago
Patch needs improvement: | set |
---|
Left comments for improvement on the pull request.
comment:23 by , 9 years ago
Patch needs improvement: | unset |
---|
Are the linked objects guaranteed to have an admin page? Looks like this patch assumes that they have one.