Different onSuccess behaviour for different forms

[Magnanimity]

Hi, me again. :)

Again, not an issue, more of an enquiry. Firstly, I have different forms on one page. This is nothing new. The problem comes in that I do not actually use form submissions (my pages never refresh or redirect). I submit form info via AJAX. So in most cases where I have one form on a page, my jQuery would look something like this:

$(document).ready(function()
{
$.validate({
onSuccess : function()
{
someFunction();
return false;
}
});
});

So on successful validation of a form someFunction() gets called, which submits the info via jQuery AJAX. My problem is that I now have two forms on the same page that must call two different fuctions. Each form has its own unique ID. Is there a way that I can discern which form has just been successfully validated in the onSuccess portion so that I can run the relevant function call? I tried console.info(this) inside the onSuccess part, but the information that I get does not discern which form was just validated.

I initially tried onsubmit="someFunction();" on the form, but when I do that, someFunction() gets called even when the form does not validate successfully, which is why I'm using onSuccess.

[victorjonsson]

Yes, there is. The documentation is lacking this information. The form element actually gets passed into the onSuccess callback, the same goes for the error callback. Example:

$.validate({
  onSuccess : function( $form ) {
    if( $form.attr('id') == 'newsletter' ) {
        newsLetterSubmission();
    } else {
       feedbackSubmission();
    } 
  }
});

[Magnanimity]

Hi again, thank you for your feedback, but it is not working 100%. When I do a console.info($form), I get an object with all form elements on the page, so $form.attr('id') is not working. In the console, the form element from which I submitted is more prominent than the others, so there must be something different about this object element, but I cannot determine what is different. Sorry to be a nuisance. I really like your form validator, but I'm trying to achieve some complex stuff and I really appreciate your help.

[victorjonsson]

Well I can't say anything about your specific case since I haven't seen your code. What do you mean with $form.attr('id') not working? Have you set the id-attibute on your forms?

The callback function works as intended as you can see in this example http://jsbin.com/EtaYikub/1/edit

[Magnanimity]

My onSuccess callback is not returning the validated form, but instead returns all the forms on the page. I will update to the latest version and see if that helps.

[FDVS]

I have quite a few forms on my project as well, I went through Victor's suggestion and got it to work for me. I'll post it since it might help.

$.validate({
    modules: 'security, location', // security for email confirmation, location for country suggestion
    onModulesLoaded : function() {
        $('input[name="clCountry"]').suggestCountry(); //activate country suggestion
    },
    onError : function() {
        return false;
    },
    onSuccess : function($form) {
        switch ($form.attr('id')) {
            default:
                return true;
            case 'preLoginForm' :
                return false;
            case 'clientForm' :
                return false;
            case 'resForm' :
                if (!$('#toggleBookTime').attr('checked')) {
                    $('#bookTime').removeAttr('disabled');
                }
                if (!$('#toggleBookTime2').is(':checked')) {
                    $('#bookTime2').removeAttr('disabled');
                }
                if ($('#bookOne').is(':checked')) {
                    $('#otherway').remove();
                }
                if ($('#otherLoc').is(':checked')) {
                    $('#other').remove();
                }
                return true;
        }
    }
});

Seems to be working on this end and I don't set this up inside the $(document).ready(); event. Hope this helps.

[Magnanimity]

Hi again, just wanted to let you know that this issue was resolved with an update to the latest version.

Thank you very much.

[victorjonsson]

Great, thanks!