At this point I believe the following is a complete set of requirements: Create a form with Html.BeginForm Turn on ClientValidationEnabled Turn on UnobtrusiveJavaScriptEnabled Set appropriate validation attributes on the model’s properties (not fields) If the Html Helpers being used to create the form elements are not on the same form as the Html.BeginForm call, … Read more
Ok, I am going to start over with a new answer here. Before you call $.validator.unobtrusive.parse, remove the original validator and unobtrusive validation from the form like so: var form = $(“#main_div”).closest(“form”); form.removeData(‘validator’); form.removeData(‘unobtrusiveValidation’); $.validator.unobtrusive.parse(form); This same answer is documented here.
The unobtrusive library will attach the validator on all forms, so you have to replace the submitHandler this way: $(“form”).data(“validator”).settings.submitHandler = function (form) { alert(‘submit’); form.submit(); };
If you are using jquery validate unobtrusive validation you could: $(function () { $(‘#signupform’).submit(function () { if($(this).valid()) { alert(‘the form is valid’); } }); });
Four hours later I finally stumbled across the answer. For some reason Chrome seems to have some inbuilt predilection to use US date formats where IE and FireFox are able to be sensible and use the regional settings on the OS. jQuery.validator.methods[“date”] = function (value, element) { return true; }
This issue is fixed in jQuery Validation Plugin 1.11.0pre. Unfortunately there is currently no pre-release build on NuGet, so it is currently necessary to download jquery.validation.js directly from GitHub: jQuery.Validation 1.11 is now available via NuGet (thanks @Simon_Weaver). UPDATE It looks like general support for jQuery 1.9 is in the jQuery.Validation code base but not … Read more
Once you have removed the offending item(s), clear the ModelState and validate again, like so: ModelState.Clear(); TryValidateModel(crew); // assumes the model being passed is named “crew” Note: Be carefull when use TryValidateModel method because this method does not validate nested object of model (As mentioned by @Merenzo).
I had the same problem. It seems that the unobtrusive validation scripts were not loaded (see screenshot at the end). I fixed it by adding at the end of _Layout.cshtml @Scripts.Render(“~/bundles/jqueryval”) The end result: @Scripts.Render(“~/bundles/jquery”) @Scripts.Render(“~/bundles/jqueryval”) @RenderSection(“scripts”, required: false) Except for my pretty standard CRUD views everything is Visual studio project template defaults. Loaded scripts … Read more
You can override the message by supplying the data-val-number attribute yourself when rendering the field. This overrides the default message. This works at least with MVC 4. @Html.EditorFor(model => model.MyNumberField, new { data_val_number=”Supply an integer, dude!” }) Remember that you have to use underscore in the attribute name for Razor to accept your attribute.
I tried Xhalent’s approach but unfortunately it wasn’t working for me. Robin’s approach did work and didn’t work. It worked great for dynamically added elements, but if you tried to use JQuery to remove all the validation attributes and spans from the DOM, the validation library still would try to validate them. However, if you … Read more