Closed zebub closed 9 years ago
This is because the unlock method is called within ajaxStop
... and if you trigger another ajax inside unlock
, its calling itself on ajaxStop
.
If you upgrade to the latest release, the plugin uses some flags to check the locked
status before triggering unlock. So you should not face this.
For advanced usage and your info.. the updated plugin also uses namespaces to bind ajaxStop
(i.e. ajaxStop.kvfileinput
instead of ajaxStop
- so one can unbind the .kvfileinput
for advanced ajax calls).
I'm experiencing strange behavior when performing an
AJAX
request in afileunlock
event.This causes the
fileunlock
event to trigger when theAJAX
request completes, in turn causing a loop.