not sure what i did, but i got this last bit working. i still need help on custom messages, & could use some guidance on getting contextual dependencies working with the accordion (making a radio input required only if a previous checkbox was selected -- i've looked at the examples, but can't get them to work in the context of the accordion).
cheers, --cz On Sep 4, 11:34 am, seezee <debbil...@gmail.com> wrote: > ok, i'm getting closer ... although i still haven't figured out how to > do custom contextual warnings as noted in the last post. the problem > i'm having now is that i have a radio button in my final accordion > container. i want the button to be required (checked="checked") for > the form to validate. but i need it to be unchecked when the user > opens the last part of the form, forcing them to select it before > final submission. the behaviour of the plugin is to validate the > entire form when the user clicks the 'next' button, which causes the > form not to open the final accordion if the radio button isn't > checked. how can i have it skip validating the final part (or any > hidden section) of the form until the accordion makes it visible? > > thanks, > > --cz > > On Sep 3, 9:53 am, seezee <debbil...@gmail.com> wrote: > > > > > hi, jörn, > > > thanks for the great plugin. if i can get it working as we need it on > > our main site, we'll be adding it to all our other sites as well. > > > i managed to get the form to validate w/ accordion functionality > > yesterday (i found the custom method before you replied), but i don't > > see how i can have multiple warnings based on context, which is pretty > > straightforward in the other examples. for instance, if if have: > > > class="pageRequired letterswithbasicpunc" > > > i then have the choice of either omitting the title tag, in which case > > the contextual message for 'letterwithbasicpunc' appears when needed, > > but the standard message appears otherwise, or i can include a title > > tag with a custom warning, which appears in _all_ contexts. is there a > > workaround for this? > > > On Sep 3, 6:53 am, Jörn Zaefferer <joern.zaeffe...@googlemail.com> > > wrote: > > > > Take a closer look at the multipart demo and its custom > > > pageRequired-method - thats key! > > > > Jörn > > > > On Wed, Sep 2, 2009 at 11:24 PM, seezee<debbil...@gmail.com> wrote: > > > > > i posted this to the plugin group, but it appears to be a dead forum > > > > -- last post was february. i'm trying to combine features of these 2 > > > > demos: > > > > >http://jquery.bassistance.de/validate/demo/milk/ > > > >http://jquery.bassistance.de/validate/demo/multipart/ > > > > > specifically, i want the ability to use custom error messages and to > > > > declare conditions in the page head, as in the 1st demo, as well as to > > > > use the accordion feature of the 2nd. if i use the code from the milk > > > > demo in the head, e.g., > > > > > $(document).ready(function() { > > > > // validate signup form on keyup and submit > > > > var validator = $("#signupform").validate({ > > > > rules: { > > > > [rules] > > > > }, > > > > messages: { > > > > [messages] > > > > }, > > > > }); > > > > } > > > > > validation runs on the entire form, including the sections not yet > > > > made visible. this prevents the 'next' button from operating, so the > > > > accordion won't expand. if i assign a unique id to the each fieldset & > > > > run separate validations for each fieldset, the accordion works, but > > > > the validation stops working. i'm pretty lousy at javascript, so i > > > > could sure use some help. has anyone else out there successfully tried > > > > this?
