OK, thanks.
I have a small correction to the form I used in the example (used
email field twice, it should be email and name):
${h.form(h.url_for())}
Email ${h.text('email')} <form:error name="email">
<br>
Name ${h.text('name')} <form:error name="name">
<br>
${h.submit('register', 'Register')}
${h.end_form()}
Also as for dynamically setting up contextual information for the
validation, you can use the "validation_ctx" method of the derived
FormHandler class you define to store that info in the "c" global (or
your own validation state object) based on the request parameters. And
then you can use that info in your validators. The "validation_ctx"
method is called by the decorator just before invoking the schema
validation.
On Jan 4, 3:42 pm, "Mike Orr" <[email protected]> wrote:
> On Sun, Jan 4, 2009 at 2:45 PM, Tycon <[email protected]> wrote:
>
> > PylonsHQ ticket system is down (does it run on pylons?)
>
> Added. It must have been down momentarily. The tickets are in a Trac
> project. I think pylonshq.com is Pylons.
>
> --
> Mike Orr <[email protected]>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
