generic.UpdateView and readonly ForeignKeys

76 views
Skip to first unread message

Lachlan Musicman

unread,
Feb 26, 2014, 5:17:28 PM2/26/14
to django...@googlegroups.com
I'm looking for a quick and easy way to implement readonly ForeignKeys
when using the generic.UpdateView.

I can't see anything that looks simpler than just ditching the
UpdateView and writing a function based view that sets the FK queryset
to a single object.

Or have I missed something?

cheers
L.

--
From this perspective it is natural that anarchism be marked by
spontaneity, differentiation, and experimentation that it be marked by
an expressed affinity with chaos, if chaos is understood to be what
lies outside or beyond the dominant game or system. Because of the
resistance to definition and categorisation, the anarchist principle
has been variously interpreted as, rather than an articulated
position, “a moral attitude, an emotional climate, or even a mood”.
This mood hangs in dramatic tension between utopian hope or dystopian
nihilism...
-----
http://zuihitsu.org/godspeed-you-black-emperor-and-the-politics-of-chaos

Lachlan Musicman

unread,
Feb 26, 2014, 5:33:53 PM2/26/14
to django...@googlegroups.com
Ok, I worked it quick and dirty. Do not try this at home, kids.

The field isn't strictly read only anymore, but I no longer mention
the field in question in forms.py

In the template, I've replaced the {{ forms.fk_model }} with {{
object.fk_model }}.

And now the field is plain text (the fk_model.__unicode__ ) instead of
a ModelChoiceField.

Cheers
L.
Reply all
Reply to author
Forward
0 new messages