-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatible with jQuery 3 slim build #541
Comments
Instructions for Reporting a Bug |
https://jsfiddle.net/v9mrjr7o/2/ (you have to open developer console and then try to submit form) But in description is already explained what could be wrong. jQuery v3 introduces a lot of sweeping chances: one of which is the removal of the jqXHR.success() callback (it has been deprecated since v1.8, but many authors don't seem to bother to migrate/update). The plugin is obviously not updated to listen to resolution of promise using the jqXHR.done() callback. Your best best is to revert to jQuery v2 or lower. – Terry Aug 12 '17 at 22:28 Thank you! |
I am sorry, my bad. It's probably not working only with Jquery 3 Slim |
Using the JSFiddle you provided, I'm unable to recreate your original error If I remove the Would you please update the JSFiddle to display the |
I am so sorry. That JSFiddle example wasn't properly saved. this one is ok. Sorry once again. |
Hey there,
I've got the problem with this package while using Jquery 3.2.1.
function ajaxForm is giving me an error: Cannot read property 'success' of undefined.
Someone on stackoverflow explained it there:
https://stackoverflow.com/questions/45655409/website-using-jquery-form-version-4-2-2-and-jquery-3-
jQuery v3 introduces a lot of sweeping chances: one of which is the removal of the jqXHR.success() callback (it has been deprecated since v1.8, but many authors don't seem to bother to migrate/update). The plugin is obviously not updated to listen to resolution of promise using the jqXHR.done() callback.
Is there any chance to fix this problem?
Thank you ;)
The text was updated successfully, but these errors were encountered: