Remote validation when submit the submit button value is null #989

Closed
Vasioky opened this Issue Jan 17, 2014 · 3 comments

Comments

Projects
None yet
3 participants
@Vasioky

Vasioky commented Jan 17, 2014

Remote validation when submit the submit button value is null

@Vasioky

This comment has been minimized.

Show comment Hide comment
@Vasioky

Vasioky Jan 17, 2014

Here is how to reproduce the bug
https://github.com/Vasioky/JqueryRemoteValidationBug

@Vasioky

This comment has been minimized.

Show comment Hide comment
@Vasioky

Vasioky Jan 17, 2014

Interesting thing is that there is a workaround to add submitHandler

 $('form').validate({
                rules: {
                    Name: {
                        required: true,
                        remote: "Home/remote"
                    }
                },
                submitHandler: function (form) {
                    form.submit();
                }
});

Vasioky commented Jan 17, 2014

Interesting thing is that there is a workaround to add submitHandler

 $('form').validate({
                rules: {
                    Name: {
                        required: true,
                        remote: "Home/remote"
                    }
                },
                submitHandler: function (form) {
                    form.submit();
                }
});

@nschonni nschonni added the Remote label Feb 4, 2014

@jzaefferer

This comment has been minimized.

Show comment Hide comment
@jzaefferer

jzaefferer Jun 28, 2015

Collaborator

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.

To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!

Collaborator

jzaefferer commented Jun 28, 2015

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.

To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!

@jzaefferer jzaefferer closed this Jun 28, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment