Nevermind, I ended up trial and erroring through the plugin to find
what I needed—it would be awesome if this could be added to the
documentation for the plugin. The correct solution is below:
$("#signup").validate({
//better error placement to keep from breaking the grid on
checkboxes
errorPlacement: function(error, element) {
error.appendTo( element.parents('li').addClass('invalid') );
},
//strips the invalid class from the invalid lis when they become
valid, puts it back if they are still invalid
highlight: function( element, errorClass ) {
$( element ).addClass( errorClass ).parents('li').addClass
('invalid');
},
unhighlight: function( element, errorClass ) {
$( element ).removeClass( errorClass ).parents('li').removeClass
('invalid');
},
//rules and messages go here
});
As a side note, I must say that thus far I've been incredibly
disappointed by the community's lack of support concerning my last two
posts to the group. I switched over to jQuery from Mootools about a
year ago and have totally loved it, and have spread the gospel as much
as possible. I recently started working for a company that is listed
on the Mootools homepage as being one of their use cases, and have
actually managed to convince them that switching over to jQuery is the
way to go. Not that we are keeping score here or anything, but
another huge site using jQuery never hurts, particularly when said
site has migrated from Mootools. This lack of support has been kind
of a bummer for me in this regard, because I found the Mootools
community—which has a reputation for snottiness and snide "rtfm"
remarks—infinitely more helpful in situations like this. Hopefully
these two posts of mine have merely slipped through the cracks and
will remain isolated incidents, but I can't help but feel reluctant to
participate in the community given these experiences...
