Ok,
In AddView.update,
self.request.response.redirect(self.nextURL())
is called, but this is not called in EditView... so change isn't as
simple as moving nextURL. However, if you put this line into
EditView.update as well as moving nextURL, then my redirect works fine.
But does this
On Feb 17, 2006, at 1:42 PM, Shaun Cutts wrote:
Ok,
In AddView.update,
self.request.response.redirect(self.nextURL())
is called, but this is not called in EditView... so change isn't as
simple as moving nextURL. However, if you put this line into
EditView.update as well as moving
Difference beetween AddView and EndView
1) for AddView: 'self.context' is view (name '+')
2) for EditView : 'self.context' is content-object
I think this is 'standart' behavior. Use 'zope.formlib' for advanced
customization your forms.
В Птн, 17/02/2006 в 13:42 -0500, Shaun Cutts пишет:
Ok,
Ok --
Thanks Gary and Michael.
I've defined changed in my mixin, and it works:
def changed( self ):
self.request.response.redirect(self.nextURL())
And I can still use the same mixin to do redirect for both edit and add
forms, so I can't grumble about that.
I'm curious how this
On Behalf Of Garanin Michael
What is mixin? Is it content-object or view?
Well, I think in the wider python context mixin is something that you
can use as a base class to extend the functionality of your class,
assuming you provide some standard interface. (e.g. UserDict.DictMixin.)
I'm not
