This seems to fix the problem, but I don't think this is a good
solution. Hopefully this patch makes the issue a little clearer though:
Index: django/views/generic/create_update.py
===
--- django/views/generic/create_update.py
The generic view django.views.create_update.update_object requires the
object to have an id in line 99.
manipulator = mod.ChangeManipulator(object.id)
Objects with OneToOneFields don't have an id attribute. Instead they
have something like "relatedobject_id" I'm not sure where this should
be
Any way of opening up registrations for trac? There's a LOT of
anonymous changing of ticket properties (one even switched a ticket
owner from adrian to anonymous) which is becoming a pain. Allow
registrations then restrict postig to registered users only?
--
Paul Bowsher
IT Systems Developer
Simp
Django Model is wonderfull. But SQLObject more flexible (and powerfull,
as i think, and has already more db interfaces).
But Django Model is tied with Django, and using Django with another OO
mapping is not comfortable.
Why do not working together? I can't understand.
If you (Django and SQLObject
Jason Huggins wrote:
>
> Robert Wittams wrote:
>
>>It seems that custom authorization is a common pattern that the generic
>>views and admin interface do not handle.
>
>
> I agree.
>
>
>>Any thoughts? I'm currently doing the first option with a wrapper round
>>the generic views. But I think
