@validate becomes self._parse() and self._render_invalid(), both of these defined on BaseController. The on_get bit is near the top of _parse() - you could easily patch/override that. I have just noticed that I didn't remove that fragment from what's left of validate() - you would need to do that too if you still wanted to use the decorator.
Regards, Mike On Feb 28, 1:59 am, Jonathan Vanasco <[email protected]> wrote: > ah, interesting -- so the validation becomes a function of the > controller. > > i'd like to make a suggestion to your then. > > i have an arg to validate called gatekeeper , which is enabled as True > by default ( along with post_only ) > In conjunction with one another, gatekeeper just makes sure that if > you GET a form that is post_only ( or: not on_get ) , you > automatically raise an error. > > in the original pylons distro, it was possible to GET a post_only form > and have things not work out the way you would want them to. > personally i thought it opened the door to security issues, others > disagreed. > > ``gatekeeper`` > Default True. Boolean to raise an error on form submission if > not complete. > > the code in mine/patch to distribution is : > > if request.environ['REQUEST_METHOD'] == 'GET' and not on_get: > if gatekeeper: > ControllerInstance.osn_form.is_error= True > raise ValidationStop() > > I'm not sure how it would work on yours. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
