#21135: Admin: Support for editing OneToOne related models in RELATED model
-------------------------------+------------------------------------
Reporter: jonash | Owner: nobody
Type: New feature | Status: new
Component: contrib.admin | Version: master
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 timo):
* version: 1.5 => master
* stage: Unreviewed => Accepted
Comment:
A better solution may be to use model inheritance and proxy models to
achieve what you are trying to accomplish.
Here's what Malcolm had to say in an [https://groups.google.com/d/topic
/django-users/QWMsXf-I-AE/discussion old thread on django-users]:
Maybe you could knock up a patch to make this work and maybe it's
worthwhile (I don't really have a strong opinion either way, beyond
thinking that there's really no end to people twisting the admin
interface beyond intended usage and perhaps the should re-evaluate their
use-cases). This is "scratch your own itch" territory, I suspect.
I agree with the above.
I also found some possible code on
[http://djangosnippets.org/snippets/2032/ djangosnipppets]. Tentatively
accepting the ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/21135#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.80ba10ca8e2bbb62510f15d6222395ac%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
